We had the exact same situation and we were using Maven Proxy for our
maven1 repo. What we ended up with was to have maven2 builds deploy to
our maven1 repo. Then we just have one repo ( the maven1 one ) that all
developers use. Our continuous integration build just deploys snaps
there on each successful build.
One issue we had was the way SNAPSHOTS were handled in the maven1 repo,
we needed to have unique groupID's for every project ( multiple projects
that deploy snapshots couldn't use the same group id, since the SNAPSHOT
time stamp version is resolved by the maven-metadata file or
something, one per directory in maven1? )
I'm not sure if this is the best solution, but it is working well for
us, at least until we can move to maven2 builds everywhere.
Saminda Abeyruwan wrote:
Hi All,
I'm new to Maven2. Please aid me to rectify the following Maven1 to Maven2
migration problem.
We have projects written with Maven1 and when we build the projects (They
are SNAPSHOT), basically these snapshots uploaded to local .maven repo.
We have been in the process of converting all Maven1 projects to Maven2.
Until the conversion completed, some converted Maven2 projects need to
refer to some of the jars in Maven1 repo (.maven). Is it possible to point
to this .maven repo (Maven1's) from pom.xml to get the relevant jars from
Maven1 repository. What are the options available for me to get this
working.
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.bloglines.com/blog/jbrekke [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
