You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Olivier Dehon <od...@gmail.com> on 2007/11/28 14:13:44 UTC
Re: Issue in dependency resolution to zip file (having muliple
jars)
Murali,
One way to solve this problem is to create a pom instead of a zip.
The pom will have all the dependencies on your JARs.
Then, project B can include a dependency to the pom project to get all
of the JARs (transitively) in the classpath when building.
-Olivier
On Wed, 2007-11-28 at 05:01 -0800, S.Murali wrote:
> I have a Project A (util_common) which is a multi-module project which
> generates a zip file during its assembly (which contains all its sub-module
> jars) and i installed it in the local repository using
> install:install-file.
>
> Now, I want to add dependency to Project A (util_common) zip file in the
> Project B pom file.
> <dependency>
> <groupId>com.proj.risk</groupId>
> <artifactId>util_common</artifactId>
> <version>1.0</version>
> <type>zip</type>
> </dependency>
>
> However, the dependency to the jar files inside the util_common zip file is
> not getting resolved from Project B.
>
> I tried unpack all the jar files during the assembly phase, so that zip
> file contains the sources of jar files rather individual jar files. But, it
> did not work.
>
> I think the problem might be due to some classpath issue while referencing,
> though not sure.
>
> I would like to know if this is possible in maven? If so, how?
>
> Thanks in advance, Murali
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org