Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <4285AF3B.2040209@douma.nu>
Date: Sat, 14 May 2005 09:56:43 +0200
From: Ate Douma <ate@douma.nu>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Jetspeed Developers List <jetspeed-dev@portals.apache.org>
Subject: Re: [VOTE] Changing version tags from"-dev" to "-SNAPSHOT"
References: <200505131611.j4DGBXZ23334@sunlist.sdrc.com>
In-Reply-To: <200505131611.j4DGBXZ23334@sunlist.sdrc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Well, I never much liked the "SNAPSHOT" feature of maven...

Although I can see it will make things easier when you have a *controlled* internal
remote maven repo, for others who don't this will introduce a new level of
unpredictability on what will be pulled in when they do a new build.

I myself prefer to be able to do a rebuild of a project, dependent on J2-cvs, knowing
only my project changes will be processed...
The only solution for that is using offline mode. But that is a pain when you
need to pull in new dependencies and as result have to go hunting for them yourself.

I could imagine a simple maven goal which synchronizes the local repository with your
internal remote maven repo when needed would be quite easy to write and gives the
same result without these (to me) negatives.

Anyway, as there is already enough support for this, I won't stand against it.
So, +0 from me.

A note to David (ST): be prepared that your bluesunrise repo will be hit much, much
harder as result of this, and make sure it contains a "stable" snapshot of J2-CVS.
It also might be wise to start looking in using the ibiblio repo.

Regards, Ate

Scott T Weaver wrote:
> I want to get everyone's' okay to change using -dev in our versions to
> -SNAPSHOT.  This would be a HUGE plus for those of us building applications
> based off of Jetspeed2's CVS.  For example, we have an internal remote maven
> repo to which we upload changed versions of the J2 jars.  The problem arises
> when changes are made in the CVS but the version does not change.  In this
> scenario, our automated builds will not pull new version of the jar from the
> remote repo into the local, causing all kinds of problems.
> 
>  
> 
> Regards,
> 
> -Scott
> 
>  
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org