Re: release announcement text

On 2010-12-13, Antoine Levy-Lambert wrote: > - performance improvements in directory scanning > - XSLT task honors classpath again (bugrep 49271) > - distinction between core tasks and optional tasks is abolished > - numerous bug fixes and improvements as documented in Bugzilla > and in WH

Re: svnpubsub for the Ant and Ivy sites

On 2010-12-13, Nicolas Lalevée wrote: > So I suggest that we say to the infra team that our sites are there: > * https://svn.apache.org/repos/asf/ant/core/trunk/docs/ > * https://svn.apache.org/repos/asf/ant/ivy/site/target/ > and in our workflow we skip the last part of going on people.a.o and sv

[VOTE] release of ant 1.8.2

Hi, as announced I have built a release candidate for Ant 1.8.2. This is available for download from http://people.apache.org/~antoine/dist/ Do you want to release these artefacts as Apache Ant 1.8.2 ? Yes [] No [] Regards, Antoine --

Re: svnpubsub for the Ant and Ivy sites

On 12/13/2010 11:31 AM, Antoine Levy-Lambert wrote: So I suggest that we say to the infra team that our sites are there: * https://svn.apache.org/repos/asf/ant/core/trunk/docs/ I just switched to http://svn.apache.org/repos/asf/ant/core/branches/ANT_SITE/docs/ The reason is that I am about t

Fixed default target

Hey! I'm wondering if it's possible to have a fixed default target, which always executes instead of what's put on the command-line? The reason for this is we use the depends feature of ant to be able to for instance publish to an ivy repository with a better flow. ant local milestone publish. An

release announcement text

Hi, here are the items I plan to indicate as key features of 1.8.2 - performance improvements in directory scanning - XSLT task honors classpath again (bugrep 49271) - distinction between core tasks and optional tasks is abolished - numerous bug fixes and improvements as documented in Bugzilla

Re: [GUMP@vmgump]: Project ivy-tests (in module ivy) failed

On 2010-12-13, Nicolas Lalevée wrote: > If it happens again, do we have rights to commit there ? Yes, every ASF committer has full access to Gump's metadata. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For a

Re: svnpubsub for the Ant and Ivy sites

On 12/13/2010 11:21 AM, Nicolas Lalevée wrote: As you may know, the infra team has developed a CMS [1]. I am not suggesting to change the way we are editing our doc and use this new CMS, because actually our workflow to publish content on the web is very close to the CMS one. In Ant: * we edit

svnpubsub for the Ant and Ivy sites

As you may know, the infra team has developed a CMS [1]. I am not suggesting to change the way we are editing our doc and use this new CMS, because actually our workflow to publish content on the web is very close to the CMS one. In Ant: * we edit some file if xdocs and commit them * we generate

Re: [GUMP@vmgump]: Project ivy-tests (in module ivy) failed

Le 13 déc. 2010 à 16:34, Stefan Bodewig a écrit : > On 2010-12-13, Nicolas Lalevée wrote: > >> The build is failing because now some ant task in the build needs >> ant-contrib. > > OK, now I see it, thank you. > >> From what I understand from Gump, it is intended to test the projects >> interd

Re: [GUMP@vmgump]: Project ivy-tests (in module ivy) failed

On 2010-12-13, Nicolas Lalevée wrote: > The build is failing because now some ant task in the build needs > ant-contrib. OK, now I see it, thank you. > From what I understand from Gump, it is intended to test the projects > interdependencies and backward compatibility. Then about the > integrati

Re: [GUMP@vmgump]: Project ivy-tests (in module ivy) failed

The build is failing because now some ant task in the build needs ant-contrib. To automatically get ant-contrib, I made the target depends on the "resolve" target which will via Ivy get the proper ant-contrib jar. Since this build is explicitly specifying "no.resolve=true", ant-contrib is then n

AW: AW: Ant 1.8.2 build next week

> > Should we move the P4-tasks to the Antlib (for later retiring) before > the release? > > > > Jan > I would rather wait and do it right after the release. We can announce > in the release message that the next release will not include the P4 > tasks. > > Antoine Ok. Jan

Re: AW: Ant 1.8.2 build next week

On 12/13/10 6:21 AM, Jan Matèrne wrote: Should we move the P4-tasks to the Antlib (for later retiring) before the release? Jan I would rather wait and do it right after the release. We can announce in the release message that the next release will not include the P4 tasks. Antoine -Urspr

AW: Ant 1.8.2 build next week

Should we move the P4-tasks to the Antlib (for later retiring) before the release? Jan > -Ursprüngliche Nachricht- > Von: Stefan Bodewig [mailto:bode...@apache.org] > Gesendet: Montag, 13. Dezember 2010 10:23 > An: dev@ant.apache.org > Betreff: Re: Ant 1.8.2 build next week > > On 2010-1

Re: Ant 1.8.2 build next week

On 2010-12-10, Antoine Levy-Lambert wrote: > if no one objects, I would like to build ant 1.8.2 next week, likely > on Monday (12/13), so the official release would then be 12/20. Sounds good. > I have seen various nags of people who have entered bug reports [1] > [2] in Bugzilla and would like

Re: Bug 50200, VectorSet kills the performance of DirectoryScanner

On 2010-12-13, Antoine Levy-Lambert wrote: > Hi, > I got a private email asking me to apply the patch suggested by > *Bug 50200* - [1] > VectorSet kills the performance of DirectoryScanner > The code looks good and I am wondering w