Re: [VOTE] EOL Apache Ant 1.9.x release series
+1 Martijn Op 16/06/2024 om 14:47 schreef Nicolas Lalevée: +1 Nicolas Le 16 juin 2024 à 08:10, Jaikiran Pai a écrit : Hello everyone, 4 years back in 2020, we initiated an vote to EOL 1.9.x release versions of Apache Ant. We didn't receive enough votes at that time to formalize it (which is OK). The last release of Ant 1.9.x release series was back in 2021 and that was a security fix. The Ant 1.9.x branch hasn't seen any recent commits in around 2 years. At the same time the Ant master branch from where we do the 1.10.x release has been active with bug fixes and relatively smaller enhancements. We have been releasing Ant 1.10.x regularly too. Ant 1.9.x allows Java 5 as a runtime whereas Ant 1.10.x requires Java 8 as the minimal runtime. The support for Java 5 has been the sole reason why the last few times we proposed EOLing 1.9.x, the vote didn't pass. Having said that, I (one of the release managers of Ant) haven't had access to Java 5 for several years now. Plus, Ant 1.9.x doesn't have several of the bug fixes that have gone into Ant 1.10.x since the past several years. The decision to not backport bug fixes from 1.10.x into 1.9.x has been intentional, it not easy to maintain Java 5 compatibility for code changes, plus the development time and testing time for such backports isn't something that we wanted to invest in. So effectively, Ant 1.9.x currently lacks features and fixes when compared to 1.10.x. Given all this, I would like to officially call for vote to EOL 1.9.x releases. What that would mean is that there won't be any more Ant 1.9.x releases. Ant 1.9.16, the last release in this 1.9.x series, 3 years back, would officially be the last one. If users do want to use that version, they can continue to do so by getting it from the usual Apache Ant download page. Having EOLed 1.9.x, the Ant team can then solely focus on 1.10.x and that makes it much more simpler to deal with managing the project infrastructure as well as code changes. As usual, please cast your vote by replying to the list. This vote will close in 72 hours, no earlier than 19 June 2024, 06:30 UTC. -Jaikiran - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Retire the IvyDE Subproject
Op 23/11/2023 om 08:19 schreef Stefan Bodewig: I'm really sorry and embarrassed but I seem to have misunderstood the purpose of the Attic, it is not responsible for retiring subprojects, only for top level projects like Ant as a whole with all subprojects. The correct process to follow is https://ant.apache.org/processes.html#Retire%20a%20subproject%20or%20component This is a new vote as I do not want to assume I could transfer the votes of a different vote and repurpose them. The actual vote: Following our own rules I propose zo retire IvyDE. Vote will be open for at lease 72 hours, will not end before 2023-11-26T07:30 UTC Sorry Stefan +1 Martijn
Re: [VOTE] Send IvyDE to the Apache Attic
+1 Martijn Op 20/11/2023 om 04:50 schreef Jaikiran Pai: On 19/11/23 11:09 pm, Stefan Bodewig wrote: ... So here is the formal vote: I hereby propose to create a board resolution that will send IvyDE to the Apache Attic. +1 -Jaikiran - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Release Apache Ant 1.10.13 based on RC1
+1 checked diff to of indicated commit to rel/1.10.12 Martijn Op 09/01/2023 om 02:30 schreef Jaikiran Pai: +1 Tried the new version to build some existing projects - worked fine Checked NOTICE file and some random manual docs - looks fine -Jaikiran On 06/01/23 4:57 pm, Stefan Bodewig wrote: On 2023-01-04, Jaikiran Pai wrote: Happy new year, everyone :) to you as well I've created RC1 release candidate for Ant 1.10.13 release: git tag: ANT_1.10.13_RC1 on commit: 6996b80b5fb59cc2769f7098d837de32680a tarballs: https://dist.apache.org/repos/dist/dev/ant/ +1 Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Release Iyv 2.5.1 Based on RC1
+1 Martijn Op 03/11/2022 om 12:56 schreef Jaikiran Pai: +1 - Downloaded the apache-ivy-2.5.1-bin.tar.gz. - Installed locally. - Ran java -jar $IVY_HOME/ivy-2.5.1.jar -version (correct version reported) - Then built a few existing projects with this version and they passed - Checked some docs in the "doc" folder and they looked fine. -Jaikiran On 01/11/22 3:40 pm, Stefan Bodewig wrote: Hi all I've built a release candidate for Ivy 2.5.1 Changelog: - BREAKING: Removed old fr\jayasoft\ivy\ant\antlib.xml AntLib definition file (jira:IVY-1612[]) - FIX: ResolveEngine resets dictator resolver to null in the global configuration (jira:IVY-1618[]) - FIX: ConcurrentModificationException in MessageLoggerHelper.sumupProblems (jira:IVY-1628[]) - FIX: useOrigin="true" fails with file-based ibiblio (jira:IVY-1616[]) - FIX: ivy:retrieve Ant task didn't create an empty fileset when no files were retrieved to a non-empty directory (jira:IVY-1631[]) - FIX: ivy:retrieve Ant task relied on the default HTTP header "Accept" which caused problems with servers that interpret it strictly (e.g. AWS CodeArtifact) (jira:IVY-1632[]) - IMPROVEMENT: Ivy command now accepts a URL for the -settings option (jira:IVY-1615[]) The release artifacts can be found at https://dist.apache.org/repos/dist/dev/ant/ivy/ (svn revision 57703) Maven Repo is https://repository.apache.org/content/repositories/orgapacheant-1055/org/apache/ivy/ivy/2.5.1/ I have not built the update site because I couldn't get the build process to work, so if anybody with the proper build environment wants to create one, thank you. I'm sure we can create it after the release if we want to. Do you vote for the release of these binaries? [ ] Yes [ ] No This vote will be open for 72 hours as usual, I'll close it on 2022-11-04 10 UTC. Thanks Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Release Apache Ant 1.10.11 based on RC1
Hi I Reviewed the changes. If the https://github.com/apache/ant/blob/master/src/main/org/apache/tools/ant/UnknownElement.java changes address an Time Of Destruction / Time of Use issue it should work. If "realThing" is created / changed from another threat the changes (or even the initial object) may not be visible from the other threads (even if the reference to the object is). This code in itself is NOT thread safe. Given the report was on a Time Of Destruction error it could help. Notwithstanding +1 Br Martijn Op 10/07/2021 om 20:51 schreef Stefan Bodewig: Hi all I've created a release candidate for 1.10.11: git tag: ANT_1.10.11_RC1 on commit: 01ce0c3b1 tarballs: https://dist.apache.org/repos/dist/dev/ant/ revision: 48767 Maven artifacts: https://repository.apache.org/content/repositories/orgapacheant-1049/org/apache/ant/ Cheers Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Release Apache Ant 1.9.15 based on RC1
Reviewed changes +1 br Martijn Kruithof Op 10/07/2021 om 20:13 schreef Stefan Bodewig: Hi all I've created a release candidate for 1.9.16: git tag: ANT_1.9.16_RC1 on commit: ea698c454 tarballs: https://dist.apache.org/repos/dist/dev/ant/ revision: 48766 Maven artifacts: https://repository.apache.org/content/repositories/orgapacheant-1049/org/apache/ant/ Cheers Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: AW: [VOTE] Release Apache AntUnit 1.4.1 based on RC1
Reviewed changes based on tag 1.4.1 RC1 vs tag 1.4 Given the compatibility claims I tried to test against ant-1.8.1 and jdk 1.5 in wich case test cases using URLs are failing. The failing of these test are probably caused by jdk 1.5 not supporting tls 1.2 which is minimally required nowadays. Notwithstanding +1 Br Martijn Op 04/07/2021 om 14:54 schreef apa...@materne.de: Downloaded src+bin.zip and did some tests. All fine. +1 Jan -Ursprüngliche Nachricht- Von: Maarten Coene Gesendet: Sonntag, 4. Juli 2021 12:17 An: Ant Developers List Betreff: Re: [VOTE] Release Apache AntUnit 1.4.1 based on RC1 +1 Maarten Op zaterdag 3 juli 2021 14:41:50 CEST schreef Stefan Bodewig : Hi all I've created a release candidate for AntUnit 1.4.1: git tag: 1_4_1_RC1 on commit: e436acf tarballs: https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit/ revision: 48645 Maven artifacts: https://repository.apache.org/content/repositories/orgapacheant-1048/org/apache/ant/ant-antunit/1.4.1/ This Vote will be open at least for 72 hours and close no earlier than 2021-07-06 13:00UTC. Cheers Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
RE: [VOTE] Release Apache Ant 1.10.9 based on RC1
Performed manual review only +1 But: - Fixed 2 typo's found (committed to master) - should reference to Rhino being available in java 7 runtime be removed from the manual (script.html) and should the system requirements in install be updated to reflect 1.10 series requires jdk 8? (preparing pull request) - Should a reference to use Rhino (which has been updated recently) be added as well? it is referenced from a lot of other places on the script manual page? Best Regards Martijn -Oorspronkelijk bericht- Van: Jaikiran Pai Verzonden: dinsdag 29 september 2020 17:34 Aan: Ant Developers List ; Stefan Bodewig Onderwerp: Re: [VOTE] Release Apache Ant 1.10.9 based on RC1 +1. - Downloaded apache-ant-1.10.9-bin.tar.gz - Checked the NOTICE file - Check some of the manuals in the downloaded binary - Built some internal projects using this new version All went fine. -Jaikiran On 27/09/20 3:58 pm, Stefan Bodewig wrote: > Hi all > > as mentioned in my last mail the release contains a decision about > implementing Nashorn support for graal.js that hasn't been discussed > before. Please don't hesitate voting -1 if you disagree with the way I > did. > > I've created a release candidate for 1.10.9: > > git tag: ANT_1.10.9_RC1 > on commit: 15686e56d > tarballs: https://dist.apache.org/repos/dist/dev/ant/ > revision: 41602 > Maven artifacts: > > https://repository.apache.org/content/repositories/orgapacheant-1046/o > rg/apache/ant/ > Snapcraft Build > Revision 17 in latest/candidate > > This Vote will be open at least for 72 hours and close no earlier than > 2020-09-30 10:30UTC. > > Cheers > > Stefan > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional > commands, e-mail: dev-h...@ant.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Release Ant 1.10.7 based on RC1
Hi +1 from me I have compared contents of the archives amongst each other, and the jar files in the lib directory with an independent build based on 9c656cc1040948412db0bb0d9ed55b2d06084a34 and have not noted any significant / unexpected differences. re-ran the testset using JDK 8 and the ant released Please note, commit 80768efaab4003d90252095d160facfc35adc35e and the tag are not visible (yet) Martijn Kruithof On 02-09-19 07:07, Jaikiran Pai wrote: +1. - Downloaded the .tar.gz binary - Installed it and checked the NOTICE file. - Random check of some manuals - Built some internal projects using this new version - Verified that the issue noted in https://bz.apache.org/bugzilla/show_bug.cgi?id=63457 is fixed in this version, by running the code attached to that issue, with this newer version. - Verified the sha512 checksum for the -bin.tar.gz is correct. -Jaikiran On 01/09/19 5:40 PM, Jaikiran Pai wrote: Hello all, I've created a release candidate RC1 for Ant 1.10.7 release. This release is mostly a bug fix release with just a couple of minor enhancements. The release was built using JDK 11 version (to include JDK9+ features/tasks). The minimal required version of Java runtime, to use this Ant release, still remains Java 8. This is the first release where we are publishing our Ant artifact(s) as a "snap" to https://snapcraft.io/. Details on how to access this release candidate version of the snap is mentioned below. Release notes: https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.7.html git tag: ANT_1.10.7_RC1 on commit 80768efaab4003d90252095d160facfc35adc35e tarballs: https://dist.apache.org/repos/dist/dev/ant/ revision 35487 Maven artifacts: https://repository.apache.org/content/repositories/orgapacheant-1039/org/apache/ant/ Snapcraft artifact: Available at https://snapcraft.io/ant as version "1.10.7" under the "latest/candidate" channel This vote will be open for at least 72 hours and will not close before 4th September 2019 12:00 UTC. -Jaikiran - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Augmenting the ant wrapper script for OS packaging
+1 On 12-06-19 07:16, Jaikiran Pai wrote: On 11/06/19 9:54 PM, Stefan Bodewig wrote: I'm a bit torn but would prefer adding it to the default script so that running Ant would use the same wrapper no matter how you've installed it. I'm afraid we'd have to ask people "how have you installed Ant" otherwise. +1. Given that the startup script already does a bunch of things to locate a Java installation and the fact that what you are proposing seems to be pretty reasonable in terms of finding the "Snap JVM", I think it's good to have it in the default script. -Jaikiran - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Jean-Louis Boudart as a PMC member
Conor MacNeill schreef op 26-11-2013 19:47: On 26 November 2013 22:04, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Jean-Louis has been around for a very long time, owned committership, contributed a lot to bring EasyAnt into the Ant PMC, and he is participating to the vote in the release process. Thus, let's invite Jean-Louis to be part of the PMC. Here is my +1. +1 Conor +1 Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Charles Duffy as a committer
+1 Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Michael Clarke as a committer
[X] +1 to add Michael Clarke as a committer Martijn Kruithof - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Ant 1.9.0 release [2nd attempt]
+1 Martijn Op 11-3-2013 15:05, Peter Reilly schreef: +1 Peter On Sun, Mar 10, 2013 at 9:30 AM, Jean-Louis Boudart jeanlouis.boud...@gmail.com wrote: +1 on the release as is too Works perfectly in easyant :) 2013/3/9 Stefan Bodewig bode...@apache.org +1 on the release as is. On 2013-03-08, Antoine Levy Lambert wrote: You can veto the release if it matters that much to you and I would then have to drop and recreate the 1.9.0 label and do a new build. Maybe I'm picking nits: you can't veto a release, this is a majority vote. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org -- Jean Louis Boudart Independent consultant Apache EasyAnt commiter http://incubator.apache.org/easyant/ - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Release Ant 1.8.4
Op 22-5-2012 9:12, Stefan Bodewig schreef: On 2012-05-22, Stefan Bodewig wrote: I would like to release Ant 1.8.4. Ant 1.8.4 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/ant/ The tag is here: http://svn.apache.org/repos/asf/ant/core/tags/ANT_184/ +1 Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Drop JDK 1.4 after 1.8.3
+1 (w move to 1.9) Martijn Op 30-1-2012 11:22, Peter Reilly schreef: + 1 and move to 1.9 Yey, we may even dabble in these new fangled generics Peter On Mon, Jan 30, 2012 at 8:40 AM, Dominique Devienneddevie...@gmail.com wrote: On Sat, Jan 28, 2012 at 6:54 AM, Stefan Bodewigbode...@apache.org wrote: On 2012-01-27, Jesse Glick wrote: As suggested in 1.8.3 thread, I propose we drop JDK 1.4 support in trunk after Ant 1.8.3 is released. It is long past EOL http://www.oracle.com/technetwork/java/eol-135779.html and cumbersome to even get installed for testing. (Note that JDK 5 is also past EOL, but I am not proposing dropping JDK 5 support in this vote.) +1 for dropping Java 1.4 support in trunk after 1.8.3. I'm with Maarten that we should switch to 1.9.0 in trunk then. +1. --DD - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Sponsor of EasyAnt
+1 Martijn On 4-1-2011 15:59, Antoine Levy-Lambert wrote: Hi, I am voting +1 for the proposal and volunteering to be the champion. Regards, Antoine On 1/4/2011 8:53 AM, Nicolas Lalevée wrote: Let's start this year with formal vote about Apache Ant being the sponsor for EasyAnt to enter the Apache incubator. The proposal has been prepared there: http://easyant.org/projects/easyant/wiki/ApacheProposal As you may note, I'm not a Champion. I have discussed with some friends which happen to be members of the ASF. At some point they thought me being a Champion would be a good fit, as suggested very earlier Antoine. As I replied to Antoine, the documentation says I don't have enough karma for a such title. We tried to dig this with my friends but it seems like a dead end. I conclude that for now I won't be a Champion. I'll probably raise the subject again while discussing the proposal on the incubator mailing list. So do we agree to sponsor EasyAnt to enter the Incubator ? Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: AW: Can Anybody Fix our Logos?
On 17-11-2010 18:21, Jan Matrne wrote: Does anybody have a correct Apache logo (with the "tm")? I haven't found any for using as "inspiration" ... Jan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org Oh irony, not even the page having the instruction has a small TM in the logo. Well I've given it a try (using paint).
Re: [VOTE] Accept Bushel Donation
On 5-11-2010 15:45, Stefan Bodewig wrote: So, do we want to accept the Bushel donation? +1 Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Release Apache Compress Antlib 1.0
+1 maybe we should add an installation instruction. Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] IvyDE 2.1.0 Release
On 2010-08-11, Nicolas Lalevée wrote: Do you vote for the release of these binaries? [ ] Yes [ ] No +1 Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Release Manuals of Last Five Ant Releases
+1
On 19-7-2010 16:21, Stefan Bodewig wrote:
Hi,
I don't really think this requires a vote since I've just repackaged
existing distributions (see buildfile at the end of the mail for
details), but it won't hurt.
Inhttp://people.apache.org/~bodewig/manual/ there are ZIP and
tar.gz/bz2 files containing the manuals of the releases 1.6.5 to 1.8.1.
The contents are similar to the manual tarballs that will be created by
the distribution target in trunk's build.xml.
I'd like to release those to the public, so please cast your vote:
[ ] +1 release them
[ ] 0 don't care
[ ] -1 no, don't release them
The plan is to create a manual directory inside Ant's distribution area
right next to the source and binaries directories and copy over all
files fromhttp://people.apache.org/~bodewig/manual/. In addition I'd
create -current symlinks just like we have for source and binaries.
Once the mirrors have picked up all files I'd delete the archives for
1.6.5 to 1.8.0 so they remain on archives.apache.org only.
Furthermore I'll add a new download page for the manual and link to it
from the cover page (if you are looking for an older version ...) and
the API docs page (if you are looking for javadocs ...) of the Ant
website.
Stefan
PS: this is how I created the files, most of it stolen from trunk's
build.xml.
project
mkdir dir=work/
macrodef name=checksums-mvn description=only md5 and sha1 are needed for the
maven directory structure
element name=resources implicit=true/
sequential
checksum algorithm=md5
resources/
/checksum
checksum algorithm=sha1
resources/
/checksum
/sequential
/macrodef
macrodef name=checksums
element name=resources implicit=true/
sequential
checksums-mvn
resources/
/checksums-mvn
checksum fileext=.sha512 algorithm=sha-512
resources/
/checksum
/sequential
/macrodef
macrodef name=get-and-zip
attribute name=version/
sequential
get
src=http://archive.apache.org/dist/ant/binaries/apache-a...@{version}-bin.tar.bz2;
dest=work/
untar src=work/apache-a...@{version}-bin.tar.bz2 dest=work
compression=bzip2/
mkdir dir=work/manual/
zip destfile=work/manual/apache-a...@{version}-manual.zip
zipfileset dir=work/apache-a...@{version}/docs/manual
prefix=apache-a...@{version}/
zipfileset file=work/apache-a...@{version}/NOTICE
prefix=apache-a...@{version}/
/zip
tar longfile=gnu
destfile=work/manual/apache-a...@{version}-manual.tar
tarfileset dir=work/apache-a...@{version}/docs/manual
prefix=apache-a...@{version}/
tarfileset file=work/apache-a...@{version}/NOTICE
prefix=apache-a...@{version}/
/tar
gzip destfile=work/manual/apache-a...@{version}-manual.tar.gz
src=work/manual/apache-a...@{version}-manual.tar/
bzip2 destfile=work/manual/apache-a...@{version}-manual.tar.bz2
src=work/manual/apache-a...@{version}-manual.tar/
delete file=work/manual/apache-a...@{version}-manual.tar/
/sequential
/macrodef
get-and-zip version=1.6.5/
get-and-zip version=1.7.0/
get-and-zip version=1.7.1/
get-and-zip version=1.8.0/
get-and-zip version=1.8.1/
checksums
fileset dir=work/manual/
exclude name=**/*.asc/
exclude name=**/*.md5/
exclude name=**/*.sha1/
exclude name=**/*.sha512/
/fileset
/checksums
/project
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Remove commercial tasks from Ant
On 19-6-2010 20:38, Bruce Atherton wrote: Ant supplies several tasks that require commercial software in order to run. This is a problem because the Ant developers do not typically have access to the commercial products required to test, maintain, and enhance the tasks. It also means that users downloading the binary edition of Ant end up with a lot of tasks that they cannot use. In order to rectify this situation, I'm calling a vote on how to deal with these unsupportable tasks. The vote is composed of two parts: should we drop support for each of these tasks from the Ant release, and should we establish the commercial tasks that have been dropped as Antlibs in the sandbox. 1. Should the following commercial tasks be dropped from being distributed with the Ant release? [ ] Continuous/Synergy tasks: CCMCheckin, CCMCheckout, CCMCheckinTask, CCMReconfigure, CCMCreateTask [ ] Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate, CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr, CCMkdir, CCMkelem [ ] Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have, P4Label, P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete, P4Integrate, P4Resolve, P4Fstat [ ] PVCS [ ] ServerDeploy, but only for the jonas and weblogic nested elements, generic can stay where it is. [ ] Source Offsite: sosget, soslabel, soscheckin, soscheckout [ ] Microsoft Visual SourceSafe (already an Antlib) +1 2. Should the commercial tasks that are voted for dropping from Ant core above be established in their own Antlibs in the sandbox? [ ] +1 = Yes, establish one new Antlib in the sandbox for each task dropped -1 = No, just drop the commercial tasks altogether from Ant Note that question 1 is a vote for code modification, so any -1 vote on question 1 is considered a veto. Question 2 is just for guidance from the community about whether there is a desire to keep the commercial tasks around in Antlibs. Since any committer can create a sandbox Antlib at any time, the vote is non-binding and any -1 vote just indicates that the voter does not think that this is a good idea rather than being a veto. +1 Three or more +1 votes with no -1 votes are required for dropping any of the commercial tasks. The vote will end in one week. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Ant source tree reorganization
On 18-5-2010 4:11, Jesse Glick wrote: Should the Ant source tree (src/main/ and perhaps also src/tests/) be split into subtrees? [ ] No, leave it the way it is - one big tree, using selector to conditionally compile pieces and route classes to various JARs. [ x ] Yes, split it into subtrees, where each tree maps to an output JAR, may have its own classpath, and is compiled completely or not at all. And while we're at it: Should ant.jar and ant-nodeps.jar be consolidated? [ ] No, leave these as two JAR outputs (and two subtrees if the first proposal is accepted). [ x ] Yes, merge them into one ant.jar (and one subtree ), to include all tasks and types with no linkage-level deps on 3rd-party libraries (even if there is an implicit dep on a 3rd-party tool such as Perforce), and remove the Core vs. Optional distinction in the manual. (Could prepare these changes on a branch if people would rather look at the result before voting.) - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - 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
+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] release of ant 1.8.1
On 4-5-2010 14:53, Stefan Bodewig wrote: On 2010-05-01, Antoine Levy-Lambertanto...@gmx.de wrote: Vote to release this build as ant 1.8.1 [X] Yes [ ] No +1 martijn No problems observed - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [POLL] Bug 48804
I agree, however it may be good to update the 1.8.0 manual with a warning that the behavior is currently not as intended and will change, published as soon as the solution is changed. br martijn On 23/04/2010 2:29 AM, Stefan Bodewig wrote: Hi all, currently extension-point and import don't play together like they are supposed to. You can't extend an imported extension point with a target from the importing build file (which is the primary use-case, really). Attached to this bug is a patch that fixes the problem (including an AntUnit test that fails in 1.8.0). The same patch breaks a different AntUnit test, namely testExtensionPointMustBeKnown in extension-point-test.xml. This test asserts that you can't extend an extension point from the same build file before that extension point has been defined. I.e. you can't do target name=bar extensionOf=foo/ extension-point name=foo/ Personally I think the changed behavior isn't a bad thing, the old behavior isn't documented and we shouldn't even try to keep it. What do you think? Stefan PS: I'd love to see this fixed with Ant 1.8.1. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [Vote] Augment feature
Hello I have quite some difficulties with the discrepancy of the name of the task and that what the task is about to do. Therefore, using the current name and functionality I would cast a -0,5 vote, as i do not want to be blocking. I can see the desire for a task that changes predeclared id's. My objection against the current name comes from the fact that the task not only augments (basically adds, increases, stretches, enlarges etc.) things but it is used to change the path at will. On the other hand I think free modification of references seems like a giant pitfall in the following situations: - when used in combination with parrallel - when related tasks in a script expect the same elements present on the path If the augment task was used to do only what its name implies (extend) and not to reduce less problems could be expected. Therefore I would be in favour of an augment feature if it can only be used to augment (and not change at will). On 14-4-2010 0:34, Bruce Atherton wrote: Ok, so this didn't start out as a vote thread, just my suggestion for what questions should appear in the vote. But since it has morphed into that I've changed the subject line to make it easier for people to find. So the questions are: 1. Are you in favor of adding the augment feature to Ant? -0,5 : Non blocking negative look. +1 if augment is only used to augment (increase, extend, combine, add to the existing) 2. Are you in favor of an attribute that allows references to be marked as final, to avoid augmentation? 3. If a final attribute is decided upon, do you think it should default to false? If you have already voted, no need to recast your vote. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [POLL] update of ant's web site (and Ivy's?)
On 11-2-2010 17:12, Stefan Bodewig wrote: If we put work into creating a branch for the website, then it should save us at least some work (the update of the site), so, yes. Count this at least as a +0.5;-) It is not like the current way of publishing would seize to function when we use a separate branch for the website. What would be the effort to using svnpubsub vs the current mechanism? (updating the frequency is a no-brainer, and doesn't take much resources). The current frequency is daily, the website is updated hourly so anything more frequent than that is not adding much speed to the publishing process. (count this as +1 for a separate branch, and a request for more info on the benefits of using svnpubsub in our environment.) Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] [second attempt] release of ant 1.8.0
On 2-2-2010 2:12, Antoine Levy Lambert wrote: The new build incorporates the fix for the junit stack traces issue. a candidate for ant 1.8.0 is available under http://people.apache.org/~antoine/dist/apache-ant-1.8.0/ Vote [x] Release as Apache Ant 1.8.0 [] Do not release yet +1 Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] release ant 1.8.0RC1
Hi I am +1 on releasing this build 2 questions though: Is it correct that no pom files are present for ant-apache-xalan2.jar in the lib directory? Is it correct that pom files are present for ant-parent and ant-stylebook although no jar files are present? Br Martijn Jesse Glick wrote: Antoine Levy Lambert wrote: [X] release this build as ant 1.8.0RC1 [ ] do not release this build I have played with it for a while in the context of NetBeans (building all IDE sources, and using various Ant-based project types inside the IDE), and have not found any regressions so far. Checked on Ubuntu and XP. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] name for target-group
I would be in favour of using targetgroup name=foo and target group=foo or even group name=foo and target group=foo the dash in the name is not something we usually do in ant Martijn Antoine Levy Lambert wrote: Hi, I would like to start a formal vote on the name of target-group. [ ] target-group name=foo/ for the group and target group=foo ... for the members of the group this is the current codebase [ ] extension-point name=foo/ for the group and target extensionOf=foo ... for members of the group [ ] others Regards, Antoine - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Accept Groovy-Front Donation
Hi a +1 from me Martijn Stefan Bodewig wrote: Hi, Nicolas wants to donate his ProjectHelper implementation that allows build files to be written in Groovy. It can be found attached to https://issues.apache.org/bugzilla/show_bug.cgi?id=48347 It would start life at Ant inside the sandbox. Since this is more than just a small patch, following the IP-Clearance process[1] which involves the incubator seems in order. I volunteer to see this through the Incubator process. But before I start doing this: do we want to accept the donation? Stefan [1] http://incubator.apache.org/ip-clearance/index.html http://incubator.apache.org/ip-clearance/ip-clearance-template.html - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Accept Groovy-Front Donation
+1 Martijn Bruce Atherton wrote: +1. Stefan Bodewig wrote: Hi, Nicolas wants to donate his ProjectHelper implementation that allows build files to be written in Groovy. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Promote the Compress Antlib
Stefan Bodewig wrote: Hi all, the compress Antlib which provides cpio and ar archiving and unarchiving tasks in addition to alternative tar, zip, bzip2 and gzip tasks is functionally more or less complete and I'd like to release it shortly after 1.8.0 since it addresses a few bugzilla issues for the core tasks as well. As a first step I propose to promote the Antlib from the sandbox to a proper Antlib. Stefan +1 Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Promote the props Antlib out of the Sandbox
+1 Martijn --- On Wed, 9/30/09, Stefan Bodewig bode...@apache.org wrote: From: Stefan Bodewig bode...@apache.org Subject: [VOTE] Promote the props Antlib out of the Sandbox To: dev@ant.apache.org Date: Wednesday, September 30, 2009, 3:54 AM Hi all, IMHO the new PropertyHelper API can be used to solve quite a few scripty things in a cleaner way and the props Antlib provides a some implementations that people could leverage. Therefore I propose to promote it out of the sandbox (the later goal would be to release a 1.0 version of it close to Ant 1.8.0). Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
debug when using ant-unit
Hello I am trying to test the adaptet get task using antunit, but I keep getting failures i cannot explain I do run the testcase in a simple build file without using antunit and the log does contain the correct line, when running from antunit the assertLogContains does not match. Is there any way to see the log of the task running inside antunit? Similar issue for a failure, when running independent of antunit I do see the BuildException with the message wanted, when running from antunit, another exception is claimed to be thrown (with another message). How do I troubleshoot these issues using antunit? Br Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: dev-list etiquette questions
Best way to contribute a patch is to create a bug report (in this case bugzilla). The title of the bug report should start with [Patch]. This is currently not documented well. br Martijn Hi Ant guys, I have a couple of etiquette questions, 1/ how do I contribute a patch? (or where can I find the info?) 2/ do you use subject prefixes on this list? (my 1st patch will be for for antlibs/svn) Thx in advance, d. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Giving the improved bzip2 code a second chance?
+1 from me too, Martijn - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: help needed with clearantlib
Seems like an maven error on an 3rd party component with instructions to
install yet another 3rd party component.
Please contact either the maven or the clearantlib user list (that if
the error persists after installing checkstyle)
br Martijn
meher03 schreef:
Hi , I am getting the following error installing clearantlib. Can anyone
please
help. Thank You
BUILD FAILED
C:\clearantlib-bin-1.2\build.xml:26: Unable to resolve artifact: Missing:
--
1) checkstyle:checkstyle:jar:${checkstyle.version}
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=checkstyle -DartifactId=checkstyle \
-Dversion=${checkstyle.version} -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=checkstyle -DartifactId=checkstyle \
-Dversion=${checkstyle.version} -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) unspecified:unspecified:jar:0.0
2) checkstyle:checkstyle:jar:${checkstyle.version}
2) junit:junit:jar:${junit.version}
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=junit -DartifactId=junit \
-Dversion=${junit.version} -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=junit -DartifactId=junit \
-Dversion=${junit.version} -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) unspecified:unspecified:jar:0.0
2) junit:junit:jar:${junit.version}
--
2 required artifacts are missing.
for artifact:
unspecified:unspecified:jar:0.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Re: svn commit: r739577 - /ant/core/trunk/src/main/org/apache/tools/ant/property/NullReturn.java
Doubted it, checked it and it returned NullPointerException.
D:\type Test.java
public class Test
{
public static void main(String[] args)
{
System.out.println(String.valueOf(null));
}
}
D:\java Test
Exception in thread main java.lang.NullPointerException
at java.lang.String.init(Unknown Source)
at java.lang.String.valueOf(Unknown Source)
at Test.main(Test.java:6)
br Martijn
Matt Benson schreef:
I always thought String.valueOf(null) returned null.
Was I on crack?
-Matt
P.S. Good to see you committing, Martijn...
--- j...@apache.org wrote:
Author: jkf
Date: Sat Jan 31 17:10:50 2009
New Revision: 739577
URL:
http://svn.apache.org/viewvc?rev=739577view=rev
Log:
Original toString would always throw a NPE.
Modified:
ant/core/trunk/src/main/org/apache/tools/ant/property/NullReturn.java
Modified:
ant/core/trunk/src/main/org/apache/tools/ant/property/NullReturn.java
URL:
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/property/NullReturn.java?rev=739577r1=739576r2=739577view=diff
==
---
ant/core/trunk/src/main/org/apache/tools/ant/property/NullReturn.java
(original)
+++
ant/core/trunk/src/main/org/apache/tools/ant/property/NullReturn.java
Sat Jan 31 17:10:50 2009
@@ -33,6 +33,6 @@
* {...@inheritdoc}
*/
public String toString() {
-return String.valueOf(null);
+return null;
}
}
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Adopt Java 1.4 as a minimum requirement for core/trunk
+1 for 1.8 / main doubting if it is a good idea for 1.7.x if we would make another one. Martijn Stefan Bodewig schreef: This is not that much based on features available (although I consider using NIO in StreamPumper) but more on where do we test. The vote is simple. If you vote +1 then we make 1.4 the minimum requirement, if you vote -1 it will stay at 1.3. This is a code change and thus subject to lazy consensus (i.e. no -1). Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Java version required for trunk
Hello I know i have not been really active for some time now (changed house, then job) yet I manage to remember previous discussions. I still feel that the following reasoning is flawed: There has been some discussion about dropping support for Java 1.3 in trunk. One of the aguments against it was that 1.4 doesn't offer anything new and going from 1.3 to Java5 was too big a step. I do think the problem is that we cannot support a whole lot of java versions for every new version of ant, just because of the amount of work associated with testing it all. The choice should not only be based on what new language features are offered by a java version, but also the number of java version we have to test against. If companies/projects/products have a good reason to stay with older java versions, the older version of ant that is supported has done all this time, and I think we should expect from companies that stay with older java versions that these companies shall bear the consequence of not being able to run the newest ant. Maybe we should consider dropping java versions even somewhat faster, I don't see the point in supporting java versions that SUN does not support anymore for the general public. From the sun website: http://java.sun.com/products/archive/eol.policy.html Revised (Current) Java SE Support Road map Release Family GA Date EOL NotificationEOSLSupport Period 1.4 February, 2002 December, 2006 October 30, 20086 ½ years 5.0 May, 2004 April, 2008 October 30, 20095 ½ years 6 December, 2006 2009* 2010* 4 years* These dates seem to be reasonable to stop supporting the corresponding java release in an upcoming ant release (if ant 1.8 appears after october 30, 2008 the 1.8 range should support 5.0 and 6 and possibly 7) We in turn we could consider to prolong the life of the point releases for critical updates to have at lease one ant version operating with the java version upto the state EOSL from SUN. Bugs eligible to be solved on the point releases after a new major release has been done would have to come from customers running a java version that is not supported by a more recent ant release, running a java version that is still supported by SUN, these should also be real bugs, not feature requests, and the company shall have to test the ant release towards the old java version and provide us the logs, especially if we do not have the possibility to run the old java version anymore. (This because I am quite sure that in 10 years java 1.4 won't be running anymore on the current hardware and operating systems.) Java SE for Business support road map Release Family GA Date EOL Notification* EOL*EOSL* Support Period 1.4 February, 2002 April, 2008 April, 2013 April, 2018 16 years 5.0 May, 2004 June, 2009 June, 2014 June, 2019 15 years 6 December, 2006 June, 2011 June, 2016 June, 2021 15 years br Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] 1.7.1 Release now available for final testing
yes [x] (+1) no [ ] I performed some basic checks, here is my +1 Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release of Apache IvyDE 2.0.0.alpha1
On Wed, Jun 18, 2008 at 6:42 PM, Nicolas Lalevée [EMAIL PROTECTED] wrote: Hi, I am pleased to announce that I have a version of IvyDE ready to be released. You will find the files in my home directory on people.apache.org /home/hibou/ivyde-release Here is my +0 I have not been into ivy(ide) (yet) and currently heavily constrained on time (new job) hope to pick up some ant work again, as soon as the release of ant is done. Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] 1.7.1beta2
Ok +1 Martijn Kevin Jackson schreef: Hi, I've been informed (on the q.t) that I never actually requested a vote before announcing that the ant 1.7.1 beta tarballs were available. So officially at the moment, the tarballs on people.apache.org that I announced are beta-in-potentia :( A retrospective vote on these tarballs has been proposed, so Available tarballs at http://people.apache.org/dist/ant/v1.7.1beta2/ are ready: yes [ x ] (+1) no [ ] (-1) Thanks, Kev PS: my vote is included above - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Ant 1.7.1 beta
+1 Martijn Kevin Jackson schreef: Hi all, I think it's time to go ahead and push out 1.7.1 for wider testing. I really *don't* want to add any changes to code at the moment, but if there are any documentation issues that someone notices I'm willing to let them in on a case by case basis Over to the vote: Despite the strange bug Steve uncovered for networked drives on Windows, Ant 1.7.1 is ready for beta: Yes, I'll help (I need someone to sign with pgp) [ x ] (+1) Yes, go ahead but I won't help [ ] (+0) No, it's not ready [ ] (-1) Thanks, Kev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.7.1 - Beta Vote
+1 on the plan / releasing a beta Martijn Kevin Jackson schreef: Hi, As I mentioned previously (although I'm a couple of days late). I'd like to release a beta of 1.7.1 within the next two weeks. The current 1.7.1 trunk is now locked for further changes (99.9% test completion on the most troublesome platform (windows)) The beta of 1.7.1 is ready: [x] yes (+1) [ ] no (you missed something...) Kev PS - my +1 is already in the above :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: https://issues.apache.org/bugzilla/show_bug.cgi?id=41724
Marcelo Tancredi schreef: Hi, I am having the same problem here. What is the fix for this? Thanks - Marcelo Tancredi IBM Software Group - Boca Raton, Florida [EMAIL PROTECTED] Hi I have added a link to the fixed source in the bugrep in ant 1.7.1 the fix will be included. Further inquiries please via the ant developers list. br Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] add Nicolas Lalevée as committer
+1 Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bug In org.apache.tools.ant.util.FileUtils
Hi
this change was intentional, a bugrep was filed that under certain
circumstances the generated file name was used before it was created,
which could indeed not be ruled out. For situations where only a name is
needed the method createTempFileName was introduced.
I see your problem and have changed the solution to be backward
compatible on the FileUtils. The createTempFileName method has been
removed and a parameter has been added to the createTempFile method.
Martijn
Petar Tahchiev schreef:
Hi guys,
here is Petar Tahchiev from the Jakarta Cactus Team. I found that the
current version of
cactus's tasks cannot work with Ant 1.8.0alpha. When Trying to execute our
tasks I get this
exception:
java.io.FileNotFoundException:
/home/peter/workspace/Cactus/cactus13879tmp.dir/web.xml (Not a directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.init(FileOutputStream.java:179)
at java.io.FileOutputStream.init(FileOutputStream.java:131)
at org.codehaus.cargo.module.AbstractDescriptorIo.writeDescriptor(
AbstractDescriptorIo.java:110)
We are using FileUtils from Ant to create a temporary directory to store
some data, and the point is that
from some time the FileUtils's method createTemFile changed its body. Now it
is:
--
public File createTempFile(String prefix, String suffix, File parentDir,
boolean deleteOnExit) {
File result = null;
String parent = (parentDir == null)
? System.getProperty(java.io.tmpdir)
: parentDir.getPath();
try {
result = File.createTempFile(prefix, suffix, new File(parent));
} catch (IOException e) {
throw new BuildException(Could not create tempfile in +
parent, e);
}
if (deleteOnExit) {
result.deleteOnExit();
}
return result;
}
---
and it used to be:
---
public File createTempFile(String prefix, String suffix, File parentDir,
boolean deleteOnExit) {
File result = null;
String parent = (parentDir == null)
? System.getProperty(java.io.tmpdir)
: parentDir.getPath();
DecimalFormat fmt = new DecimalFormat(#);
synchronized (rand) {
do {
result = new File(parent,
prefix + fmt.format(Math.abs(rand.nextInt()))
+ suffix);
} while (result.exists());
}
if (deleteOnExit) {
result.deleteOnExit();
}
return result;
}
---
You see now the new file uses File.createTempFile to create the temp file.
And here comes the
problem, we use the createTempFile method to create directories. According
to the Javadoc API:
File.createTempFile - Creates an empty file in the default temporary-file
directory, using the given prefix and suffix to generate its name.
So every time it creates a file, instead of a directory, no matter if I say
tempFile.mkdirs(); !!!
I can implement the method I need myself, but I think that the clearer
approach would be, you guys to bring back
the old implementation of the method in the FileUtils, because there might
be some other guys that use
it to create a temporary folder.
Hope I explained it well and didn't confuse you.
Please let me know what you think, and keep me posted on CC, because I am
not subscribed to [EMAIL PROTECTED]
Thanks and have a good evening.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Ivy 2.0.0-beta1 (second attempt)
+1 Martijn -Original Message- From: Xavier Hanin [mailto:[EMAIL PROTECTED] Sent: jeudi 6 décembre 2007 7:34 To: Ant Developers List Subject: [VOTE] Release Ivy 2.0.0-beta1 (second attempt) I have built a new release candidate for Ivy 2.0.0-beta1 You can download it from this URL: http://people.apache.org/~xavier/ivy/staging/2.0.0-beta1/ http://people.apache.org/%7Exavier/ivy/staging/2.0.0-beta1/ and the m2 repository is here: http://people.apache.org/~xavier/m2-staging-repo/http://people.apache.org/%7Exavier/m2-staging- repo/ Compared to the previous release attempt I've only the following changes (which can be tracked in svn in the 2.0.0-beta1 branch): - merged a fix on cache locking (disabled by default) - merged some changes in makepom task to address Gilles remark - fix a bug on a unit test of makepom not done on trunk (still need to be merged to trunk) - reflect change to makepomin build-release.xml - package readme with all ditribs (including crypto notice) - put maven 2 distrib in a m2 staging repo for ease of testing I haven't done much testing of these artifacts, I had some slight troubles getting in my way (but when it takes 10 min to make a full release build a slight error can make you loose a lot of time), and it's getting really late over here, but I don't expect to have any more time for a new release attempt until next week, so if ever this one doesn't pass, I hope someone will step up to replace me as release mgr for this release. So, do you vote for the release of these binaries? [ ] Yes [ ] No Regards, Xavier, Ivy 2.0.0-beta1 release manager -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: [VOTE] Migrate Ivy SVN
Stefan Bodewig schreef: On Thu, 29 Nov 2007, Gilles Scokart [EMAIL PROTECTED] wrote: This was already discussed, but the conclusion was not clear. Do we migrate https://svn.apache.org/repos/asf/incubator/ivy to https://svn.apache.org/repos/asf/ant/ivy I thought this was already decided upon so +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where to place sponsorship link?
Gilles Scokart schreef: Did someone have an idea where to place the link to the sponsorship page? Did we have to place it in ant home page only, or do we have to place it also in ivy home page In ant home page, I think a good place could be: - a separate menu Sponsorship at the end of the project managment menu pointing to a new small page with the two required links. - A separate section in the contributors page. I was wondering if it would be both more effective and efficient to include the required links directly in the menu under a separate header sponsorship, so without an extra page in between. Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: terminating running builds better
To Recently I have put some effort to remove ignoring thread.interrupt from all kinds of (endless) loops. Interrupting a few times (as other parts may also wait in order to neatly close resources) should now stop ant. Martijn Darin Swanson schreef: Eclipse is pretty similar to #1. We have a progress monitor / build listener within which we check to see if the user has requested to cancel the build. If the monitor is cancelled we throw a OperationCancelledException which halts the execution of the build from the Eclipse entry point and reports the cancelled message to the user. Darins http://www.runnerwhocodes.blogspot.com/ Jesse Glick [EMAIL PROTECTED] Sent by: news [EMAIL PROTECTED] 11/03/2007 01:19 PM Please respond to Ant Developers List dev@ant.apache.org To dev@ant.apache.org cc Subject Re: terminating running builds better Steve Loughran wrote: What do IDEs do to stop ant builds? just kill the thread/process? NB behaves as follows: 1. It sets a special flag. The next time any BuildListener/BuildLogger method is called on the IDE's listener, it will throw a BuildException, which usually stops the build. 2. If several seconds have elapsed with no listener method, or if the build did not stop for any other reason, Thread.stop is called. For example, if java fork=true is the active task, any output printed will cause #1 to be triggered. Otherwise, ThreadDeath is caught by the task, which stops the external process and then rethrows. Not perfect but seems to work reasonably well in practice. #2 could probably be improved to first try Thread.interrupt and only use Thread.stop as a last resort. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant SVN Trunk - errors in LocatorTest RmicAdvancedTest
Steve Loughran schreef: Kev Jackson wrote: Hi, After Steve's work yesterday, I was going to pull in the changes to the release to try and get a clean build...but: (these errors occur with the svn trunk code) LocatorTest testNetworkURI Failure Expected file:\\PC03\jclasses\lib\ant-1.7.0.jar to resolve to \\PC03\jclasses\lib\ant-1.7.0.jar but got D:\\PC03\jclasses\lib\ant-1.7.0.jar expected:[]\\PC03\jclasses\lib\... but was:[D:]\\PC03\jclasses\lib\... I'm not sure what this should be - \\ is a unc path right, and windows should support that, so I'm not sure where the D: comes from (except that's the local disk that I'm running the ant tests from) LocatorTest testUnixNetworkPath Failure Expected file://cluster/home/ant/lib to resolve to \\cluster\home\ant\lib but got D:\\cluster\home\ant\lib expected:[]\\cluster\home\ant\l... but was:[D:]\\cluster\home\ant\l... Should this execute at all on a windows machine? I hadnt decided what the right outcome here was...the code has the option of us providing a separate windows expected string, but we need to know what to expect If I type, in ie7, file://morzine/slo I get a new windows explorer window opening up to the share \\morzine\slo If I type, in ie6, file://morzine/slo the IE6 window turns into an windows explorer window showing the share \\morzine\slo in icon vew In firefox i have to type file:/home.famkruithof.net/jkf (Yes that's 5 slashes) before it opens an share file:// is the base / represents root and // reprensents the start of the share It won't settle for more or less slashes. I still have to test under java uri handling Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r590990 - /ant/core/trunk/src/main/org/apache/tools/ant/util/WorkerAnt.java
public void waitUntilFinished(long timeout) throws InterruptedException {
synchronized(notify) {
-if(finished) {
-return;
+while (!finished) {
+notify.wait(timeout);
}
-notify.wait(timeout);
}
}
I hope you noticed that this is not an equivalent change, not just
starting to accepting false interrupts, but also to ignore the timeout.
to do it correctly probably it should be using something using
currentTimeMillis as well.
Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bugs in release branch
Hi Using ant 1.7.1 alpha on jdk 1.6 i have the same junit test failures ( 7 failures and 5 errors) and some antunit testcases fail 1 error, 2 failures (Furthermore it blocks halfway the test until user input is received imo this is annoying for automated testing.) results: http://kruithof.xs4all.nl/ant/ant-17branch-16 Using ant 1.7.1 alpha on jdk 1.4 i have for junit 7 failures (the same ones) / no errors and 4 failures and 7 errors on the antunit test cases. results: http://kruithof.xs4all.nl/ant/ant-17branch-14 Using ant 1.8 alpha on jdk 1.6 i have for junit 6 errors and 6 failures and for antunit 3 failures and 7 errors (also this one blocks halfway the test until user input is received) results: http://kruithof.xs4all.nl/ant/ant-trunk-16 Using ant 1.8 alpha on jdk 1.4 i have for junit 1 error and 6 failures (the same ones) / 3 failures and 7 errors on the antunit test cases. results: http://kruithof.xs4all.nl/ant/ant-trunk-14 Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Merge Ivy and Ant Dev Lists
Stefan Bodewig schreef: Hi, it seemed as if the discussion favored a joined mailing lists of Anf (and antlibs) and Ivy, so here is the formal vote. Should we merge [EMAIL PROTECTED] into [EMAIL PROTECTED] and likewise [EMAIL PROTECTED] into the new [EMAIL PROTECTED] Stefan +1 Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Create a Separate Mailing List for Commits/Bugzilla/Gump ...
Stefan Bodewig schreef: Hi, this came up in the thread dealing with mailing list organization now that Ivy is with us, but I guess many people have missed it. Do we want to add a new list [EMAIL PROTECTED] that will receive all Commit, Gump, Bugzilla, Jira and Wiki notification mails (and whatever else may come up in the future)? Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] +1 Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r585108 - /ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/XSLTProcess.java
Kevin Jackson schreef: Tell me how to merge stuff in SVN and I will try! I just copied'n'pasted :( apparently svn 1.5 will have easier merging than currently[1] http://blog.red-bean.com/sussman/?p=79 I've been playing with git recently and I'm very very impressed by it's performance - cloning the entire linux kernel source is very fast considering my network connection vs the size of the source tree. Performing a checkout of a project using svn is less stellar :( Kev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I am merging using eclipse merge option on svn (with the subversion plugin) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ivy mailing list organisation
Xavier Hanin schreef: On 10/12/07, Stefan Bodewig [EMAIL PROTECTED] wrote: On Fri, 12 Oct 2007, Martijn Kruithof [EMAIL PROTECTED] wrote: maybe we could create the following lists ant-bugs (gump, bugzilla, (what bug platform is ivy on?)) ant-commits (svn commits from both ivy and ant) ant-dev (development discussion on both ivy and ant) ant-user (as-is for the users) ivy-user (as-is for the users) works for me (but I probably wouldn't split bugs and commits at all). And instead of ant-dev, [EMAIL PROTECTED] as it is right now. Ivy uses JIRA and Xavier is the admin IIRC. Fine for me too, and I agree with Stefan, I wouldn't split bugs and commits. There's also yet another notification e-mail kind: wiki notifications. Where would they fall in? Good points new proposal: notifications (gump, wiki, bugzilla, jira, wiki, svn, for both ivy and ant) dev (development discussion on both ivy and ant) ant-user ivy-user Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Ivy mailing list organisation
[EMAIL PROTECTED] schreef: maybe we could create the following lists ant-bugs (gump, bugzilla, (what bug platform is ivy on?)) ant-commits (svn commits from both ivy and ant) ant-dev (development discussion on both ivy and ant) ant-user (as-is for the users) ivy-user (as-is for the users) works for me (but I probably wouldn't split bugs and commits at all). And instead of ant-dev, [EMAIL PROTECTED] as it is right now. Ivy uses JIRA and Xavier is the admin IIRC. Fine for me too, and I agree with Stefan, I wouldn't split bugs and commits. There's also yet another notification e-mail kind: wiki notifications. Where would they fall in? Both projects (Ant and Ivy) have the same mail-origins. So we could also do: - wiki --- [EMAIL PROTECTED] [EMAIL PROTECTED] - bugtracking (Bugzilla + JIRA) --- [EMAIL PROTECTED] [EMAIL PROTECTED] - Users --- [EMAIL PROTECTED][EMAIL PROTECTED] - Developers--- [EMAIL PROTECTED] [EMAIL PROTECTED] - Usage of Gump --- [EMAIL PROTECTED] ([EMAIL PROTECTED]) maybe only one - Subversion--- [EMAIL PROTECTED] ([EMAIL PROTECTED]) maybe only one total 10-12 mailinglists Imo these are too many lists for the volume we have, furthermore in order to build a single development community, I'd really be in favour of only having one dev list. Of course everyone in the community can have his or her specific points of intrest and be more active in one part or the other, but we still are one development community. Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Infrastructure
Xavier Hanin schreef: On 10/12/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I don't want either, but ATM Ivy site is not integrated to incubator site, and Ivy is reachable at incubator.apache.org/ivy/. So why not take the same approach here? We can do that as a first step and think about an integrated solution later. If you check in your site into svn somewhere under ant/ivy any person with an Unix account in the Ant group can check it out to people.apache.org and the site would go live. We used to have our site in svn, but now we generate it and publish it using ssh. We have a build.xml for that, so we only need to change the destination location in the build.xml and publish the site, this should be pretty easy. One question: How do we handle relocation for people having bookmarked pages @ incubator.apache.org/ivy/? Not sure if this is possible. But maybe Apache httpd URL-rewrite could help... Indeed, it seems to be possible. Here's what wicket guys use: .htaccess --- RewriteEngine on RewriteRule ^(.*)$ http://wicket.apache.org/$1 [R,L] --- Pretty easy to adapt to our needs :-) So I will move Ivy site if nobody objects. Xavier Fine to move it, probably a moved permanently response (R=301) to the browsers is better though. I currently have an update script on people (minotaur) that updates the ant website once a day from svn. dependent on the location the ivy specifics of the website will be stored the script will need to be updated to do a separate sync for the ivy parts of the website. The current sync is from /ant/core/trunk/docs for the base documentation and /ant/core/tags/ANT_170/docs/manual for the manual part of the documentation (this depends on the one doing an explicit checkout of a certain branch at a specific position.) I assume the script would pick up a new location after an explicit initial checkout. If not, I'll add it. (The script) #!/bin/tcsh cd /www/ant.apache.org /usr/local/bin/svn up | /usr/bin/grep -v At revision Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ivy mailing list organisation
Stefan Bodewig schreef: On Fri, 12 Oct 2007, Xavier Hanin [EMAIL PROTECTED] wrote: On 10/11/07, Dominique Devienne [EMAIL PROTECTED] wrote: What about using [EMAIL PROTECTED] and [EMAIL PROTECTED] directly, and discuss Ivy directly on the Ant lists? Ivy could be considered in a way as a big AntLib, and we don't have separate lists for AntLibs for example. Just a thought... --DD I don't really know what I think about that... Same here. So I don't know what I really prefer, maybe it's something we should ask to our (Ant and Ivy) users on our current user mailing list? That might be a good idea for users, but what about dev? We are the users here. I understand your wish to keep automatic mails and human generated content separate. Maybe we should do so for Ant as well? Stefan I'd agree on separation of the commit messages for ant as well. volumes on september ivy-commits 119 ivy-dev 51 ivy-user 146 ant-dev 453 (48 gump, 113 svn, many bugzilla) ant-user 446 maybe we could create the following lists ant-bugs (gump, bugzilla, (what bug platform is ivy on?)) ant-commits (svn commits from both ivy and ant) ant-dev (development discussion on both ivy and ant) ant-user (as-is for the users) ivy-user (as-is for the users) br Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r581055 - /ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/ssh/Scp.java
Please review, I was not able to test it today.
(the { in the while clause is on a separate line because it would break
the 80 char limit)
Martijn
[EMAIL PROTECTED] schreef:
Author: jkf
Date: Mon Oct 1 13:07:17 2007
New Revision: 581055
URL: http://svn.apache.org/viewvc?rev=581055view=rev
Log:
pr 43521, @ in filename not allowed anymore since @ allowed in password.
Modified:
ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/ssh/Scp.java
Modified:
ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/ssh/Scp.java
URL:
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/ssh/Scp.java?rev=581055r1=581054r2=581055view=diff
==
--- ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/ssh/Scp.java
(original)
+++ ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/ssh/Scp.java
Mon Oct 1 13:07:17 2007
@@ -310,10 +310,21 @@
}
private String parseUri(String uri) {
-int indexOfAt = uri.lastIndexOf('@');
+
+int indexOfAt = uri.indexOf('@');
int indexOfColon = uri.indexOf(':');
+
if (indexOfColon -1 indexOfColon indexOfAt) {
// user:[EMAIL PROTECTED]:/path notation
+// everything upto the last @ before the last : is considered
+// password. (so if the path contains an @ and a : it will not
work)
+int indexOfCurrentAt = indexOfAt;
+int indexOfLastColon = uri.lastIndexOf(':');
+while (indexOfCurrentAt -1 indexOfCurrentAt
indexOfLastColon)
+{
+indexOfAt = indexOfCurrentAt;
+indexOfCurrentAt = uri.indexOf('@', indexOfCurrentAt + 1);
+}
setUsername(uri.substring(0, indexOfColon));
setPassword(uri.substring(indexOfColon + 1, indexOfAt));
} else {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Ivy as subproject of Ant
[EMAIL PROTECTED] schreef: The Ivy community has voted [1] for becoming a subproject of Ant. Should we accept Ivy as subproject? Which means that we will share the ACL and have similar access rights to subversion. Our initial thought [2] when we starting mentoring Ivy in the Incubator was accepting. But maybe thoughts change ... I'll start with +1 Jan +1 Martijn [1] http://marc.info/?l=ivy-devm=119078926811557w=2 [2] http://marc.info/?l=ant-devm=116118082522301w=2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release manager for 1.7.1
Kevin Jackson wrote: Hi all, It's time to get a bug-fix release out, and again today we're getting messages from the user list asking for 1.7.1. I volunteer to be release manager (but would like an experienced hand to back me up procedurally and with svn branching etc). +1 Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Ben Burgess as committer
+1 Martijn Peter Reilly wrote: Hi all, I would like to propose Ben Burgess as a committer for the ant project, with a special interest in maintaining the starteam tasks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Weblogic and Starteam antlibs for ant 1.8.0
Yes - move the weblogic and starteam tasks to antlibs. [ ] No - keep them in ant 1.8.0 [ ] My vote is for Yes [X] Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote: Proposed removal of the ant-type attribute
+1 Martijn Kevin Jackson schreef: +1 deprecate for 1.7.1 if no-one dissents Kev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.7.x branch
+1 Martijn Matt Benson schreef: I'd like to create one. Any objections? -Matt Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mailp=graduation+giftscs=bz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Probable bug found: scp task does not handle correctly directories containing subdirectories
Please verify this with an older (0.1.29) version of jsch or with the
latest Ant (nightly build) before submitting a bugreport.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41090
br Martijn
Jean-Noël Rivasseau schreef:
Hi, I posted this on the user list but noone answered, I have better luck
here.
I am using Ant 1.6.5 and Ant 1.7 on Gentoo Linux amd64, and the same
behavior appears.
When using the scp task, I cannot copy a directory that contains
subdirectories. When copying a directory that has no subdirectories,
things
work fine, but any directory with subdirs in it will cause the scp
task to
hang.
By hang, I mean that the scp task when Ant is loaded from the command
line
never finishes.
Should a bug report be filed? Is this normal behavior?
My code:
scp todir=[EMAIL PROTECTED] :/home/elvanor/test/ port=23
keyfile=${user.home}/.ssh/id_rsa passphrase= verbose=true
fileset dir=build/WEB-INF/classes includes=**/* /
/scp
Note that there are no errors related to authentication or whatever. Just
changing the fileset dir attribute to some directory that has no
subdirectories makes the whoile thing work perfectly.
Jean-Noël
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] drop java 1.2 support in ant 1.7.1 and later
This vote has passed as there were only votes in favour of dropping support of java 1.2 Martijn Martijn Kruithof schreef: Hi Because the discussion is coming up again, and I would like to have a clear result, here an official Vote request. Given the facts that 1) java 1.2 is EOL 2) java 1.2 is not supported by the official ant 1.7.0 delivery 3) the problems running java 1.2 on some newer versions of operating systems I propose to drop java 1.2 support completely in ant 1.7.1 , also for custom builds. If some organisation wants to stick to java 1.2, I would expect it to be acceptable to stick to ant 1.6.5 for such organisation. It has to be noted that the ant 1.7.0 delivery can be built using jdk 1.2 and also be used using jdk 1.2 in that case. [ ] Yes drop Java 1.2 support altogether as of now [ ] No do not drop Java 1.2 support altogether as of now Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] move defect tracking from bugzilla to Jira
On Tue, 24 Apr 2007, Steve Loughran [EMAIL PROTECTED] wrote: The fact that people are running automation experiments on bugzilla makes me think that now is a good time to move to Jira. Accordinly, I would like to call a vote about moving to JIRA [] Yes, move to JIRA [] No, stay with Bugzilla I do not really see the point in switching, JIRA also seems to have its spam problems. My stance is -0. In case the infra team wants us to switch I am +1, but I do not see any point in switching just for the fun of it. Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: minimum supported Java version
I believe it still is Java 1.2. I cannot test the standard builds on it anymore and for my linux environment i cannot build and test it anymore. I remember some discussion from 2 years ago vaguely but can't remember if it came to a vote. I'd vote in favour of dropping support for both 1.2 and 1.3 if a vote was called. (both 1.2 and 1.3 have completed the SUN EOL process) (1.3 on solaris 8 is still in the EOL process as per customer support agreement) I could see this as a general mechanism, we do not support jdks in new releases anymore that have completed the end of life process. Martijn On Mon, 23 Apr 2007, Steve Loughran wrote: What is our minium Java version these days? Java 1.3? IntrospectionHelper has some stuff (EMPTY_MAP) that is only needed for 1.2 support, so if we are on java1.3+, I could strip it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: minimum supported Java version
Steve Loughran schreef: OK, so we are java1.3+ now. Excellent. Could we make 1.3+ that (or even 1.4+) make official via a vote? Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] drop java 1.2 support in ant 1.7.1 and later
Hi Because the discussion is coming up again, and I would like to have a clear result, here an official Vote request. Given the facts that 1) java 1.2 is EOL 2) java 1.2 is not supported by the official ant 1.7.0 delivery 3) the problems running java 1.2 on some newer versions of operating systems I propose to drop java 1.2 support completely in ant 1.7.1 , also for custom builds. If some organisation wants to stick to java 1.2, I would expect it to be acceptable to stick to ant 1.6.5 for such organisation. It has to be noted that the ant 1.7.0 delivery can be built using jdk 1.2 and also be used using jdk 1.2 in that case. [ ] Yes drop Java 1.2 support altogether as of now [ ] No do not drop Java 1.2 support altogether as of now Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
someone playing with bugzilla
I have marked all those bugreps as resolved / invalid, and added the developers list again, because the guy tried to hide his activity from us (he did this all on 18-4-2007) . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Manual page
I have manually updated the api manual page at the ant website to display the original placeholder message. (now without the in-between frame pages, where things got broken) (For obvious reasons this page is not updated via svn.) If you see this page online at ant.apache.org, it is not a bug, but on purpose. We do not provide an online version of the API docs, they are included with all our distributions. Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Nightlies
Hi It seems that the nighly builds do not pull the most recent changes (head) from svn (anymore). Antoine could you please have a look at what is going on? Br Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
automagic website update
Hi I have installed a cron job on people.apache.org to automatically update the web site. Any objections? Script: /home/jkf/updateweb #!/bin/tcsh cd /www/ant.apache.org /usr/local/bin/svn up | /usr/bin/grep -v At revision crontab: 57 2 * * * /home/jkf/updateweb br Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AntUnit
Antoine Levy-Lambert schreef: Hi, I have not done anything much with antunit yet, but I am also +1. It is a cool way of testing ant tasks. Regards, Antoine Not only that our testsuite of 1.7.0 final relies on it so definetely +1 here. Martijn Original-Nachricht Datum: Fri, 22 Dec 2006 18:27:08 + Von: Peter Reilly [EMAIL PROTECTED] An: Ant Developers List dev@ant.apache.org Betreff: Re: AntUnit On 12/22/06, Stefan Bodewig [EMAIL PROTECTED] wrote: On Thu, 21 Dec 2006, Peter Reilly [EMAIL PROTECTED] wrote: I haven't seen anybody complain about missing features in beta2, is AntUnit ready for a 1.0 release? Does it work with ant 1.6.5? Not at all. Apart from relying on ResourceCollections it uses a bunch of other API changes or the new backtrace attribute on macrodef. I just had a vague memory of a request to make antunit ant 1.6 compatible, but I am cool with making it depend on ant 1.7. So +1 for releasing antunit 1.0. Peter Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Branch
Have we already created an ANT_17_BRANCH? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Branch
Matt Benson schreef: --- Martijn Kruithof [EMAIL PROTECTED] wrote: Have we already created an ANT_17_BRANCH? Not that I know of. We did pretty well restraining ourselves from committing to HEAD just before the release. :) Should we wait on branching until nearer to 1.7.1, or until we know we want to put something in that should be for 1.8? -Matt I think we should create a branch as soon as the 1.7 version series stabilizes. (and only make things public that should be in 1.8 after the 1.7 series has become oficially stable) Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release of Apache Ant 1.7.0 - new upload done
Antoine Levy-Lambert schreef: On Dec 16, 2006, at 5:42 PM, Martijn Kruithof wrote: On Wed, 13 Dec 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: I did a third upload where the HasFreeSpace condition will be present. I am +1 on releasing those, we should however document that the official release does not work with jdk 1.2 Hello Martijn, I am fine with documenting that the release does not run under JDK 1.2. Since the documentation of the release is frozen, (because it is part of the Subversion tag and of the various binaries) I can write it in the email which will announce the release, and also write in on our web site after the release. This would be fine Does any one know whether, when one builds 1.7.0 using JDK 1.4.0, ant runs under JDK 1.2 ? I just verfied a build using j2sdk1.4.2_10, it does not run under jdk 1.2.2. Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release of Apache Ant 1.7.0 - new upload done
On Wed, 13 Dec 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: I did a third upload where the HasFreeSpace condition will be present. I am +1 on releasing those, we should however document that the official release does not work with jdk 1.2 Also in the WHATSNEW still the following entry is present * On Java1.5+, Ant automatically sets the system property java.net.useSystemProxies to true, which gives it automatic use of the local IE (Windows) or Gnome2 (Unix/Linux) proxy settings. This may break any build file that somehow relied on content outside the firewall being unreachable: use the -noproxy command-line option to disable this new feature. Note that the Java1.5 proxy configuration system still does not appear to work reliably on Windows or Linux. I thought this wasn't true anymore Also maybe we should remove: * The -noproxy option which was in the previous 1.7 alpha and beta releases has been removed. It is the default behavior and not needed. Martijn Results when trying to run on java 1.2.2 on windows are the same as with the release candidate: D:\data\eclipseworkspace\ant-trunkset JAVA_HOME=c:\java\jdk1.2.2 D:\data\eclipseworkspace\ant-trunkd:\apache-ant-1.7.0\bin\ant test Buildfile: build.xml A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.addReference (Ljava/lang/String;Ljava/lang/Objec t;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.fireMessageLoggedEvent (Lorg/apache/tools/ant/Bu ildEvent;Ljava/lang/String;I)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/util/FileUtils.fromURI (Ljava/lang/String;)Ljava/lang/St ring;': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/taskdefs/ProcessDestroyer.add (Ljava/lang/Process;)Z': I nterpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i [property] java.lang.IllegalMonitorStateException: current thread not owner [property] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.j ava, Compiled Code) [property] at java.lang.Thread.run(Thread.java:479) [property] java.lang.IllegalMonitorStateException: current thread not owner [property] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.j ava, Compiled Code) [property] at java.lang.Thread.run(Thread.java:479) ^CBatchopdracht beëindigen (J/N)? ^C D:\data\eclipseworkspace\ant-trunk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: JDK 1.2 compatibility
My experiments where conducted using the official RC1 with 1.2, not by building and running with 1.2 The official RC1 works (limited) with 1.3 and higher these issues have been changes, so that a similar build will run successfully on 1.3. Martijn [EMAIL PROTECTED] wrote: Ok, test results: build.bat -nouserlib test - build: ok - compile-tests: ok (11 files use or override a deprecated API) junit-batch: [mkdir] Created dir: C:\ant\svn-repository\ant\core\build\testcases\xml [junit] Testsuite: org.apache.tools.ant.AntClassLoaderDelegationTest BUILD FAILED C:\ant\svn-repository\ant\core\build.xml:1754: The following error occurred while executing this line: C:\ant\svn-repository\ant\core\build.xml:1636: java.lang.IllegalMonitorStateException: current thread not owner Same error when executing a 2nd time. Jan -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Montag, 27. November 2006 09:01 An: dev@ant.apache.org Betreff: AW: JDK 1.2 compatibility I'm doing a test on - WinXP SP2 - Classic VM (build JDK-1.2.1_004, native threads) - Revision: 479528 (HEAD at this time ;-) - command: build.bat -nouserlib -- bootstrap * bootstrap: ok (5 files use or override a deprecated API) * build: ok (3 files use or override a deprecated API) BUILD SUCCESSFUL Done Bootstrapping Ant Distribution -- build * build: ok (8 files use or override a deprecated API) BUILD SUCCESSFUL - dist\bin.\ant -version Apache Ant version 1.7.0RC1 compiled on November 27 2006 We can not assure 1.2-buildability for optional tasks, because we can assure that the external libraries are 1.2-compliant (class-version error). I'm retrying the testsuite (which needs time on my machine :-( ) Jan -Ursprüngliche Nachricht- Von: Martijn Kruithof [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 24. November 2006 21:28 An: Ant Developers List Betreff: Re: JDK 1.2 compatibility Peter Reilly schreef: On 11/24/06, Martijn Kruithof [EMAIL PROTECTED] wrote: As you might have noticed. about a week ago I wrote about some troubles on jdk 1.3 which by now are fixed. However I didn't get any reaction on the fact that the official builds do not work at all for JDK 1.2. What were the issues (I cannot easily find the email in question)? It completely fails: It seems our release candidate is not nearly compatible with JDK 1.2.2 JDK 1.2.2_017 on windows XP home gives: D:\data\eclipseworkspace\ant-trunkapache-ant-1.7.0RC1\bin\ant test Buildfile: build.xml A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.addReference (Ljava/lang/String;Ljava/lang/Objec t;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.fireMessageLoggedEvent (Lorg/apache/tools/ant/Bu ildEvent;Ljava/lang/String;I)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/util/FileUtils.fromURI (Ljava/lang/String;)Ljava/lang/St ring;': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.addCreatedTask (Ljava/lang/String;Lorg/a pache/tools/ant/Task;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/taskdefs/ProcessDestroyer.add (Ljava/lang/Process;)Z': I nterpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i [property] java.lang.IllegalMonitorStateException: current thread not owner [property] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.j ava, Compiled Code) [property] at java.lang.Thread.run(Thread.java:479) [property] java.lang.IllegalMonitorStateException: current thread not owner [property] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.j ava, Compiled Code) [property] at java.lang.Thread.run(Thread.java:479) I couldn't get jdk 1.2 to run on linux. Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
Re: seemingly infinite loop in Project class
Peter Reilly schreef:
On 11/23/06, Dave Brosius [EMAIL PROTECTED] wrote:
protected void fireMessageLogged(Project project, String message,
int priority) {
fireMessageLogged(project, message, priority);
}
That does incorrect.
It possible should be fireMessageLogged(project, message, null,
priority).
The question is why is there so many variants of fireMessageLogged(),
+Event
- they are protected methods - so they can only be used by derived
classses
of Project and by classes within o.a.t.a ?
Peter
Yep it is incorrect.
I have added, and not removed the methods because of backward
compatibility. In my view protected methods are just as public as public
methods (we may have users we do not know of, and they would be
rightfully using it). If they would have been package scoped I would not
have mercy.
Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JDK 1.2 compatibility
As you might have noticed. about a week ago I wrote about some troubles on jdk 1.3 which by now are fixed. However I didn't get any reaction on the fact that the official builds do not work at all for JDK 1.2. I am not too concerned about dropping support for JDK 1.2, but we should agree on it, and if we drop support for JDK 1.2, make it official. Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.2 compatibility
Peter Reilly schreef: On 11/24/06, Martijn Kruithof [EMAIL PROTECTED] wrote: As you might have noticed. about a week ago I wrote about some troubles on jdk 1.3 which by now are fixed. However I didn't get any reaction on the fact that the official builds do not work at all for JDK 1.2. What were the issues (I cannot easily find the email in question)? It completely fails: It seems our release candidate is not nearly compatible with JDK 1.2.2 JDK 1.2.2_017 on windows XP home gives: D:\data\eclipseworkspace\ant-trunkapache-ant-1.7.0RC1\bin\ant test Buildfile: build.xml A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.addReference (Ljava/lang/String;Ljava/lang/Objec t;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.fireMessageLoggedEvent (Lorg/apache/tools/ant/Bu ildEvent;Ljava/lang/String;I)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/util/FileUtils.fromURI (Ljava/lang/String;)Ljava/lang/St ring;': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.addCreatedTask (Ljava/lang/String;Lorg/a pache/tools/ant/Task;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/taskdefs/ProcessDestroyer.add (Ljava/lang/Process;)Z': I nterpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i [property] java.lang.IllegalMonitorStateException: current thread not owner [property] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.j ava, Compiled Code) [property] at java.lang.Thread.run(Thread.java:479) [property] java.lang.IllegalMonitorStateException: current thread not owner [property] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.j ava, Compiled Code) [property] at java.lang.Thread.run(Thread.java:479) I couldn't get jdk 1.2 to run on linux. Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] add ant-testutil.jar to the ant distribution
Antoine Levy-Lambert schreef: Hi, Steve Loughran entered a bug report asking for creating a POM for ant-testutil.jar. This is easy. The real issue is that until now this artefact was not part of our binary distribution. So let's vote on the following Do you want to add ant-testutil.jar to the binary distribution, and supply a POM file for it. Yes [X] No [ ] Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FileUtilsTest jdk 1.3 vs 1.5
Hi On jdk 1.3 the test testFromURI() will fail because with jdk 1.3 no drive letter is inserted for a path that does not contain a drive letter. with jdk 1.5 the drive letter is inserted for a path that is drive absolute the fromURI method has javadoc claiming the following: /** * Constructs a file path from a codefile:/code URI. * * pWill be an absolute path if the given URI is absolute./p * * pSwallows '%' that are not followed by two characters, * doesn't deal with non-ASCII characters./p * * @param uri the URI designating a file in the local filesystem. * @return the local file system path for the file. * @since Ant 1.6 */ One could argue that a path without a drive letter is not absolute but relative and therefore the drive letter should not be inserted at all. (And the test should fail for jdk 1.5 and not jdk 1.3.) Definitely the behaviour should be the same. What is your opinion on the required behaviour? Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache Ant 1.7.0RC1
Hi It seems our release candidate is not nearly compatible with JDK 1.2.2 JDK 1.2.2_017 on windows XP home gives: D:\data\eclipseworkspace\ant-trunkapache-ant-1.7.0RC1\bin\ant test Buildfile: build.xml A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.addReference (Ljava/lang/String;Ljava/lang/Objec t;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.fireMessageLoggedEvent (Lorg/apache/tools/ant/Bu ildEvent;Ljava/lang/String;I)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/util/FileUtils.fromURI (Ljava/lang/String;)Ljava/lang/St ring;': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.addCreatedTask (Ljava/lang/String;Lorg/a pache/tools/ant/Task;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/taskdefs/ProcessDestroyer.add (Ljava/lang/Process;)Z': I nterpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg i [property] java.lang.IllegalMonitorStateException: current thread not owner [property] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.j ava, Compiled Code) [property] at java.lang.Thread.run(Thread.java:479) [property] java.lang.IllegalMonitorStateException: current thread not owner [property] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.j ava, Compiled Code) [property] at java.lang.Thread.run(Thread.java:479) Also on jdk 1.3 a significant number of testcases fail. Partly of methods being used that are not there before jdk 1.4. (For instance StringBuffer.append(StringBuffer) used instead of StringBuffer.append(Object)) But also because of parts of JUnit that do use 1.4 specific methods. Still +1 on releasing RC1 tomorrow, it should be noted however that this release will not work with 1.2 and work very limited with 1.3 based jvm. I am looking into getting a1.5 based build working towards 1.3 jvm's, I will NOT start to work on getting it to work on 1.2 as well. Martijn Antoine Levy-Lambert schreef: Hi, I hit the send button a bit too fast. I want to ask : OK to release these files as Ant 1.7.0RC1 on Sunday, November 12th, as Ant 1.7.0RC1 ? Yes [] No [] Regards, Antoine Antoine Levy-Lambert wrote: Hi, I have just built and uploaded to my apache account Apache Ant 1.7.0RC1. binaries are here : http://people.apache.org/~antoine/apache-ant-1.7.0RC1/distribution/binaries/ source distribution is here : http://people.apache.org/~antoine/apache-ant-1.7.0RC1/distribution/source/ the files for an upload to ibiblio are here : http://people.apache.org/~antoine/apache-ant-1.7.0RC1/java-repository/ Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache .NET Antlib 1.0 final
+0 Martijn On 10/29/06, Stefan Bodewig [EMAIL PROTECTED] wrote: Hi, I've created distribution files for the .NET Antlib and uploaded them to http://people.apache.org/~bodewig/dotnet-antlib/ and propose to release them as 1.0 final. As described on the release plan for this Antlib I don't expect the betas to get enough people to test it and the Antlib needs more testers outside the Ant team so I'd like to skip further betas. The release has been tested on: WinXP + Microsoft .NET 1.1 WinXP + Microsoft .NET 2.0 WinXP + Mono 1.1.17 Linux + Mono 1.1.14 (Gump) Linux + Mono 1.1.17 Mac OS X + Mono 1.1.18 Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release AntUnit 1.0Beta2
Antoine Levy-Lambert schreef: Hello Stefan, did a quick verification of the download of the tar.gz. Works fine, checked md5 and signature. By the way, if you svn checkout openpgp from jakarta commons sandbox, the ant task to gpg sign binary files is here, and you can build it with mvn install. I wanted even to update the openpgp web site to show this, but could not, I am waiting to get jakarta UNIX group membership. +1 for the release, Antoine Stefan Bodewig wrote: Hi, I've uploaded binaries of AntUnit to http://people.apache.org/~bodewig/antunit/, please verify them. I propose to publish them as Apache AntUnit 1.0 Beta2. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r354209 - in /ant/core/trunk: CONTRIBUTORS WHATSNEW contributors.xml docs/manual/running.html src/script/ant.bat
Antoine Levy-Lambert schreef: [EMAIL PROTECTED] wrote: Modified: ant/core/trunk/CONTRIBUTORS URL: http://svn.apache.org/viewcvs/ant/core/trunk/CONTRIBUTORS?rev=354209r1=354208r2=354209view=diff == Binary files - no diff available. Does anybody know why CONTRIBUTORS is binary ? Good evening, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Because of the entering of the names of contributors containing character like (but not limited to) èæ etc. in UTF-8 encoding. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release 1.7.0Beta3
Antoine Levy-Lambert wrote: Hi, I propose to build a third beta on Sunday, October 15th the tag in Subversion would be : ANT_170_B3 the version returned by ant -version would be : ant 1.7.0Beta3 Regards, Antoine +1 Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: VOTE: deferring resolving of references
Peter Reilly wrote: Impact: It is a one-line change. Influence release of 1.7: I do not think so. (I think that we need to release an ant 1.7beta3 soon, freeze commits after that (or branch) and try to get as many users to try it out.) There are BC issues: some scripts may depend on references defined in tasks that are not run, for example target name=not-run delete fileset id= delete.id dir=build/ /delete /target target name=clean delete fileset refid=delete.id / /delete /target Such scripts I would consider to be dodgy. Peter In that case +1 On 9/29/06, Martijn Kruithof [EMAIL PROTECTED] wrote: Peter Reilly wrote: Hi, I started a thead last week that did not end in a conclusion. should we defer resolving references until runtime: original message Currently in ant, there is two steps in processing a project build file, a parsing step and an execution step. In the parsing step a DOM like structure of Targets and UnknownElements are build up. These targets and unknown elements are then processed in the execution step. This model works quite ok. One part that does not work like this is the processing of the id attribute, these get processed at parsing stage. This has given rise to a lot of bugs and strange behaviour. http://issues.apache.org/bugzilla/show_bug.cgi?id=34458 http://issues.apache.org/bugzilla/show_bug.cgi?id=36955 http://issues.apache.org/bugzilla/show_bug.cgi?id=37688 http://issues.apache.org/bugzilla/show_bug.cgi?id=21724 This type of bug will happen more as people write larger build files (or equivalate using lots of import and macrodef) and use shared build files. I propose that we defer handing id's until the processing stage. thread: http://marc.theaimsgroup.com/?t=11589336704r=1w=2 Vote to include deferring for ant 1.7: Yes [ ] No [ ] I will start with Yes [x] Peter How big is the impact? How will this influence the release of 1.7? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
