You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Dennis Lundberg <de...@apache.org> on 2008/01/03 22:50:51 UTC

Getting a grip on our current and future build systems

Hi

I've created a page on our wiki [1] where I have tried to show which
build systems are used by the different Commons components. Both proper
and sandbox components are represented, but in separate sections.

The page also has a little marking for "primary build system". To get
reasonable values for that I have taken the currently used build system
in the nightly build scripts in commons-nightly.

There are probably errors in there, so please feel free to jump in and
correct them. Especially the "primary" marking, as the people working on
a component might have other plans than the nightly builds...

I hope that this page can also work as a road map for us. We can use it
to show our intentions regarding which build systems we support. One
possible addition would be to have another marking for "will be
deprecated in the next release".

Please share your thoughts on the matter.


[1] http://wiki.apache.org/commons/BuildSystems

-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: Getting a grip on our current and future build systems

Posted by Rahul Akolkar <ra...@gmail.com>.
On 1/3/08, Dennis Lundberg <de...@apache.org> wrote:
<snip/>
>
> Please share your thoughts on the matter.
>
>
> [1] http://wiki.apache.org/commons/BuildSystems
>
<snap/>

I've used m1 for Commons releases, and it works well for me. ATM, I
have no plans to do things any differently in the near future.

-Rahul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: Getting a grip on our current and future build systems

Posted by Phil Steitz <ph...@gmail.com>.
On Jan 3, 2008 4:16 PM, Niall Pemberton <ni...@gmail.com> wrote:
> On Jan 3, 2008 10:55 PM, simon <si...@chello.at> wrote:
> >
> > On Thu, 2008-01-03 at 22:50 +0100, Dennis Lundberg wrote:
> > > Hi
> > >
> > > I've created a page on our wiki [1] where I have tried to show which
> > > build systems are used by the different Commons components. Both proper
> > > and sandbox components are represented, but in separate sections.
> > <snip>
> > >
> > > [1] http://wiki.apache.org/commons/BuildSystems
> > >
> >
> > Thanks Dennis, that looks useful. Things are actually more consistent
> > than I expected :-).
> >
> > I'd definitely like to see the next Digester release use maven2.
> >
> > The new new OSGi stuff seems a good reason to make a new Digester
> > release; once it's ready upstream I'll try to make time to work on that.
> > If you could spare some time to help with maven2 stuff for Digester that
> > would be great.
>
> AFAIK the m2 build is pretty much ready to use. The main difference is
> that the m2 binary distro includes the site, but the m1 only javadocs
> - thats easy to change if required. Otherwise I think the only other
> thing is to upgrade to commons-parent-6 if/when its released (fixes
> the duplicate notice/license issue caused by remote resources plugin).
>
> Try something like "mvn -Prc site assembly:assembly" to produce the
> jars, source and binary distros and see what you think.
>
> Niall
>
> Niall

Thanks to all of you guys for helping move this along.  While I am in
process of pushing out a m1 release for [pool], I hope this will be my
last and I went that route only because there is some urgency to get
this release out.

Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: Getting a grip on our current and future build systems

Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 3, 2008 10:55 PM, simon <si...@chello.at> wrote:
>
> On Thu, 2008-01-03 at 22:50 +0100, Dennis Lundberg wrote:
> > Hi
> >
> > I've created a page on our wiki [1] where I have tried to show which
> > build systems are used by the different Commons components. Both proper
> > and sandbox components are represented, but in separate sections.
> <snip>
> >
> > [1] http://wiki.apache.org/commons/BuildSystems
> >
>
> Thanks Dennis, that looks useful. Things are actually more consistent
> than I expected :-).
>
> I'd definitely like to see the next Digester release use maven2.
>
> The new new OSGi stuff seems a good reason to make a new Digester
> release; once it's ready upstream I'll try to make time to work on that.
> If you could spare some time to help with maven2 stuff for Digester that
> would be great.

AFAIK the m2 build is pretty much ready to use. The main difference is
that the m2 binary distro includes the site, but the m1 only javadocs
- thats easy to change if required. Otherwise I think the only other
thing is to upgrade to commons-parent-6 if/when its released (fixes
the duplicate notice/license issue caused by remote resources plugin).

Try something like "mvn -Prc site assembly:assembly" to produce the
jars, source and binary distros and see what you think.

Niall

Niall
> Cheers, Simon

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: Getting a grip on our current and future build systems

Posted by simon <si...@chello.at>.
On Thu, 2008-01-03 at 22:50 +0100, Dennis Lundberg wrote:
> Hi
> 
> I've created a page on our wiki [1] where I have tried to show which
> build systems are used by the different Commons components. Both proper
> and sandbox components are represented, but in separate sections.
<snip>
> 
> [1] http://wiki.apache.org/commons/BuildSystems
> 

Thanks Dennis, that looks useful. Things are actually more consistent
than I expected :-).

I'd definitely like to see the next Digester release use maven2.

The new new OSGi stuff seems a good reason to make a new Digester
release; once it's ready upstream I'll try to make time to work on that.
If you could spare some time to help with maven2 stuff for Digester that
would be great.

Cheers, Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org