You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Henri Yandell <ba...@generationjava.com> on 2004/05/15 05:26:44 UTC
[general] release instructions
Now that IO is out, I have 3 hours on a Saturday to spend on Apache. I'm
aiming to spend tomorrow improving the release documentation based on
discoveries while releasing IO.
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.
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.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [general] release instructions
Posted by Emmanuel Bourg <eb...@micropole-univers.com>.
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?
...and for those pulling the source from CVS and not using Maven (yet) :)
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [general] release instructions
Posted by Craig McClanahan <cr...@apache.org>.
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
>
>
>
This reply is tremendously out of date (sorry ... I've been travelling
and heads-down for the last couple of months, and am only just getting
back to Apache stuff) ... but here's the skinny on commons nightly builds.
- They run on my home desktop nightly, and get uploaded.
(I would heartily support a migration of this to some Apache
sponsored hardware somewhere, especially if others would
then be involved in maintaining the build scripts).
- My current build scripts require that "ant clean dist" (using a
relatively recent Ant) works correctly, and builds a "dist"
directory whose contents are what should be in a binary
distribution.
- In turn, that means a project must either use Ant as its primary
build tool, or use Maven to regenerate a build.xml that works
correctly whenever an incompatible change is made.
As of this morning when I tried, running "ant dist" on the build.xml for
configuration still fails trying to find class
"org.apache.commons.collections.map.LinkedMap" -- implying that perhaps
your project.xml file is pointing at an incorrect version of Commons
Collections (although I would have thought that would make your Maven
based builds fail as well.
Further, I could not even use "maven ant" myself to regenerate a
build.xml file (simply to see if that was the only cause of the
problem). I get a bunch of errors of the general form:
Invalid Redirect URI from:
http://maven-plugins.sf.net:80/maven/plugins/maven-findbugs-plugin-0.7.2.jar.md5
to:
http://maven-plugins.sourceforge.net/maven/plugins/maven-findbugs-plugin-0.7.2.jar.md5
The bottom line is that I'd be happy to add "configuration" to the set
of nightly commons builds, but I need a build.xml file that works to
make that happen.
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[general] continuous integration Was: [general] release instructions
Posted by 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
RE: [general] release instructions
Posted by Eric Pugh <ep...@upstate.com>.
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
Re: [general] release instructions
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
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
Re: [general] release instructions
Posted by Henri Yandell <ba...@generationjava.com>.
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
Re: [general] release instructions
Posted by Stephen Colebourne <sc...@btopenworld.com>.
> 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