You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by simon <si...@chello.at> on 2008/02/07 08:02:58 UTC
RE: Conceptual Confusion about build and release process using
maven.
On Wed, 2008-02-06 at 09:47 -0500, Edelson, Justin wrote:
> > 1) During the development process within an iteration, how to make
> > sure that all the module owners dependent on "a.jar" keeps up to date
> > with the changing versions of a.jar as the development goes on until
> > Integration Testing.
> It sounds to me like you want to use a SNAPSHOT version within each iteration. That way dependent module owners don't need to constantly update their poms. Once you hit your testing phase, do an "alpha" or "beta" release of all the modules and test against that.
Yes, this is probably what you are looking for.
(1) deploying
When a module with a version of form 1.2.3-SNAPSHOT is deployed, then
there are two choices: with or without datestamp.
Without datestamp, the 1.2.3-SNAPSHOT file will just overwrite the
previous one in the repository.
With datestamp, a new 1.2.3-SNAPSHOT-yyyymmddn file file be created.
Whether deploy applies datestamps or not is configured in the repository
block. Using datestamps clutters the repository, but does mean that
other projects can decide to depend on the snapshot for a particular
date if they want.
(2)
When a project has a dependency on a 1.2.3-SNAPSHOT module, then it
checks the repository for a 1.2.3-SNAPSHOT-yyyymmddn or 1.2.3-SNAPSHOT
file, and downloads it if it is newer.
Exactly when the check is done is configurable: every time maven is run,
once per day, once per week (I think those are the options). I cannot
remember offhand where that is configured.
Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Conceptual Confusion about build and release process using maven.
Posted by Nicole Lacoste <ni...@gmail.com>.
Hi,
I recommend reading chapter 7, Team Collaboration with Maven, from Better
Builds with Maven.
Nicole
On 07/02/2008, simon <si...@chello.at> wrote:
>
>
> On Wed, 2008-02-06 at 09:47 -0500, Edelson, Justin wrote:
> > > 1) During the development process within an iteration, how to make
> > > sure that all the module owners dependent on "a.jar" keeps up to date
> > > with the changing versions of a.jar as the development goes on until
> > > Integration Testing.
> > It sounds to me like you want to use a SNAPSHOT version within each
> iteration. That way dependent module owners don't need to constantly update
> their poms. Once you hit your testing phase, do an "alpha" or "beta"
> release of all the modules and test against that.
>
> Yes, this is probably what you are looking for.
>
> (1) deploying
>
> When a module with a version of form 1.2.3-SNAPSHOT is deployed, then
> there are two choices: with or without datestamp.
>
> Without datestamp, the 1.2.3-SNAPSHOT file will just overwrite the
> previous one in the repository.
>
> With datestamp, a new 1.2.3-SNAPSHOT-yyyymmddn file file be created.
>
> Whether deploy applies datestamps or not is configured in the repository
> block. Using datestamps clutters the repository, but does mean that
> other projects can decide to depend on the snapshot for a particular
> date if they want.
>
> (2)
> When a project has a dependency on a 1.2.3-SNAPSHOT module, then it
> checks the repository for a 1.2.3-SNAPSHOT-yyyymmddn or 1.2.3-SNAPSHOT
> file, and downloads it if it is newer.
>
> Exactly when the check is done is configurable: every time maven is run,
> once per day, once per week (I think those are the options). I cannot
> remember offhand where that is configured.
>
> Regards,
> Simon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>