On Wed, May 16, 2007 2:03 pm, Barrie Treloar wrote: >> Who on the team is not going to have Eclipse installed? Even on a >> build server you would just install Eclipse. Not doing that means >> you're going to end up with a GB of duplication if you're using/ >> testing with multiple versions of Eclipse.
In our case, our build servers don't have Eclipse, because our build servers are headless Unix boxes. :( This doesn't mean our headless boxes can't have an eclipse installation directory available to them though. > At the moment I have used the maven-eclipse-plugin to duplicate the > Eclipse installation into the repository. The benefit of this is the > ability to create Eclipse Target Platforms using transitive > dependencies. If a plugin exists that is able to import an eclipse installation into a maven repository just by providing the location of eclipse, it seems logical that it should be possible to point at an eclipse installation as a maven repository of type "eclipse", as opposed to type "legacy" or "default". The only problem would be that information normally extracted from a pom, now has to be extracted from the plugin after the plugin has been downloaded. I'm not sure how much of a problem this would be, I don't know the internal workings of the dependency plugin that well. Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
