You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Christian Schlaefcke <cs...@wms-network.de> on 2005/07/06 15:00:45 UTC

[m1]: SCM, CVS, Basic understanding, howto wanted

Hi Folks,

after I played around with m2 a bit I decided to start with m1 first 
because it is way better documented and easier to comprehend when 
beginning with maven at all. I did the ten minute test and my feeling 
about this is very good. As I want to go on I now want to try to manage 
my own project with maven. But now I have questions I cannot find the 
answeres anywhere.

My main question is: How do I setup my project with cvs?

I found brief information that it is possible and a short description 
how. But my requirement is a bit special. I need to setup a mechanism 
that any team member gets anything from the cvs-repository to start 
working without worrying what different projects, libraries, property 
files might be necessary to be able to work.
When I setup my project for maven I have it on my disc and I can modify 
and use the project.xml file to manage that project locally with maven. 
But what if the project and even the project.xml file only exists in 
cvs. How do I tell maven that this project resides in cvs. Or way round: 
How do I tell maven that a fresh generated project should be commited to 
cvs. Looks a bit like the hen & egg problem to me.

Another question I cannot find the answer for:
When sharing a team project we should have an internal repository, 
right? What to add to the (internal) maven repository? The projects in 
general? The sourcefiles? The libraries? The property files? Only the 
released jars? Nothing?

If you think I´m confused, you´re right ;-)
Any hint or link to useful documentation that points me to the right 
direction is highly appreciated!

Thanks & regards,

Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m1]: SCM, CVS, Basic understanding, howto wanted

Posted by dan tran <da...@gmail.com>.
Christian,

Take a look at maven-scm-plugin to bootstrap your build. 

You need an internal maven repository so that maven-jar-plugin,
maven-war-plugin,
etc to deploy to.  All those plugins use maven-artifact-plugin.  Read
the doc and plugin.jelly will give you a much better understanding.

Start with one simple project (like a jar file).  Then expand to
multiple projects
using maven-multiproject-plugin.

it is also well worth to have a comprehensive maven book since it seems you 
are new to maven.

Good luck.

-Dan








On 7/6/05, Christian Schlaefcke <cs...@wms-network.de> wrote:
> Hi Folks,
> 
> after I played around with m2 a bit I decided to start with m1 first
> because it is way better documented and easier to comprehend when
> beginning with maven at all. I did the ten minute test and my feeling
> about this is very good. As I want to go on I now want to try to manage
> my own project with maven. But now I have questions I cannot find the
> answeres anywhere.
> 
> My main question is: How do I setup my project with cvs?
> 
> I found brief information that it is possible and a short description
> how. But my requirement is a bit special. I need to setup a mechanism
> that any team member gets anything from the cvs-repository to start
> working without worrying what different projects, libraries, property
> files might be necessary to be able to work.
> When I setup my project for maven I have it on my disc and I can modify
> and use the project.xml file to manage that project locally with maven.
> But what if the project and even the project.xml file only exists in
> cvs. How do I tell maven that this project resides in cvs. Or way round:
> How do I tell maven that a fresh generated project should be commited to
> cvs. Looks a bit like the hen & egg problem to me.
> 
> Another question I cannot find the answer for:
> When sharing a team project we should have an internal repository,
> right? What to add to the (internal) maven repository? The projects in
> general? The sourcefiles? The libraries? The property files? Only the
> released jars? Nothing?
> 
> If you think I´m confused, you´re right ;-)
> Any hint or link to useful documentation that points me to the right
> direction is highly appreciated!
> 
> Thanks & regards,
> 
> Chris
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org