On Thu, Sep 15, 2011 at 07:54:13PM +0200, Emmanuel Bourg wrote:
> The infra team has unlocked the deployment of snapshots for the
> components with a commons-* groupId, and Continuum is properly
> configured to be able to deploy the snapshots automatically if we
> desire so.
Is a nightly snapshot
The infra team has unlocked the deployment of snapshots for the
components with a commons-* groupId, and Continuum is properly
configured to be able to deploy the snapshots automatically if we desire so.
We are still not allowed to deploy JCS in its current groupId.
Emmanuel Bourg
Le 02/08/2
I've done some tests of snapshot deployment, here are my observations:
- Continuum is not properly configured to deploy Maven snapshots. If we
want to use it we'll have to request some help from the infra team.
- Snapshots for several projects using the old groupId commons-* can't
be deployed
I made a test with Continuum to deploy an artifact, I didn't expect to
trigger a mass failure of all projects. Sorry for the spam.
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional comma
Le 01/08/2011 21:21, Dennis Lundberg a écrit :
Phil, I have to respectfully disagree here.
What you are saying, and I'm paraphrasing here, is that we need to make
it as difficult as possible for our users to get hold of and use the
latest non-stable version of commons components. We should be m
On 8/1/11 12:21 PM, Dennis Lundberg wrote:
> On 2011-08-01 20:19, Phil Steitz wrote:
>> On 8/1/11 10:16 AM, Ralph Goers wrote:
>>> On Aug 1, 2011, at 10:03 AM, Luc Maisonobe wrote:
>>>
Le 01/08/2011 18:41, Phil Steitz a écrit :
> On 8/1/11 9:25 AM, Emmanuel Bourg wrote:
>> Le 01/08/201
On 2011-08-01 20:19, Phil Steitz wrote:
> On 8/1/11 10:16 AM, Ralph Goers wrote:
>> On Aug 1, 2011, at 10:03 AM, Luc Maisonobe wrote:
>>
>>> Le 01/08/2011 18:41, Phil Steitz a écrit :
On 8/1/11 9:25 AM, Emmanuel Bourg wrote:
> Le 01/08/2011 17:57, Ralph Goers a écrit :
>> These will ju
+1
>
> I really prefer a CI-triggered publishing. I see no values in producing a
> "nightly" if nothing has been changed.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@comm
On 8/1/11 10:16 AM, Ralph Goers wrote:
> On Aug 1, 2011, at 10:03 AM, Luc Maisonobe wrote:
>
>> Le 01/08/2011 18:41, Phil Steitz a écrit :
>>> On 8/1/11 9:25 AM, Emmanuel Bourg wrote:
Le 01/08/2011 17:57, Ralph Goers a écrit :
> These will just be new SNAPSHOTs so deploying a new one every
+1 - having it in a maven repo all ready for consumption hopefully increases
the motivation for testing.
If using a nexus repo it can tidy out stale instances.
The snapshot and release repos will be under distinct addresses anyway - so
it requires the consumer to actively configure this anyway...
On Aug 1, 2011, at 10:03 AM, Luc Maisonobe wrote:
> Le 01/08/2011 18:41, Phil Steitz a écrit :
>> On 8/1/11 9:25 AM, Emmanuel Bourg wrote:
>>> Le 01/08/2011 17:57, Ralph Goers a écrit :
These will just be new SNAPSHOTs so deploying a new one every
evening regardless of whether it has ch
Le 01/08/2011 18:41, Phil Steitz a écrit :
On 8/1/11 9:25 AM, Emmanuel Bourg wrote:
Le 01/08/2011 17:57, Ralph Goers a écrit :
These will just be new SNAPSHOTs so deploying a new one every
evening regardless of whether it has changed should be no big
deal. SNAPSHOTs without a timestamp overwrit
My view is 100% the opposite. We should provide only snapshot jars and if they
want the source they should get it from SVN. This is for two reasons - a)
deploying snapshots is easy and b) this is not a release.
Ralph
On Aug 1, 2011, at 9:41 AM, Phil Steitz wrote:
> On 8/1/11 9:25 AM, Emmanuel
On 8/1/11 9:25 AM, Emmanuel Bourg wrote:
> Le 01/08/2011 17:57, Ralph Goers a écrit :
>> These will just be new SNAPSHOTs so deploying a new one every
>> evening regardless of whether it has changed should be no big
>> deal. SNAPSHOTs without a timestamp overwrite a previous one
>> while timestampe
Le 01/08/2011 17:57, Ralph Goers a écrit :
These will just be new SNAPSHOTs so deploying a new one every evening
regardless of whether it has changed should be no big deal. SNAPSHOTs without a
timestamp overwrite a previous one while timestamped SNAPSHOTs should be
cleaned up automatically by
These will just be new SNAPSHOTs so deploying a new one every evening
regardless of whether it has changed should be no big deal. SNAPSHOTs without a
timestamp overwrite a previous one while timestamped SNAPSHOTs should be
cleaned up automatically by Nexus.
Ralph
On Aug 1, 2011, at 8:45 AM, Em
Le 01/08/2011 17:38, Jörg Schaible a écrit :
I really prefer a CI-triggered publishing. I see no values in producing a
"nightly" if nothing has been changed.
Either nightly or trigger by commit builds are fine as long as it's
automated.
Emmanuel Bourg
--
Phil Steitz wrote:
> On 8/1/11 2:19 AM, Emmanuel Bourg wrote:
>> Hi all,
>>
>> Once upon a time, in an era of pioneers, we had nightly builds
>> producing fresh jars available to heroic developers interested in
>> testing the latest features committed to our projects.
>>
>> As I understand now the
The implication to that is that if you piggyback on a Jenkins or Continuum
instance that is already publishing artifacts then you don't need a new
account. If you want to use a CI system that isn't already set up then you
will need to get one for that CI system to use.
Ralph
On Aug 1, 2011, a
Le 01/08/2011 16:57, Phil Steitz a écrit :
+1 for making nightlies available again. I think Continuum actually
produces the artifacts already and all we need to do is find a way
to make them publicly available. Several years back when the old
set up died, it was because the script that we were
On 8/1/11 2:19 AM, Emmanuel Bourg wrote:
> Hi all,
>
> Once upon a time, in an era of pioneers, we had nightly builds
> producing fresh jars available to heroic developers interested in
> testing the latest features committed to our projects.
>
> As I understand now there is no equivalent process.
+1 for uploading snapshots
AFAIK jobs on Continuum are already set up for every commons
component, so we should "just" properly configure the artifacts
deploy...
All the best,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Aug 1, 2011 at 3:49 PM, Ralph Goers wrote
I believe other projects are doing this with Jenkins so I see no reason we
couldn't also.
Ralph
On Aug 1, 2011, at 2:19 AM, Emmanuel Bourg wrote:
> Hi all,
>
> Once upon a time, in an era of pioneers, we had nightly builds producing
> fresh jars available to heroic developers interested in te
Hi all,
Once upon a time, in an era of pioneers, we had nightly builds producing
fresh jars available to heroic developers interested in testing the
latest features committed to our projects.
As I understand now there is no equivalent process. There is a snapshot
repository for Maven artifac
24 matches
Mail list logo
