On 14 April 2011 15:26, John Casey <jdca...@commonjava.org> wrote: > mvn package install == mvn install
Except that it behaves differently, which is why I think it may be something more than just an assembly bug ... > Are you talking about assemblies created by previous Maven executions, that > are just lying around in file form in the target/ directory? > > Is there a project out there I can take a look at that will exhibit the > problem? See MASSEMBLY-553 for all the details. > On 4/14/11 9:20 AM, sebb wrote: >> >> The assembly plugin is broken for versions after 2.2-beta-5. >> >> Both 2.2 and 2.2.1 ignore attached assemblies which are defined in the >> parent pom when running "mvn install". >> >> However the attached assemblies are processed if one runs "mvn clean >> install" or "mvn package install", and they are also processed if >> defined in the current pom. It seems to be just inherited attaches >> that are ignored. >> >> Is anyone looking at this? >> >> It seems quite a serious error, which possibly exends beyond the >> assembly plugin itself, given that the package goal is implicitly >> called by install. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > -- > John Casey > Developer, PMC Member - Apache Maven (http://maven.apache.org) > Blog: http://www.johnofalltrades.name/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
