Re: AW: [VOTE] use nexus for maven upload of ant release

jan.mate...@rzf.fin-nrw.de wrote: > If using Nexus is the "official way" I am +1 for uploading Ant, Antlibs and > Ivy. > > This wasnt part of the vote, but I am also > +1 for putting the upload procedure in a common.xml > Where should this common.xml live ? > +1 for using Ivy for uploading >

Re: xdocs and trunk

Jesse Glick wrote: > On 05/14/2010 06:28 PM, Antoine Levy-Lambert wrote: >> Then on the day of the release, I did another svn switch to trunk. > > I guess I'm confused then. The aim of the procedure was to have the announcement of the release checked in in trunk in advance, because this is part of

Re: Ant source structure and ant*.jar build products

Hello Jesse, Jesse Glick wrote: > In relation to > : > > Ironically enough, I find the Ant build script to be a poor example of > an Ant script. The system of compiling certain classes and not others > according to classpath availability,

Re: xdocs and trunk

On 05/14/2010 06:28 PM, Antoine Levy-Lambert wrote: Then on the day of the release, I did another svn switch to trunk. I guess I'm confused then. We could also use the ANT_SITE branch permanently That would make sense to me. Of course you would only need to branch xdocs, not the rest of th

Re: xdocs and trunk

Hello Jesse, in fact, the ANT_SITE branch is a branch which contains all the source code of ant-core. I created it to handle the period between the build of ant 1.8.1 and the actual release. I svn switched to ANT_SITE /www/ant.apache.org on people.apache.org after having committed changes announc

Re: Ant source structure and ant*.jar build products

On 05/14/2010 04:00 PM, Peter Reilly wrote: Personally I think that there should be only one ant.jar file ... and not loads of itty-bitty ones. This would break usage from Maven repositories, for which separate POMs with separate dependency lists are created. ---

Re: Ant source structure and ant*.jar build products

Personally I think that there should be only one ant.jar file (as was the case in ant 1.5 - well two) and not loads of itty-bitty ones. Peter On Fri, May 14, 2010 at 7:08 PM, Jesse Glick wrote: > In relation to : > > Ironically enough, I

xdocs and trunk

As I understand it, xdocs/ is now being maintained on the ANT_SITE branch, rather than being tied to a product branch. If so, shouldn't this directory be deleted from the Subversion trunk, to avoid any possible confusion? - To

Ant source structure and ant*.jar build products

In relation to : Ironically enough, I find the Ant build script to be a poor example of an Ant script. The system of compiling certain classes and not others according to classpath availability, and then packing classes to different JARs,

Re: AW: [VOTE] use nexus for maven upload of ant release

+1 to all these good ideas, including the three on the original vote. On 14/05/2010 2:35 AM, jan.mate...@rzf.fin-nrw.de wrote: If using Nexus is the "official way" I am +1 for uploading Ant, Antlibs and Ivy. This wasnt part of the vote, but I am also +1 for putting the upload procedure in a com

Re: [VOTE] use nexus for maven upload of ant release

+1 for all. Gilles Scokart On 13 May 2010 22:19, Antoine Levy-Lambert wrote: > Hi, > > Brian Fox on the repository list has advised me to upload the ant artefacts > to the maven repository using nexus. [1] > > I have entered a sub-task of INFRA-1996 "Track projects that want to use > the Nexu

AW: [ANN] release of Apache Ant 1.8.1

1.8.1 by me (without any proxy) Jan >-Ursprüngliche Nachricht- >Von: Maarten Coene [mailto:maarten_co...@yahoo.com] >Gesendet: Freitag, 14. Mai 2010 13:29 >An: Ant Developers List >Betreff: Re: [ANN] release of Apache Ant 1.8.1 > >Maybe it is caused by the proxy server, but >http://ant

Re: [ANN] release of Apache Ant 1.8.1

Maybe it is caused by the proxy server, but http://ant.apache.org/manual/index.html still points to the 1.8.0 documentation? Maarten - Original Message From: Antoine Levy-Lambert To: Ant Developers List Sent: Sat, May 8, 2010 1:15:23 AM Subject: [ANN] release of Apache Ant 1.8.1 Hi

Re: [VOTE] use nexus for maven upload of ant release

+1 to all and +1 to doc howto Peter On Fri, May 14, 2010 at 10:47 AM, Kevin Jackson wrote: > Hi, > >> This wasnt part of the vote, but I am also >> +1 for putting the upload procedure in a common.xml > > +1 > >> +1 for using Ivy for uploading > > +1 > >> +1 for including a src.zip into our dist

Re: [VOTE] use nexus for maven upload of ant release

Hi, > This wasnt part of the vote, but I am also > +1 for putting the upload procedure in a common.xml +1 > +1 for using Ivy for uploading +1 > +1 for including a src.zip into our distro (was asked by Brian on > https://issues.apache.org/jira/browse/INFRA-2706) >   I like getting information

AW: [VOTE] use nexus for maven upload of ant release

If using Nexus is the "official way" I am +1 for uploading Ant, Antlibs and Ivy. This wasnt part of the vote, but I am also +1 for putting the upload procedure in a common.xml +1 for using Ivy for uploading +1 for including a src.zip into our distro (was asked by Brian on https://issues.apache.or

Re: [VOTE] use nexus for maven upload of ant release

+1 to use nexus to upload ant, antlibs and ivy Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] use nexus for maven upload of ant release

Hi, > We should probably extract the steps into targets of the "common" build > infrastructure so each Antlib build will benefit from it instantly. +1 for this > >> Do we want to use nexus to upload our ant release to nexus > > Since the only other option seems to be to not publish to the Maven

Re: [VOTE] use nexus for maven upload of ant release

On 2010-05-13, Antoine Levy-Lambert wrote: > Brian Fox on the repository list has advised me to upload the ant > artefacts to the maven repository using nexus. [1] I wonder why it seems to get harder to get anything into the Maven repository if you don't use Maven to build with every release, oh