Re: Build process question

[Alistair Wilson <al...@oracle.com>]

Thanks for the info.

I've read the release process document which is very similar to our 
process up to a point but does not cover a case where additional 
archives are generated and built.  For example, in addition to building 
the bridge sample war files during the maven deploy lifecycle and 
deploying them to a repository, the samples are also gathered together 
in zips/tars to be downloaded from the myfaces bridge site.  These 
additional files do not belong in a maven repository so, answering my 
own question, I suggest we'll be okay putting these additional files in 
a private people.apache.org directory for review as before.

On 23/12/2010 20:45, Mark Struberg wrote:
> Hi Alistair!
>
> Donald did a really great writeup for Apache BVAL. I used the same process already with OpenWebBeans with great success. And Lu, Gerhard and Jakob also already released MyFaces artifacts according to this guideline.
>
> http://incubator.apache.org/bval/cwiki/release-setup.html
> http://incubator.apache.org/bval/cwiki/release-process.html
>
>
> LieGrue,
> strub
>
> --- On Thu, 12/23/10, Alistair Wilson<al...@oracle.com>  wrote:
>
>> From: Alistair Wilson<al...@oracle.com>
>> Subject: Build process question
>> To: dev@myfaces.apache.org
>> Date: Thursday, December 23, 2010, 8:34 PM
>> Hi,
>>
>> I'd like to confirm a step in our release process using the
>> Nexus repository.
>>
>> We're getting the portlet bridge ready for release. 
>> The release consist of the maven artifacts which are
>> deployed to a staging repository (straightforward and
>> documented by other projects), and archives for the source,
>> examples and distribution which are built outside "maven
>> release:perform" and will eventually be downloaded from the
>> site.  In previous releases these zip/tars were copied
>> to people.apache.org for review and then manually copied to
>> the appropriate location to be downloadable.  I'd just
>> like to check this is still the case in the world of Nexus.
>>
>> Thanks,
>>
>> Alistair
>>
>
>

Re: Build process question

[Mark Struberg <st...@yahoo.de>]

Hi Alistair!

You can easily add those bundles to maven also. We have a few projects with their own 'distribution' or 'assembly' module which use the maven-assembly-plugin [1] to create those tar.gz and zip files. Usually the plugin is in a profile calles 'apache-release' or the while child-module only gets added in this profile, so this bundling will only be performed at release time.

Please see myfaces-core and myfaces-ext-cdi for an example.

LieGrue,
strub


[1] http://maven.apache.org/plugins/maven-assembly-plugin/

--- On Tue, 1/4/11, Alistair Wilson <al...@oracle.com> wrote:

> From: Alistair Wilson <al...@oracle.com>
> Subject: Re: Build process question
> To: "MyFaces Development" <de...@myfaces.apache.org>
> Date: Tuesday, January 4, 2011, 5:16 PM
> Thanks for the info.
> 
> I've read the release process document which is very
> similar to our 
> process up to a point but does not cover a case where
> additional 
> archives are generated and built.  For example, in
> addition to building 
> the bridge sample war files during the maven deploy
> lifecycle and 
> deploying them to a repository, the samples are also
> gathered together 
> in zips/tars to be downloaded from the myfaces bridge
> site.  These 
> additional files do not belong in a maven repository so,
> answering my 
> own question, I suggest we'll be okay putting these
> additional files in 
> a private people.apache.org directory for review as
> before.
> 
> On 23/12/2010 20:45, Mark Struberg wrote:
> > Hi Alistair!
> >
> > Donald did a really great writeup for Apache BVAL. I
> used the same process already with OpenWebBeans with great
> success. And Lu, Gerhard and Jakob also already released
> MyFaces artifacts according to this guideline.
> >
> > http://incubator.apache.org/bval/cwiki/release-setup.html
> > http://incubator.apache.org/bval/cwiki/release-process.html
> >
> >
> > LieGrue,
> > strub
> >
> > --- On Thu, 12/23/10, Alistair Wilson<al...@oracle.com> 
> wrote:
> >
> >> From: Alistair Wilson<al...@oracle.com>
> >> Subject: Build process question
> >> To: dev@myfaces.apache.org
> >> Date: Thursday, December 23, 2010, 8:34 PM
> >> Hi,
> >>
> >> I'd like to confirm a step in our release process
> using the
> >> Nexus repository.
> >>
> >> We're getting the portlet bridge ready for
> release. 
> >> The release consist of the maven artifacts which
> are
> >> deployed to a staging repository (straightforward
> and
> >> documented by other projects), and archives for
> the source,
> >> examples and distribution which are built outside
> "maven
> >> release:perform" and will eventually be downloaded
> from the
> >> site.  In previous releases these zip/tars
> were copied
> >> to people.apache.org for review and then manually
> copied to
> >> the appropriate location to be downloadable. 
> I'd just
> >> like to check this is still the case in the world
> of Nexus.
> >>
> >> Thanks,
> >>
> >> Alistair
> >>
> >
> >
>