Hello,
when migrating to Maven 2 we have a multi-module project. The core
component is a web application but it also contains classes required for
other modules to compile.
Let's say we have
0 the parent pom project for all modules
A (the core) with packaging as war and
B which depends on A
When running mvn install on the pom.xml from the parent project (0),
maven complains about an unresolved dependency for A.jar. While that's
absolutely correct as there is only A.war, not A.jar
I have some diffculties to solve this issue. When I tried to set type
for dependancy to war, I got some exceptions.
I think the Maven way / good design would require to split up the
project but that is not possible by now, so please don't give that advise.
Is there a way to build the module twice, once as jar and once as war or
to tell Maven to include the required dependencies? From that what I've
read until now it should be possible by using two different pom.xml
(yes, really bad), but maybe it is possible by defining own
goal/lifecyle phase and using the assembly plugin (twice). But I'm new
to Maven and this seems to be a quite complex for me
as newbie by now.
Today when running mvn install on the parent pom everything seems to be
fine. Has this issue been solved in the last two weeks? I haven't
checked if there is a new version of some Maven plugin and the things
are really going on the last few weeks, new versions of m2eclipse,
maven3-SNAPSHOT (embedded in m2eclipse) and some plugins all over there.
With kind regards Sebastian
--
Sebastian Oerding
Senior Developer
Sun Certified Java Programmer
match2blue software development GmbH
Leutragraben 1
07743 Jena
Germany
Tel.: +49(0) 3641 573 3474
Fax: +49(0) 3641 573 3488
Mobil: +49(0) 176 96 036 136
[email protected]
www.match2blue.com
Geschäftsführer: Michael Selle
Registernummer: HRB 503726
Registergericht: Amtsgericht Jena
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
