Yep - the Felix release process outlines this deployment of a snapshot
just before doing the actual release. I think it would make sense for
Aries to follow that too:
http://felix.apache.org/documentation/development/release-management-nexus.html
David
On 30 June 2014 22:27, Daniel Kulp
Deploying a snapshot would not help in that case, because the modification
i've had to make for the release is about upgrading from snapshots to
releases which are not available yet.
I've fixed the build by uploading a 2.0.1-SNAPSHOT of parent and switching
the being-released modules to it.
Our release instructions also include the deployment step:
http://aries.apache.org/development/releasingaries.html
In the discussion of the release strategy (incremental vs trunk-breaking)
they don't include the detail about preferring to depend on releases, which
might be worth adding.
Holly
Again, deployment of a snapshot is not the issue here.
The problem is that artifacts being released use the parent 2.0.0 which is
not publicly available yet.
Anyway, I've moved those bundles to use parent 2.0.1-SNAPSHOT so everything
should be sorted.
2014-07-01 10:45 GMT+02:00 Holly Cummins
release process
(was: Re: [VOTE] Release Apache Aries Parent 2.0.0)
Again, deployment of a snapshot is not the issue here.
The problem is that artifacts being released use the parent 2.0.0 which is
not publicly available yet.
Anyway, I've moved those bundles to use parent 2.0.1
is not
the issue here. The problem is that artifacts being released
From: Guillaume Nodet gno...@apache.org
To: dev@aries.apache.org
Date: 07/01/2014 03:51 AM
Subject: Re: Top down build of trunk failing during release process (was:
Re: [VOTE] Release Apache Aries Parent 2.0.0
From: Guillaume Nodet gno...@apache.org
To: dev@aries.apache.org
Date: 07/01/2014 03:51 AM
Subject: Re: Top down build of trunk failing during release process
(was: Re: [VOTE] Release Apache Aries Parent 2.0.0)
Again, deployment of a snapshot is not the issue here.
The problem
Subject:Re: Top down build of trunk failing during release process
(was: Re: [VOTE] Release Apache Aries Parent 2.0.0)
This is perhaps where my point about over-use of the snapshot dependencies
and the versioning applies. For example, does blueprint core now need
parser-1.2.1
PM
Subject: Re: Top down build of trunk failing during release process
(was: Re: [VOTE] Release Apache Aries Parent 2.0.0)
This is perhaps where my point about over-use of the snapshot dependencies
and the versioning applies. For example, does blueprint core now need
parser-1.2.1
Subject:Top down build of trunk failing during release process (was:
Re: [VOTE] Release Apache Aries Parent 2.0.0)
After the release candidate artifacts are posted, module poms have their
version bumped up. So parent is now 2.0.1-SNAPSHOT. Modules that are being
released
10 matches
Mail list logo
