mvn install -X and theck the debug logging on why the build of the war project is terminated.
/Anders On Wed, May 5, 2010 at 12:22, <[email protected]> wrote: > We have a large number of release projects with a common project layout. > Usually the release works well, but now we have a case that a module > dependency is not resolved: > > project structure (simplified): > -project (parent pom) > -project_war > -project_ear > --> depends on the war > > Now when we trigger the release 1.1, mvn complains during the build of > project_ear, that project_war:1.1 cannot be found. > project_war is triggered BEFORE project_ear (which is correct), but for > some reason, mvn finishes building the project_war module after the > compiler:compile phase. It doesn't run the package and install phases. > Hence, the project_war.war dependency cannot be found afterwards during the > build of project_ear. > > Any hint what is causing this? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
