I have a similar problem with the jspc-maven-plugin. That plugin uses
MavenProject.getCompileClasspathElements() to build a classpath that it
hands to the JSP compiler. When ran from a multiproject POM I get
target/classes in the classpath instead of the JAR file for one of the
projects that is part of the multiproject build. I need the JAR file (in
the repo) instead of target/classes because the JAR file has a .tld in
it, which is not in target/classes.
Richard Allen
Brian E. Fox wrote:
Copy-dependencies relies on maven to generate the list of dependencies
to copy. I suspect this is an issue in the maven dependency resolution,
where sibling dependencies are replaced with class path references
(example ../api/target/classes). File a jira under the mojo project and
I'll take a look.
-----Original Message-----
From: Stephen Duncan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 07, 2006 7:00 PM
To: [email protected]
Subject: [mojo-user] dependency-maven-plugin and MultiProject
I noticed this for the first time today.
Using the following structure
service
- api
- impl
I have the dependency-maven-plugin:copy-dependencies goal attached the
package phase of the impl module.
"impl" has a dependency on "api". When I run "mvn package" from the
"impl" folder, it correctly includes the "api" jar in the
target/dependency folder.
When I run "mvn package" from the "service" folder, the "api" jar is not
included in the impl/target/dependency folder.
Is there a bug already in the system for this? If not, where do bugs
for the dependency-maven-plugin go? I don't see a component for this
plugin at http://jira.codehaus.org/browse/MOJO
--
Stephen Duncan Jr
www.stephenduncanjr.com
