The workaround is not working for me! I tried mvn release:prepare -DpreparationGoals="clean install" without success. Any other thoughts??
On Sun, Jan 25, 2009 at 11:44 PM, Barrie Treloar <baerr...@gmail.com> wrote: > On Mon, Jan 26, 2009 at 5:03 PM, Thiago Moreira (timba) > <tmoreira2...@gmail.com> wrote: > > Hi there, > > > > I have a multi module project and one of the sub modules produce two > > artifacts: temp-1.2.3.jar and temp-1.2.3-*test*.jar the last one is built > > using this configuration: > > > > <plugin> > > <artifactId>maven-jar-plugin</artifactId> > > <executions> > > <execution> > > <goals> > > <goal>test-jar</goal> > > </goals> > > </execution> > > </executions> > > </plugin> > > > > This second artifact is referenced in another sub module as a compile > > dependency. It works fine for all my development BUT it doesn't work when > > I'm trying to release it. Because the release:prepare goal only executes > the > > "clean verify" goals not the install one. > > This is a known problem > http://jira.codehaus.org/browse/MRELEASE-264 > > The workaround is to add to your command line > -DpreparationGoals=clean install > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
