The package goal should work as the reactor resolves dependencies using the built artifacts rather than the local repository. It does work with the normal "jar" packaging and fails with "bundle" packaging so there is something going on.
Using the install goal modifies the local repository and allows this to work. However, a build failure will result in an inconsistent local repository. We can turn bundling back on if we're OK with that happening on the build system (I don't know what else Gump is doing around the build e.g. is it wiping the local repo). On Nov 2, 2010, at 2:18 AM, Stefan Bodewig wrote: > On 2010-11-02, Jeremy Boynes wrote: > >> This started failing with r1029387. If I remove the >> <packaging>bundle<packaging> from the spec module then the reactor >> starts resolving it again. Could this be something with the bundle >> plugin not working with the package goal? > > I don't think so. It is more likely that the reactor inside Gump needs > to use the install goal so -impl is inside the local repo when -compat > resolves its dependencies. This is not the first time I've seen this > sort of behavior inside Gump. > > I've changed the goal used by Gump from package to install - let's see > whether this helps. > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
