--Original Message-
> > From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, February 21, 2006 9:52 PM
> > To: Maven Users List
> > Subject: Re: [m2] Newbie dependency question
> >
> > About the version, the best practices recommend to keep a sepa
hese
> > integrate? Do they label the source, apply the right value to the
> > tag in the pom, and keep track of incrementing the build number?
> >
> > Also, I assume in maven that each artifact/pom should be built in an
> > autonomous manor, each with its own automati
Alexandre,
I have some further questions below...
-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 21, 2006 9:52 PM
To: Maven Users List
Subject: Re: [m2] Newbie dependency question
About the version, the best practices recommend to keep a
t; I think that if I get the big picture of how to use maven2 in an aggressive
> continuous build system I can get going with it, right now I feel I don't
> know how to begin. (I have ordered a maven book but it isn't published yet.)
>
> Any ideas/suggestions are greatly
tly appreciated.
-dh
-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 6:13 PM
To: Maven Users List
Subject: Re: [m2] Newbie dependency question
>From what I understand you want to use the fresh version of some
components that are st
>From what I understand you want to use the fresh version of some
components that are still in development, what is usually called a
night build or a snapshot. You should declare their version as
1.0-SNAPSHOT or something like that. Then you just need to setup an
enterprise snapshot repository wich
