Mark, running merely 'package' is faster, and it is useful in diagnosing problems.
On Wed, Oct 20, 2010 at 4:21 AM, Mark Struberg <[email protected]> wrote: > folks, really, > > $> mvn clean install > > is the way to LOCALLY install the snapshot, thus way getting the single jars > into your LOCAL maven repo (~/.m2/repository/org/apache/isis/...) so other > modules can pick it up. > > Otoh > > $> mvn package > > just _packages_ (builds the jar in ./taget) and doesn't make your module > available for other modules! > > Don't be afreaid to _install_ a mvn project. It doesn NOT mean that you > _deploy_ something into any upstream remote repository! > > THAT would be done with > > $> mvn clean install > > See the mvn default lifecycle for more details: > > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > > LieGrue, > strub > > --- On Wed, 10/20/10, Benson Margulies <[email protected]> wrote: > >> From: Benson Margulies <[email protected]> >> Subject: Re: Snapshots >> To: [email protected] >> Date: Wednesday, October 20, 2010, 12:14 AM >> I can tell you that. The reactor >> specifically exists for this purpose. >> However, the reactor is sensitive to what's been produced >> over the >> course of the build. There is no test-jar until the jar >> plugin runs to >> make the test jar, and your toplevel pom puts that in >> 'package'. If >> you moved that to compile, then all will be well. >> >> It's a bit of a magic trick that the normal jar file is >> available >> without 'package', but maven has a certain number of magic >> tricks. >> >> On Tue, Oct 19, 2010 at 8:05 PM, Robert Matthews >> <[email protected]> >> wrote: >> > That make sense and it then builds. The question >> then remains though as to >> > why the main source's dependencies can be resolved >> without the jar files >> > being created. >> > >> > I have posted a message to the Maven guys about this, >> so lets see what they >> > come back with. >> > >> > Rob >> > >> > On 20/10/10 00:55, Benson Margulies wrote: >> >> >> >> My patch isn't needed. Just run mvn package so >> that the test-jar >> >> artifacts get created. >> >> >> > >> > >> > > > >
