On Tue, Oct 16, 2012 at 3:19 AM, Wayne Fay <wayne...@gmail.com> wrote:
>> The problem with this is that I also need to build standalone jars of myLib2
>> and myLib3, and they need myLib1 themselves. Their code refers to classes in
>> myLib1 and myLib3 code defers also to classes in myLib2. myLib2 and myLib3 do
>> not even compile if they don't have myLib1/myLib2 listed as dependency in
>> their pom file. But if I list them as dependecies, those are expected to be
>> found in a repository or manually installed. Otherwise if I list them as
>> modules, I'm forced to packaging="pom", so no standalone jars...
>
> Just set things up as you've been told and build your projects from
> the top/parent each time, not from the children. Then the reactor
> finds the files it needs when it builds each library. Use packaging of
> "jar" in each lib, and use packaging "pom" for the top parent.

You dont need Nexus yet for your 3 module setup.

I assume the number of classes you have are tiny* (by some definition of tiny).
If you whole build run from the top level, as Wayne suggests, take
longer than 5 minutes then we can help you to speed it up.

Since you are new its easier to start with the small steps.

When you are feeling braver you can run with options like "--also-make".
But in your case I doubt that this will save you any cpu cycles.

Most people work in an IDE rather than on the command line.
What this means is, that most of the time you just work in your IDE
that has maven support (Eclipse or IDE do) and you let the IDE rebuild
your projects for you.
When you are ready to commit back into your SCM or you would like to
run the complete set of test (unit or integration) you break out to a
shell and run "mvn clean install" and check nothing is broken.
The incremental build cycle of an IDE will save you a lot more time
than trying to improve the Maven build process.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to