I am goin to read that document right now.
Actually, I am only familiar with cvs and I am learning svn. However the
project I am staring is in ant and svn, so I hav to learn what the best way
to port an existing svn/ant application to svn/maven
---
Thank You
Mick Knutson
Sr. Java/J2EE Consultant
BASE logic, inc.
(415) 648-1804 (S.F., CA)
http://www.BASELogic.com
Washington Mutual (WAMU) (Emeryville, California)
---
From: Julian Wood <[EMAIL PROTECTED]>
Reply-To: "Maven Users List" <[email protected]>
To: "Maven Users List" <[email protected]>
Subject: Re: [m2] Do I need to change my directory structure for
subversion?
Date: Wed, 8 Feb 2006 17:56:09 -0700
If you're doing the porting, and it's okay to change around what is in
cvs/svn, I would do the following.
myproject/releases
myproject/branches
myproject/trunk
myproject/trunk/pom.xml
myproject/trunk/src
myproject/trunk/jar1/
myproject/trunk/jar1/pom.xml
myproject/trunk/jar1/src
myproject/trunk/jar2/
myproject/trunk/jar2/pom.xml
myproject/trunk/jar2/src
myproject/trunk/jar3/
myproject/trunk/jar3/pom.xml
myproject/trunk/jar3/src
The packaging on the parent is just 'pom', while each of the child modules
is jar. They will all be built automatically, if you package from the
parent basedir.
Use svn move to get to this dir structure.
myproject/releases is often called myproject/tags in maven parlance.
I'm not sure if you have to port over any releases or branches, but if you
do, I would try and close things out in cvs, then make a new branch in svn
and a new release using mvn, using your new dir structure.
I wrote a document on this latter type of stuff which might help:
http://wiki.ucalgary.ca/page/LearningCommons/Documentation/
Project_Versioning_-_Best_Practices
J
I have been using maven with cvs, and now am needing to move to
subversion.
And I am very confused at the how to deal with the ./branches, ./
releases, ./trunk I am seeing in an existing subversion project (that
does not have maven currently).
I guess my confusion is that the ant project I am migrating is boken up
into 3 different ars, but each has their own branch and trunk. Thus I was
confused by trying o match that to a module in m2. So it seems that I am
just going to have to create 1 maven project fo each jar.
Then however, my issue is how to I create an assembly that will contain
all these jars, as well as some extra resources I need in my assembly?
Do I still create:
root pom
--> ./jar1/trunk/**
--> ./jar1/trunk/**
--> ./trunk/src/main/assembly/*
--> ./trunk/src/main/resources/*
and then I will have to build the subprojects seperately?
---
Thank You
Mick Knutson
Sr. Java/J2EE Consultant
BASE logic, inc.
(415) 648-1804 (S.F., CA)
http://www.BASELogic.com
Washington Mutual (WAMU) (Emeryville, California)
---
From: "Mick Knutson" <[EMAIL PROTECTED]>
Reply-To: "Maven Users List" <[email protected]>
To: [email protected]
Subject: [m2] Do I need to change my directory structure for subversion?
Date: Wed, 08 Feb 2006 15:57:18 -0800
I have been using maven with cvs, and now am needing to move to
subversion.
And I am very confused at the how to deal with the ./branches, ./
releases, ./trunk I am seeing in an existing subversion project (that
does not have maven currently).
---
Thank You
Mick Knutson
Sr. Java/J2EE Consultant
BASE logic, inc.
(415) 648-1804 (S.F., CA)
http://www.BASELogic.com
Washington Mutual (WAMU) (Emeryville, California)
---
---------------------------------------------------------------------
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]
--
Julian Wood <[EMAIL PROTECTED]>
Programmer/Analyst
University of Calgary
http://commons.ucalgary.ca
---------------------------------------------------------------------
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]
