On Fri, Jul 10, 2009 at 6:17 PM, jdboer<jdb...@diversit.eu> wrote: > I know about the lifecycle and I've seen the ear lifecycle. > Because the ear:generateApplicationXml goal is causing the problem > (probably) I created a custom Ear plugin with version 2.3.2-TEST in which I > removed the generateApplicationXml goal (by removing all annotations from > GenerateApplicationXmlMojo class). The generateApplicationXml goal is not in > the plugin.xml file anymore. When I run 'mvn help:effective-pom' on the test > project, I can see the ear project uses the 2.3.2-TEST version of the Ear > plugin. > But when running 'mvn eclipse:eclipse' still the ear:generateApplicationXml > goal is sought. An error occurs now because I cannot be found. Logical > because it doesn't exist anymore, but why, who, where still searches for it?
Because the standard lifecycles are defined in plexus components - outside the plugins. You need to fiddle with the maven core if you want to pull out ear:generateApplicationXml from the build process. > Running 'mvn install' before 'mvn eclipse:eclipse' is not an option for us. > We have a very big Ear project with lots of jars and multiple wars. We want > a developer to be able to checkout the project and generate the Eclipse > project files without having the install everything first. Do you have continuous integration happening? If your CI server has already run mvn deploy (to your internal snapshot repository) then maven can pull down prebuilt dependencies. (They do not have to be the LATEST they just need to exist - since eclipse:eclipse will be resolving the projects to local files anyway) > Another solution I though of was adjusting the GenerateApplicationXmlMojo > class so it can resolve the dependencies via the reactor just like the > Eclipse plugin does. Both run in the generate:resources cycle so if the > Eclipse plugin is able to resolve the reactor dependencies, the > GenerateApplicationXmlMojo must be as well. That sounds feasible and probably a better solution. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
