Context Navigation

KIELER Meeting 2011/04/20

Christian presents the restructured build process.
The new build process requires plug-ins to be free of compile errors, which leads directly into the next topic...

#1621 rvh: For reasons of shameless self-promotion, KLay should present some sort of information in the status bar like "KIELER layout executed in x ms"; there should be an option to disable that feature
#1622 Rename the /trunk/tools folder to /trunk/plugins-dev
What do we do with 3rd party plug-ins and with experimental code?
- When we needed some libraries that are not available as Eclipse plug-ins, we just created a plug-in for it. They usually don't have any dependencies and don't disturb anything when they are in the trunk.
- Experimental stuff may go into the trunk, provided that it compiles fine. Highly experimental and possibly broken stuff should go into a private directory.
We should have a page in the Wiki listing all deleted plug-ins along with the number of the revision they were deleted in.
#1623 msp will go through all plug-ins and remove those we don't need any more:
- org.eclipse.papyrus.diagram.statemachine
- org.encog
- org.lejos.
- all krep plug-ins
Plug-ins that don't contain sources should have a build.properties file that doesn't have a src.. entry.
#1624 ybe will clean up his 3rd party plug-ins with msp:
- Plug-ins that exist as official, downloadable Eclipse Orbit plug-ins should be replaced by those.
- Plug-ins that don't, but whose source code exists should be checked in with their source.