[general] continuous integration Was: [general] release instructions

[Henri Yandell <ba...@generationjava.com>]

I also have a nightly build [actually constant build rather than nightly]
running in my basement for Jakarta Commons [and sandbox] that looks much
like http://builds.osjava.org/.

It relies on Maven, not Ant.

Unsure if anyone is interested in me publishing it and hooking up email
warnings to the list. I know Apache are hoping to avoid being dependent on
3rd party resources.

Hen

On Tue, 18 May 2004, Eric Pugh wrote:

> configuration has a build.xml that is periodically spit out using the Maven
> Ant goal, however, it then requires massaging and therefore never seems to
> keep up with the Maven build..   I believe that it exists only for the
> nightly build, is that correct?
>
> I guess I'm asking:
> 1) What is required to get configuration to participate in the nightly
> build?
> 2) What is required to get configuration to participate in the gump build?
>
> Eric
>
> > -----Original Message-----
> > From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
> > Sent: Tuesday, May 18, 2004 2:37 PM
> > To: Jakarta Commons Developers List
> > Subject: Re: [general] release instructions
> >
> >
> > Yes, a big CAUTION there. Many of the build.xml's are generated by maven
> >   or hand written, and many are still in use by developers.
> >
> > I'd really like to see something where (take collections for instance)
> > maven.xml uses the ant build.xml script to either pregoal,goal,postgoal
> > the dist goal, this way collections can maintain their unique builds but
> > they can all be exec'd within maven too.
> >
> > I'm not sure about the top level jakarta-commons/build.xml, we should
> > review its usage and see whos using know days.
> >
> > -Mark
> >
> > Henri Yandell wrote:
> >
> > > Cool, what I was hoping [or hoping not to] find out :)
> > >
> > > Will ensure that I don't remove things.
> > >
> > > Hen
> > >
> > > On Sat, 15 May 2004, Stephen Colebourne wrote:
> > >
> > >
> > >>>I'm under the impression that all of our releases are now cut
> > using Maven,
> > >>>so I'd like to mavenise [as such] the release instructions so they make
> > >>>some sense in the modern context.
> > >>
> > >>By all means add maven stuff, but please don't delete ant references.
> > >>
> > >>
> > >>>Am I correct in this? Is there any reason to keep the old
> > build.xml's, or
> > >>>should we maven ant in each project and push in each maven generated
> > >>>build.xml.
> > >>
> > >>collections builds multiple targets now within the ant script,
> > and I'm not
> > >>in the mood of trying to get maven.xml to work.
> > >>
> > >>Stephen
> > >>
> > >>
> > >>---------------------------------------------------------------------
> > >>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > >>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > >>
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > >
> >
> > --
> > Mark Diggory
> > Software Developer
> > Harvard MIT Data Center
> > http://www.hmdc.harvard.edu
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>


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