aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: [CANCELLED] [VOTE] Aries util and blueprint.api 1.0.0 release candidates
Date Tue, 03 Jul 2012 17:32:00 GMT
I haven't had a chance to look carefully at what Jeremy is saying, but I think he's probably
wrong about util.  Please note that there is only one intended output bundle from all the
util stuff.  Everything else is junk needed to build parts against two different osgi levels.

I don't think we need to change the groupId or artifactId of our previous util bundle.  We
should probably override the deploy mojo to skip deploy on everything except the intended
util bundle.

more later

david jencks

On Jul 3, 2012, at 10:22 AM, Holly Cummins wrote:

> I agree that we need to get the group id right for this release. At
> the moment util is the only bundle with a group id of
> org.apache.aries, so it's a bit of an exception to our pattern. I'll
> make these changes and respin the release. I'm not entirely convinced
> that util-bundle is an improvement on util, but since that only
> determines where things are in subversion, and not any externals, I
> think we can probably choose what we like. :)
> On Tue, Jul 3, 2012 at 5:51 PM, Jeremy Hughes <> wrote:
>> The util modules look odd. trunk/util used to be a single module with
>> no sub-modules and produced a single bundle. This is the first time
>> we're trying to release util since it changed to a multi-bundle
>> project. It hasn't followed the pattern of the rest of Aries and so
>> since this is a 1.0 release I think we should get it right. e.g.
>> org.apache.aries.util-parent should be groupId org.apache.aries.util
>> artifactId util.
>> Blueprint has blueprint/blueprint-bundle which outputs a bundle with
>> symbolic name org.apache.aries.blueprint. blueprint-bundle pulls
>> together content from multiple other sibling modules. Also, the
>> blueprint bundle has:
>> <groupId>org.apache.aries.blueprint</groupId>
>> <artifactId>org.apache.aries.blueprint</artifactId>
>> So, I'm thinking we should have util/util-bundle with BSN
>> org.apache.aries.util and that can pull together content from util-42
>> as it does today. OK, it's a bit different to blueprint because
>> blueprint-bundle is *just* about pulling together content from other
>> sub-modules. Along with this set the groupId to be
>> org.apache.aries.util and the artifactId to the same (that's how we do
>> it in blueprint) ... I appreciate this is a change to the maven
>> groupId but the BSN does stay the same.
>> Another thing is the javadoc. It would be good to have a single
>> javadoc jar but the more I look at it, the more I think, this is just
>> a nit.
>> Jeremy
>> On 29 June 2012 14:46, Holly Cummins <> wrote:
>>> I've staged a release candidate for the Aries 1.0.0 util and
>>> blueprint.api bundles. The modules are staged and tagged in
>>> Instructions for verifying the release are at
>>> Alternately, cut and paste the following to run a full check:
>>> wget --no-check-certificate
>>> chmod a+x
>>> ./ 287 mytempdirectory 2>&1 | tee verifyresults.txt
>>> grep FAIL verifyresults.txt
>>> grep ERROR verifyresults.txt
>>> Failures are reported since there are no SHAs for the
>>> archetype-catalog.xml file in the repository, but I believe this is
>>> acceptable (and I can update the script to filter these out if
>>> everyone else agrees).
>>> Artifacts are in one staged
>>> repo,
>>> Links to the *.zip files for each module are provided below.
>>> The RAT and IANAL build checks passed.
>>> The vote will be open for 72 hours.
>>> [ ] +1
>>> [ ]  0
>>> [ ] -1

View raw message