Dear Maven Users:
I'm trying to integrate maven 2.0.4 into our projects. Internally we
have our own dependency/distribution/packaging mechanism, but would like
to leverage the power of maven. I am trying to integrate the use of
maven with our existing mechanism. I believe I have most issues sorted
out except for managing dependencies. I have a few ideas but I'm not
sure what the best practice should be and was hoping to get ideas,
thoughts, or advice on this from the community.
Here are some of my ideas
(1) Using a custom XML element, instead of :
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
</dependency>
have something like :
<customLocalDependency>
<groupId>junit-patched</groupId>
<artifactId>junit-patched</artifactId>
<version>3.8.1</version>
</customLocalDependency>
and write a plugin that is aware of our current mechanism. This plugin
can then add the junit-patched.jar to the classpaths based on the file
location our existing distribution/packaging mechanism.
(2) Use a specific groupId in the dependency that would trigger a
plugin that would add it to the classpath appropriately.
(3) Use the systemPath mechanism
<dependency>
<groupId>junit-patched</groupId>
<artifactId>junit-patched</artifactId>
<version>3.8.1</version>
<scope>system</scope>
<systemPath>/customdistributiondeploymentroot/lib/jars/junit.jar</systemPath>
</dependency>
Does this make sense? The idea is to use the dependencies in their
current location without the need to copy it into a local repository as
we have made quite a bit of investment in our current mechanism, since
we use it for qa, production, launches etc.
Thanks for any insight!
Sumit
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
