Thilo Goetz wrote: > Marshall Schor wrote: > >> I've succeeded in getting maven to build the eclipse update site. Here >> are some particulars, in case anyone wants to suggest improvements >> before I commit things. >> >> First, I did two features. One is just the runtime plugin. This is for >> those projects which want to package something as an RCP (Rich Client >> Platform). The other feature is the Eclipse tooling for UIMA, >> including these 4 things: The Component Descriptor Editor, the Debug, >> the JCasGenp, and the Pear packager. >> >> The two features are set up so that the tools one automatically includes >> the runtime (if it's not already there). >> >> The features are also set up to "depend" on the things they need. This >> causes, for instance, EMF be specified as a dependency. If you select >> both the UIMA update site and a site having the EMF updates, the button >> to add needed dependencies automatically is usable. >> >> There will be 3 new projects for this: >> uimaj-eclipse-feature-runtime >> uimaj-eclipse-feature-tools >> uimaj-eclipse-update-site >> >> The feature projects have 1 file (feature.xml) needed by the maven >> build. But to make >> eclipse editing easier, I propose to check in the ".project" for these >> which sets the nature >> to allow for the feature editor to run. >> > [...] > > Is there no other way to do this? We already have so many projects. One > file per project really seems like a bit of a waste. No big deal, but if > there's a way this can all go into one project, I'd prefer that. > I agree - it's silly, but that's what the Eclipse mechanisms seem to make you do. I guess it's because each has its own "builder", or "nature" ... Or maybe I just don't know how to do it the other way :-)
-Marshall
