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 zoe.slattery@googlemail.com
 designates 209.85.218.213 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=HrHROqDZ4gXrp505FU+spwvbOyn86uBRTXGa4R3XycgvpuB9jE8eioaXgm3v0ibESq
         p4GERrx7v33CrX+TFFtmNVaZkuX1J5Al9MrC/InHaAyYDEQILUoeH2mx2DzuGhBFk5+1
         riwzs2XJpDwfw8hl6gL6CpUStQmtAYlsO9wd4=
Message-ID: <4BAA085E.3000607@gmail.com>
Date: Wed, 24 Mar 2010 12:41:02 +0000
From: zoe slattery <zoe.slattery@googlemail.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: aries-dev@incubator.apache.org
Subject: Re: Aries release - the shape of repo org/apache/aries
References: <adbf02b11003080556i68fd066bwa3f0cc32dc0ca1cb@mail.gmail.com>
 	<4B951F1C.3050101@gmail.com> <4B9DB155.9030407@gmail.com>
 	<4BA8F223.6030909@gmail.com>
 <adbf02b11003240511i4f3b227duf7f00f26bb80eb03@mail.gmail.com>
In-Reply-To: <adbf02b11003240511i4f3b227duf7f00f26bb80eb03@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jeremy Hughes wrote:
> 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 the
>>>> 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 zip
>>>> files and make them available along with the sample jars. I think the right
>>>> 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 task of
>>>> 173 if you think this is the right thing to do.
>>>>         
>>> Creating the zip/tar is certainly one possible solution.  If 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).   I'm not opposed 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 the
>> blog sample. Generating the zip using the assembly plugin is straightforward
>> 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, then
>> '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 zip I
>> run:
>>
>> mvn install -Papache-release
>>
>> from within the standalone-assembly project, the  zip file is created and
>> 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 Execution
>> Root
>>
>> so, the zip file will never be built.
>>
>> Is there another way to do this?
>>     
>
> Assembly plugin would be the ideal way. Does setting
> runOnlyAtExecutionRoot to false work? It seems the default for this is
> false anyway, but maybe something in a parent / grandparent pom etc is
> setting it to true.
>   
It is set to true in the Apache7pom.xml. So, my understanding of this is 
that we if want to use the Apache release process we are stuck with 
it...does any Maven expert know a way around this?
>   
>> Or am I missing something obvious? If not 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.
>>
>> 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
>>>>>
>>>>>
>>>>>           
>>>>         
>>>       
>>     
>
>