> I think a seperate (maven) plugin is the best to handle this, > so it can > also depend on a a plain eclipse installation, instead of a > huge amount > of jars on ibiblio that change quite often. (eg depending on an > ECLIPSE_HOME env variable or property setting.
+1 for the property setting. I hate environment variables. Eclipse has an Update Manager that can install new features. Such features define a consistent set of plugins and fragments and can be retrieved from a webserver in a specific format (the update site). The format is completely described in the docs on the Eclipse website. If we would create a maven eclipse plugin, I would like to state dependencies on features or plugins and be able to define the update site that host the features/plugins instead of the JARs from the maven repo (either local or remote). As far as I know, Maven HEAD has now general artifact support, so in my naive thinking, it shouldn't be that hard to depend on complete plugin zip files. With the addition of a special classloader, we add all the JARs in the zip to the classpath for compilation. All the JARs are specified in the plugin.xml file which is also in the ZIP. Comments? Did I make myself clear? Ringo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
