Well, if the same issue was reported somewhere else and there is a workaround - go with that!
/Anders On Fri, Nov 13, 2009 at 16:19, Stephanie Johnson <jstephani...@gmail.com>wrote: > Added inheritance=true and phase=install, still install doesnt build the > assemblies. > > I read about the same issue in some forum last week, did not understand the > explanation correctly. Now trying to find the link, couldnt find it. But > there was some reference about parent pom referring to child, child having > reference to parent and that doesnt work well with assemblies. There was > some suggestion about writing a separate pom for assemblies alone. > > I have a sample project which can depict this problem. Will sending that > help? > > Thanks. > > On Fri, Nov 13, 2009 at 1:00 AM, Anders Hammar <and...@hammar.net> wrote: > > > I think what you're missing is making the plugin inherited. You set that > > like this: > > <inherited>true</inherited> > > Check the pom schema (or this page: > > http://maven.apache.org/guides/introduction/introduction-to-the-pom.html > ) > > for exact syntax. > > > > Also, I noticed that you don't have no id defined for the execution. > > I'm not sure if it's required though. > > > > To see the effective pom, execute > > mvn help:effective-pom > > This is very helpful to see what the child pom will be including > > inheritance and everything. Use that and to make sure that the plugin > > binding really exists in the child module. > > > > /Anders > > > > > > On Thu, Nov 12, 2009 at 20:47, Stephanie Johnson <jstephani...@gmail.com > > >wrote: > > > > > I have attached my parent pom.xml and one of my modules pom.xml. > > > Please take a look. > > > > > > Thanks. > > > > > > On 11/12/09, Anders Hammar <and...@hammar.net> wrote: > > > > You mus be doing something wrong. If the plugin is bound correctly, > it > > > will > > > > be executed. > > > > If you post the pom snippet we might spot the issue. > > > > > > > > /Anders > > > > > > > > On Thu, Nov 12, 2009 at 19:25, Stephanie Johnson > > > > <jstephani...@gmail.com>wrote: > > > > > > > >> Thanks for your suggestion Anders. But that doesnt seem to work. If > I > > > >> associate my assembly plugin to package phase or install phase and > run > > > >> mvn install or mvn package - it does not build my assemblies. > > > >> > > > >> I tried running mvn install first and then running mvn > > > >> assembly:assembly. This generates following error. > > > >> > > > >> [ERROR] BUILD ERROR > > > >> [INFO] > > > >> > > ------------------------------------------------------------------------ > > > >> [INFO] Failed to create assembly: Artifact: blaw blaw (included by > > > >> module) does not have an artifact with a file. Please ensure the > > > >> package phase is run before the assembly is generated. > > > >> > > > >> This is weird because all the dependencies are built installed and > > ready > > > >> to > > > >> use. > > > >> > > > >> Thanks. > > > >> > > > >> On 11/11/09, Anders Hammar <and...@hammar.net> wrote: > > > >> > You should bind the assembly plugin to an appropriate phase (such > as > > > >> > 'package'). The, you only need to run > > > >> > mvn install > > > >> > > > > >> > /Anders > > > >> > > > > >> > On Tue, Nov 10, 2009 at 22:33, Stephanie Johnson > > > >> > <jstephani...@gmail.com>wrote: > > > >> > > > > >> >> All, > > > >> >> > > > >> >> I am using Maven 2.0.9 to build a multi module project. I have > > > defined > > > >> the > > > >> >> assembly plugin in my parent pom. I can get my assemblies built > > using > > > >> >> > > > >> >> mvn install assembly:assemly > > > >> >> > > > >> >> This command runs the tests twice, once during install phase and > > > >> >> another > > > >> >> during assembly. I tried assembly:single but it throws an error. > > Any > > > >> help > > > >> >> to > > > >> >> fix get my assemblies built without running the tests twice is > much > > > >> >> appreciated. > > > >> >> > > > >> >> Thanks. > > > >> >> > > > >> > > > > >> > > > >> > --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > >> For additional commands, e-mail: users-h...@maven.apache.org > > > >> > > > >> > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > >
