Do you have your Nexus or other repository set up?
Maven will fall into place much better once you have this working.
You build your dependencies first, deploy them as SNAPSHOTS which puts
them into your team's repository and then Eclipse and Maven will build
your dependent modules painlessly.
When you are ready to release, repeat the process with release versions
and it all works seamlessly.
General advice to all new Maven users.
If you are having trouble with Maven, try to think what it is that you
are building that is so different from regular software.
If you are trying to build something that other people do and you are
having trouble, you are doing something wrong.
Don't try to fix or bend Maven, change your development process so that
it follows the Maven way.
Or don't use Maven unless you want to be completely frustrated and spend
many hours in the forum and modifying plug-ins.
Ron
On 03/10/2010 12:46 PM, Iron Eagle wrote:
Thank you. Importing the parent pom into eclipse solved the problem. Now all
dependencies are resolved correctly within eclipse and all artifacts are build
successfully.
The only thing, that is still not working, is building module A (that depends
on module B) within the directory of module A (and without having installed
module B before). But if I understand it correctly, this is a design issue of
maven.
best reagrds
-------- Original-Nachricht --------
Datum: Sat, 02 Oct 2010 15:02:26 -0400
Von: Marshall Schor<[email protected]>
An: Maven Users List<[email protected]>
Betreff: Re: Dependencies between modules of a multi module project
m2eclipse supports both styles of dependency resolution -
1) resolving using normal maven dependency resolution (usually, the
prebuilt jar
in the .m2 local repository), or
2) from the current workspace (allowing you to "pick up" changes there,
even if
the other project(s) weren't built/installed.
This is described in the m2eclipse book, here:
http://www.sonatype.com/books/m2eclipse-book/reference/dependencies.html#dependencies-sect-resolving-dependencies
-Marshall Schor
On 10/2/2010 7:22 AM, Antonio Petrelli wrote:
2010/10/2 Iron Eagle<[email protected]>:
Some times, I use the command line (there its no problem). But most
time, I use eclipse. I've searched for a tutorial for that problem, but the
result doesn't really satisfy me.
If you use m2eclipse and you checkout the entire main pom project as
Maven project, the project created for module B will have a reference
to the project for module A.
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
