Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jpjhughes@gmail.com designates
 209.85.220.212 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:content-type
         :content-transfer-encoding;
        b=cEIue+dRzkZzDeOttKfRIUYkA/hyT1tddJdq4YxQBBw0mO7EJdQwL2nUiELmoPxrSe
         KrwhutOVkEjlgYaN0s2ho2ajKroyqVjO3KGu5JjJXR8uA5Fgsvi84lWrhAkNUnVdOng3
         On64CTLP4mNWFwABtzUMcs69onw/Uf7qI6S+I=
MIME-Version: 1.0
Sender: jpjhughes@gmail.com
In-Reply-To: <4BA8F223.6030909@gmail.com>
References: <adbf02b11003080556i68fd066bwa3f0cc32dc0ca1cb@mail.gmail.com>
	<4B951F1C.3050101@gmail.com> <4B9DB155.9030407@gmail.com>
	<4BA8F223.6030909@gmail.com>
From: Jeremy Hughes <hughesj@apache.org>
Date: Wed, 24 Mar 2010 15:10:03 +0000
Message-ID: <adbf02b11003240810q573e3b00sbd27b9fcca188ae1@mail.gmail.com>
Subject: Re: Aries release - the shape of repo org/apache/aries
To: aries-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 23 March 2010 16:53, zoe slattery <zoe.slattery@googlemail.com> wrote:
>
>>>
>>> 2) Sample 'assemblies'. At the moment most of the samples have a
>>> 'platform assembly' project which copies all the jars required to run t=
he
>>> sample into a target directory and provides some minimal configuration.=
 I
>>> think it might be a good idea to package the platforms as tar and/or zi=
p
>>> files and make them available along with the sample jars. I think the r=
ight
>>> way to do this is probably (I'd like advice on this, I'm definitely not=
 a
>>> Maven expert) to change the platform assembly projects to use the maven
>>> assembly plugin to create zip/tar files. I'll raise a JIRA as a sub tas=
k of
>>> 173 if you think this is the right thing to do.
>>
>> Creating the zip/tar is certainly one possible solution. =A0If we decide=
 to
>> go that route then the first mechanism that comes to my mind is the
>> maven-assembly-plugin (but I'm no maven expert either). =A0 I'm not oppo=
sed to
>> building the zip/tar of the platform assemblies - but I wonder if it is
>> really necessary.
>>
>>
> I am beginning to think it probably isn't possible :-).
>
> I spent some time trying to work out how to generate a platform zip for t=
he
> blog sample. Generating the zip using the assembly plugin is straightforw=
ard
> enough but I ran into problems when the apache-release process checks the
> licenses. I think it's checking for META-INF/LICENCE inside every jar in =
the
> zip. Of course it doesn't find them for equinox platform jars - so it
> chokes.
>
> A better plan would be to make a standalone-assembly project that will
> create a zip that just has a pom.xml (the same as the one in the the
> blog-assembly project) and the platform configuration files
> (configuration/config.ini). The zip could be extracted into say /tmp, the=
n
> 'mvn install' should create the whole platform as long as the user have
> maven and java installed. I have this working perfectly. To create the zi=
p I
> run:
>
> mvn install -Papache-release
>
> from within the standalone-assembly project, the =A0zip file is created a=
nd
> installed in .m2/repository. Great.
>
> However - this won't work as part of build of the full tree, the problem =
is:
>
> [INFO] [assembly:single {execution: source-release-assembly}]
> [INFO] Skipping the assembly in this project because it's not the Executi=
on
> Root
>
> so, the zip file will never be built.
>
> Is there another way to do this? Or am I missing something obvious? If no=
t I
> think we just have to say that people who want to run the samples have to
> check out and build Aries - this seems less than ideal to me. My
> standalone-assembly project is not checked in, I can do so if anyone else
> wants to look at this.

Sure, I think it's worth checking it in to share even if it's not
finished. I'll take a look if you do.

>
> Zoe
>
>>
>>
>>>
>>>> I appreciate this might be disruptive, but IMO it's best to have (what
>>>> I think is necessary) disruption done sooner rather than later.
>>>>
>>>> Please do comment on this proposal - I've tried to mark the changes
>>>> with 'TODO' to help.
>>>>
>>>> Thanks,
>>>> Jeremy
>>>>
>>>>
>>>
>>>
>>
>>
>
>