Cheers Max, very useful information.
I believe the approach will be more to try and work independently of the
existing m1 system. So current projects on m1 will work as they do right
now. New projects (like mine) will use an alternative based on m2. If
for some reason we decide to abandon m2, i can use the existing
infrastructure for m1.
That leaves the question of whether a machine can run both m1 and m2?
I'm guessing that to run m2 on the command line, you don't type maven(!).
Cheers
Rakesh
Max Cooper wrote:
On Thu, 2006-12-07 at 09:12 +0000, Rakesh Patel wrote:
Hi,
I have just joined a new company which uses Maven 1.x. I have no
experience with Maven at all and have been charged with evaluating a
move to Maven 2.x.
I am looking for some high-level information about the implications of
moving:
1. The existing infrastructure includes a repository for maven 1.x
builds - this must remain in place so is it possible to have a separate
repository for maven 2.x builds?
Absolutely. You can keep the m1 repo and setup a separate m2 repo with
no conflict. (It sounds like you can also use some tools to serve as a
dual m1+m2 repo as well, but I have no experience with that.)
2. We have a build machine which must be used for compiling all
releases. This is hooked to the maven 1.x repository. Can it (easily)
aslo use the maven 2.x repositiory or would we be better off starting
with a new build box?
Yes, m1 and m2 are configured independently, so you can point m1 at the
m1 repo and m2 at the m2 repo with no conflict. I have m1 and m2
installed on my PC, both pointing to different internal repos, and I can
run both without having to change any settings in between.
3. Any other issues?
Be aware that m1 and m2 are different, and that the conversion is
probably not going to be as easy as just installing m2 and running a
build.
M1 and m2 both use the project.xml file, and you won't be able to have
one project.xml file that works for both m1 and m2. So that means you
can't have both builds working at the same time, generally. You could
have both working if you set one up in a parallel structure as shown
below, but I would avoid this because it is troublesome to configure and
maintain, IME:
root/
|-module1/
| |-project.xml (for m1)
| |-src/
|-module2/
| |-project.xml (for m1)
| |-src/
|-maven2build/
|-module1/
| |-project.xml (for m2, refers to ../../module1/src, etc.)
|-module2/
|-project.xml (for m2, refers to ../../module2/src, etc.)
The maven.xml file (used for "scripting" in m1) is gone in m2. I would
review what is in your maven.xml files and see if equivalent
functionality can be achieved with core or 3rd party m2 plugins. For
stuff that you can't do with off-the-shelf m2 plugins, you will need to
write your own plugins or use the maven-antrun-plugin to hook in some
Ant scripts.
-Max
Like i said, i have not used Maven before and the hope is that if its
feasible to move to Maven 2.x on my project, then i can begin to learn
there.
Thanks
Rakesh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
