From the looks of it, you're hitting limitations of workspace artifact
resolution, i.e. even though maven correctly resolves project dependency
into target\classes folder, maven-war-plugin expects dependency to be a
file and fails. If both the war and the dependency project have the same
parent, you may have better luck running "maven install" goal on the
parent project. Or you can install dependency manually and package the
war project with workspace dependency resolution disabled (not pretty,
but should work).
Also, have you considered using wtp and m2e/wtp integration? You should
be able to run your projects directly from workspace, if the projects do
not rely on war overlays/warpath, at least.
Daniel Kröger wrote:
Hi,
I started to use m2eclipse (0.9.5) for a Wicket project which references
another Maven-based project in my Eclipse workspace through the
corresponding dependency in its pom.xml. I'm using Windows XP, Java 6
and Eclipse 3.4.
The workspace resolution does work and the referenced project is
correctly displayed under the Maven Dependencies classpath container.
However when packaging the Wicket project as WAR through a Maven Build
Run Configuration (the checkbox "Resolve workspace artifacts" is checked
there) a FileNotFoundException is thrown while processing this
dependency. I attached the complete stacktrace as textfile to this message.
Is this a known problem or did i just miss something? Thanks in advance
for your replies.
Regards,
Daniel
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
