On 03/02/2011 22:28, Guillaume Nodet wrote:
What kind of experiments do you have in mind ?
Probably this is more to do with my understanding (or lack of) of the
way in which the current maven
build specifies versions and how the release process deals with them.
I'm not sure to actually understand how the release process will be
different if we release everyting in one go, component by component,
or bundle by bundle. At the end, it always comes down to the same
steps: updating pom dependencies, mvn release:prepare release:perform,
updating jira, vote, updating the web site, annoucement.
The obvious different will be at which level you run the command from,
but apart from that, I kinda fail to see what kind of impact it would
have.
The aim is to keep the release process the same, as you say. To take a
specific example, I was looking at the quiesce module, the sort of thing
that the pom.xml would need to indicate is:
1) Quiesce module depends on released versions of parent, testsupport,
util (this is easy)
2) Quiesce module depends on a released version of the quiesce api (one
of the agregator's sub-modules) but development versions of the
implementation sub-modules.
At the moment to make step 2 work it's necessary to override the default
package imports for, say, the quiesce manager implementation and comment
out quiesce-api in the modules section. After that I get something which
builds and runs - the quiesce manager implementation bundle has the
correct package imports. I've checked in the quiesce pom (with debug in
it). I'm not quite sure what the release process will do with this, so I
need to check.
Zoe
On Thu, Feb 3, 2011 at 16:11,<[email protected]> wrote:
Author: zoe
Date: Thu Feb 3 15:11:33 2011
New Revision: 1066827
URL: http://svn.apache.org/viewvc?rev=1066827&view=rev
Log:
recreating with 0.4 from trunk
Added:
aries/branches/experimental-release-by-module/
- copied from r1066825, aries/trunk/
