commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton" <niall.pember...@gmail.com>
Subject Re: Getting a grip on our current and future build systems
Date Thu, 03 Jan 2008 23:16:55 GMT
On Jan 3, 2008 10:55 PM, simon <simon.kitching@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


Mime
View raw message