Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer;
  b=qKVpQRu5xTBYt+KyFxWeSKl/dVNoUzM4jaf0elstX8MZ9DSj1sSUEeKiBzdaloO2ok8fZhAROVRKSHdff63hrEG8UbWg5M2plE+VOtw2OU8jsprWD17gqdx/mUpGfCcCwmhkG4yGYgaiVKJj+cn3t/VpLYpjmGTm+AvX4zQMmlo=
  ;
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [CANCELLED] [VOTE] Aries util and blueprint.api 1.0.0 release
 candidates
From: David Jencks <david_jencks@yahoo.com>
In-Reply-To: 
 <CAC9tjn8NX41SYaF9V4q9Sqo8zUkebPhkwEyv9zsF-JPfNc+-aw@mail.gmail.com>
Date: Tue, 3 Jul 2012 10:32:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <607FA6B3-7EB4-4AA9-B784-A42AC4934F3E@yahoo.com>
References: 
 <CAC9tjn-rcDwzPsOQ6TaScpfu2jhyAYWZ_VBhnu2EVfYdJsF+Qg@mail.gmail.com>
 <CAKbW_r4Kx-SJPybThA=hXcmrM6tKmJV6T7vz2T5u-cREOrDqoA@mail.gmail.com>
 <CAC9tjn8NX41SYaF9V4q9Sqo8zUkebPhkwEyv9zsF-JPfNc+-aw@mail.gmail.com>
To: dev@aries.apache.org

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. :)
>=20
> On Tue, Jul 3, 2012 at 5:51 PM, Jeremy Hughes <hughesj@apache.org> =
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.
>>=20
>> 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:
>>=20
>> <groupId>org.apache.aries.blueprint</groupId>
>> <artifactId>org.apache.aries.blueprint</artifactId>
>>=20
>> 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.
>>=20
>> 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.
>>=20
>> Jeremy
>>=20
>>=20
>> On 29 June 2012 14:46, Holly Cummins <holly.k.cummins@googlemail.com> =
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
>>>=20
>>> =
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.util-parent-1=
.0.0/
>>> =
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.blueprint.api=
-1.0.0/
>>>=20
>>> Instructions for verifying the release are at
>>> http://aries.apache.org/development/verifyingrelease.html.
>>> Alternately, cut and paste the following to run a full check:
>>>=20
>>> wget --no-check-certificate
>>> =
https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
>>> chmod a+x verify_staged_release.sh
>>> ./verify_staged_release.sh 287 mytempdirectory 2>&1 | tee =
verifyresults.txt
>>> grep FAIL verifyresults.txt
>>> grep ERROR verifyresults.txt
>>>=20
>>> 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).
>>>=20
>>> Artifacts are in one staged
>>> =
repo,https://repository.apache.org/content/repositories/orgapachearies-287=
/.
>>>=20
>>> Links to the *.zip files for each module are provided below.
>>>=20
>>> =
https://repository.apache.org/content/repositories/orgapachearies-287/org/=
apache/aries/blueprint/org.apache.aries.blueprint.api/1.0.0/org.apache.ari=
es.blueprint.api-1.0.0-source-release.zip
>>> =
https://repository.apache.org/content/repositories/orgapachearies-287/org/=
apache/aries/org.apache.aries.util-parent/1.0.0/org.apache.aries.util-pare=
nt-1.0.0-source-release.zip
>>>=20
>>> The RAT and IANAL build checks passed.
>>>=20
>>> The vote will be open for 72 hours.
>>>=20
>>> [ ] +1
>>> [ ]  0
>>> [ ] -1