Hi Fabian, I don't understand why it's not enough to exclude some artifacts from the release profile in the parent pom.
Cheers, Reto On Mon, Jul 18, 2011 at 10:49 AM, Fabian Christ <[email protected]> wrote: > Hi, > > facing the problem that we may want to exclude some artifacts from a > release we need a way to manage this. I see the problem that at the > moment everything in trunk is aligned to be in a release. How would I > manage to exclude some artifacts and run it through Hudson? This would > change the trunk. Some integration tests may need to be disabled. > People currently working on code that will not be in the next release > may have the problem that they can't commit their stuff for the time > the trunk is freezed for the release. > > I read [1] linked from [2] and I'm thinking about creating such a > stable branch for doing releases. > > WDYT? > > [1] http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/ > [2] > http://incubator.apache.org/guides/releasemanagement.html#managing%20subversion > > -- > Fabian >
