AW: Cutting AntUnit 1.3

I couldn't find any Jira issues [1] related to the migration, so I think cutting the release before migration would be faster ;) Jan [1] https://issues.apache.org/jira/browse/INFRA-1983?jql=project%20%3D%20INFRA%2 0AND%20text%20~%20%22ant%20git%22 -Ursprüngliche Nachricht- Von:

AW: Ant-Matrix-Job

://builds.apache.org/computer/ - time is 13sec behind - ping=158ms Jan -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] Gesendet: Donnerstag, 8. Mai 2014 07:56 An: 'Ant Developers List' Betreff: AW: Ant-Matrix-Job The job is back again https

AW: Ant-Matrix-Job

: Yesterday I was wondering why it didn't appeared in my Personal View, but I didn't looked into it, merly though it was a UI bug. But it seems indeed gone… Nicolas Le 5 mai 2014 à 12:35, Jan Matèrne (jhm) apa...@materne.de a écrit : Does anyone know where (and why

AW: Hoped for advantages of migrating to git

As a ASF project we MUST have a repo in Apache land: http://www.apache.org/dev/writable-git ASF releases must be cut from the canonical ASF Git repositories. The absolute minimum is therefore: - working on somewhere else - starting a release: -- pull all changes to local -- push to ASF-repo --

AW: git commit: update STATUS file

Tried my git access (with success ;) Jan -Ursprüngliche Nachricht- Von: j...@apache.org [mailto:j...@apache.org] Gesendet: Montag, 26. Mai 2014 08:44 An: notificati...@ant.apache.org Betreff: git commit: update STATUS file Repository: ant Updated Branches: refs/heads/master

AW: migration to git : next steps - Jenkins

I changed the repo urls from svn to git for - Ant-Build-Matrix - Ant_BuildFromPOMs - Ant_Nightly - EasyAnt - Ivy - Ivy-check - IvyDE all with additional behaviour: clean before checkout and I started the builds. I'll have to wait for running builds ... Jan -Ursprüngliche Nachricht-

AW: migration to git : next steps - Jenkins

https://builds.apache.org/view/A-D/view/Ant/job/Ant_BuildFromPOMs/lastBuild/ works ... Other jobs are waiting in the queue. Jan -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] Gesendet: Dienstag, 27. Mai 2014 08:49 An: 'Ant Developers List' Betreff: AW

migration to git : next steps - updating Jenkins jobs

Current status: - Ant-Build-Matrix repo: git https://builds.apache.org/job/Ant_BuildFromPOMs/ status: errors on the slaves - Ant_BuildFromPOMs repo: git https://builds.apache.org/job/Ant_BuildFromPOMs/ status: run fine (using locks-and-latches, no archiving) -

AW: migration to git : next steps - updating Jenkins jobs

Subject migration to git : next steps - updating Jenkins jobs Text Here is an intermediate result and my opinion on that: Ant-Build-Matrix has problems on Ubuntu and on Windows. On Windows it seems (to me) that there is no git installed or not on the PATH. -- open an INFRA-Ticket? On Ubuntu

migration to git : next steps - updating Jenkins jobs

Here is an intermediate result and my opinion on that: Ant-Build-Matrix has problems on Ubuntu and on Windows. On Windows it seems (to me) that there is no git installed or not on the PATH. -- open an INFRA-Ticket? On Ubuntu publishing the build results failed. -- I'll have a look at the

migration to git : next steps - Jenkins

Here is an intermediate result and my opinion on that: Open problems = Ant-Build-Matrix has problems on Ubuntu and on Windows. On Windows it seems (to me) that there is no git installed or not on the PATH. -- open an INFRA-Ticket? On Ubuntu publishing the build results

migration to git : next steps - Jenkins

Here is an intermediate result and my opinion on that: All jobs are successful running or waiting for a blocking INFRA-issue. What about the IvyDE-updatesite? Open problems = I dont know wheter IvyDE-updatesite is migrated to git, too. -- Question to the IvyDE experts here ;)

migration to git : next steps - Jenkins

Here is an intermediate result and my opinion on that: All jobs are successful running or waiting for a blocking INFRA-issue. What about the IvyDE-updatesite? Also I updated the view (add missing ivy-tests) https://builds.apache.org/view/A-D/view/Ant/ I deactivated the windows builds until

IvyDE-updatesite

After git-migration the artefacts aren't available under 'trunk' any more. I couldn't change this by myself (access forbidden), so I attach a patch file. Jan https://builds.apache.org/view/A-D/view/Ant/job/IvyDE-updatesite/lastBuild/c onsole

AW: IvyDE-updatesite

- Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] Gesendet: Mittwoch, 28. Mai 2014 12:49 An: 'Ant Developers List' Betreff: IvyDE-updatesite After git-migration the artefacts aren't available under 'trunk' any more. I couldn't change this by myself (access forbidden), so I attach a patch file

Testing Antlibs

I am trying to build the antlibs, mainly props. A simple ant distribution works, but executing tests fail: 1. ${ant-testutil.jar} must be specified although it is part of the standard Ant installation 2. antunit is not present (I tweaked the common/build.xml to download that during the build)

AW: description of git repos

fixed now Jan this is done now. https://issues.apache.org/jira/browse/INFRA-7858 the description column on https://git-wip-us.apache.org/repos/asf says Apache Ivy for most of the Antlibs and IvyDE and Apache Ant for all the EasyAnt repos. Is this somethong we can fix ourselves

AW: Testing Antlibs

Betreff: Re: Testing Antlibs On 2014-06-03, Jan Matèrne (jhm) wrote: I am trying to build the antlibs, mainly props. A simple ant distribution works, but executing tests fail: 1. ${ant-testutil.jar} must be specified although it is part of the standard Ant installation Not sure

Jenkins for AntLibs

The Jenkins job for the first AntLib is running. If they arent any objections I will clone that for the other AntLibs. Jan https://builds.apache.org/job/AntLib-props/ * jdk: default * nodes: ubuntu (= no windows due git problems) * scm=git * triggered: after antlib-common (means,

IvyDE compiler error @ Jenkins

https://builds.apache.org/view/A-D/view/Ant/job/IvyDE/lastBuild/consoleFull [java] [javac] 650. ERROR in /home/jenkins/jenkins-slave/workspace/IvyDE/work/eclipse/plugins/org.apache. ivyde.eclipse/src/java/org/apache/ivyde/internal/eclipse/workspaceresolver/W orkspaceResolver.java (at

Repository access

After ivyde-updatesite (svn) this is the 2nd repo where I can't commit/push https://git-wip-us.apache.org/repos/asf/easyant-core.git Is there any reason? Jan

EasyAnt - status

In easyant-core there are two disclaimers (DISCLAIMER, README) saying that EA is still in incubation. I thought i was graduated ... this was also posted on http://blog.easyant.org/apache-graduation/ This should be updated. Jan

Building AntLibs

What is the way to deal with dependencies of AntLibs? - antlib-antunit requires junit - antlib-compress requires junit, commons-compress - ... Best way I think of is using Ivy from the antlib-commons/build.xml and specifying an ivy.xml in the antlibs itself. Jan

AW: Repository access

. It must be read only. Nicolas Le 5 juin 2014 à 07:57, Jan Matèrne (jhm) apa...@materne.de a écrit : After ivyde-updatesite (svn) this is the 2nd repo where I can't commit/push https://git-wip-us.apache.org/repos/asf/easyant-core.git Is there any reason? Jan

AntUnit @ Jenkins

The job is ready. But the last build gives me an error: https://builds.apache.org/view/A-D/view/Ant/job/AntLib-antunit/lastBuild/con sole [au:antunit] Build File: /x1/jenkins/jenkins-slave/workspace/AntLib-antunit/src/tests/antunit/assertR esourceExists-test.xml [au:antunit] Tests run: 4,

AntLib-svn @ Jenkins

AntLib-SVN ist running on Jenkins now without problems. https://builds.apache.org/job/AntLib-svn https://builds.apache.org/job/AntLib-svn/lastBuild/console Jan

AW: AW: Repository access

, Jan Matèrne (jhm) apa...@materne.de a écrit : After ivyde-updatesite (svn) this is the 2nd repo where I can't commit/push https://git-wip-us.apache.org/repos/asf/easyant-core.git Is there any reason? Jan

AW: AW: Repository access

in svn either. It must be read only. Nicolas Le 5 juin 2014 à 07:57, Jan Matèrne (jhm) apa...@materne.de a écrit : After ivyde-updatesite (svn) this is the 2nd repo where I can't commit/push https://git-wip-us.apache.org/repos/asf/easyant-core.git

GitHub integration

https://blogs.apache.org/infra/entry/improved_integration_between_apache_and To be more precise, these new features allows for the following: 1. Any Pull Request that gets opened, closed, reopened or commented on now gets recorded on the project's mailing list 2. If a project has a JIRA instance,

[VOTE] GitHub integration

After some out-of-vote +1, I'll start a formal vote (oh, my 1st one ;) Apache Infra supplies a variety of GitHub integrations [1]. As specified there, it is an opt in, so we must decide which of these services we want to have. Supported integrations are: 1. Any Pull Request that gets

AW: [VOTE] GitHub integration

Apache Infra supplies a variety of GitHub integrations [1]. As specified there, it is an opt in, so we must decide which of these services we want to have. My votes 1. Any Pull Request that gets opened, closed, reopened or commented on now gets recorded on the project's mailing list +1

AW: AW: Repository access

to be renamed to be pre-pended with Ant- for auth to work - in the same way as taglibs and Ivy are done now. Open an issue to have those repos renamed Next step by Conor ... Jan -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] Gesendet: Samstag, 7. Juni 2014

AW: [VOTE] GitHub integration

From my experience with log4net and commons, pull requests are pertty rare, BTW. At Camel PRs come in very often ... Jan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail:

AW: [jira] [Commented] (INFRA-7816) Create readonly git mirror for Xooki

I wouldnt count myself to the Ivy team, but I prefer changing to trunk/branches structure: * conform to other svn repos * easier setup for infra for the read only git repo Jan -Ursprüngliche Nachricht- Von: Jean-Louis Boudart [mailto:jeanlouis.boud...@gmail.com] Gesendet: Dienstag,

AW: AW: Repository access

://issues.apache.org/jira/browse/INFRA-7890 2014-06-08 11:20 GMT+02:00 Jan Matèrne (jhm) apa...@materne.de: Ticket closed: gmcdonald the asf-authorization-template is the place to add folks to easyant incubator project. A PMC Chair can do this. If EasyAnt is no longer an Incubator project

[RESULT] [VOTE] GitHub integration

The week is over. #1 and #3 passed, so I'll create the INFRA-ticket. Jan 1. Any Pull Request that gets opened, closed, reopened or commented on now gets recorded on the project's mailing list +1: Jan Stefan Antoine 2. If a project has a JIRA instance, any PRs or comments on PRs

AW: [RESULT] [VOTE] GitHub integration

https://issues.apache.org/jira/browse/INFRA-7913 Jan -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] Gesendet: Dienstag, 17. Juni 2014 08:05 An: 'Ant Developers List' Betreff: [RESULT] [VOTE] GitHub integration The week is over. #1 and #3 passed, so

AW: svn commit: r1603069 - /ant/site/easyant/sources/Sourcerepository.html

Not sure if there is something to generate with xooki ... Jan Log: repo changed to git Modified: ant/site/easyant/sources/Sourcerepository.html --- ant/site/easyant/sources/Sourcerepository.html (original) +++ ant/site/easyant/sources/Sourcerepository.html Tue Jun 17 06:38:38 2014

WG: [jira] [Commented] (INFRA-7913) Add GitHub integration to Ant git repos

Not sure who is ML moderator. But please send ;-) Jan -Ursprüngliche Nachricht- Von: Jake Farrell (JIRA) [mailto:j...@apache.org] Gesendet: Dienstag, 17. Juni 2014 15:24 An: j...@apache.org Betreff: [jira] [Commented] (INFRA-7913) Add GitHub integration to Ant git repos [

AW: Build failed in Jenkins: EasyAnt #175

Changed the configuration SCM-Git::Additional Behaviour Advanced sub-modules behaviour Recursively update submodules = true Build successful Job failed due archiving issues (I removed the trunk in the path and resceduled a build). Jan -Ursprüngliche Nachricht- Von: Jean-Louis

AW: Build failed in Jenkins: EasyAnt #175

All blue now. Jan -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] Gesendet: Mittwoch, 18. Juni 2014 08:09 An: 'Ant Developers List' Betreff: AW: Build failed in Jenkins: EasyAnt #175 Changed the configuration SCM-Git::Additional Behaviour Advanced

https://issues.apache.org/jira/browse/INFRA-7913

Regarding GitHub integration: https://issues.apache.org/jira/browse/INFRA-7913 Jake Farrell added a comment - 17/Jun/14 14:23 Please have a mailing list moderator send an email to the following two addresses to subscribe them to you dev list dev-subscribe-allow-git=git.apache@ant.apache.org

AW: IvyDE-updatesite - fix for jenkins

Ok thanks for check. I created a ticket for that. https://issues.apache.org/jira/browse/INFRA-7975 Jan -Ursprüngliche Nachricht- Von: Nicolas Lalevée [mailto:nicolas.lale...@hibnet.org] Gesendet: Samstag, 28. Juni 2014 00:09 An: Ant Developers List Betreff: Re: IvyDE-updatesite -

AW: git commit: add common module as a git submodule

I prefer having all antlibs in the same structure. My special buildfile is only a workaround. If submodules are the way we want to go (and if it works), I would change the Jenkins jobs and remove that buildfile. Common is built on https://builds.apache.org/view/A-D/view/Ant/job/AntLib-common/

AW: git commit: add common module as a git submodule

Oh, sorry you meant compress ;) No it wasn't built at Jenkins. Have cloned a job: https://builds.apache.org/view/A-D/view/Ant/job/AntLib-compress/ Needs a round or two (or three) for working smoothly ... cheers Jan -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm) [mailto:apa

AW: [1/8] make it compile under Java5 (1.5.0_22-b03)

Because Java5 is the lowest specified java version we support/require: http://ant.apache.org/faq.html#java-version Jan -Ursprüngliche Nachricht- Von: Antoine Levy Lambert [mailto:anto...@gmx.de] Gesendet: Mittwoch, 9. Juli 2014 23:43 An: dev@ant.apache.org Betreff: Re: [1/8] make it

AW: Build failed in Jenkins: Ivy-tests » JDK 1.5 (latest),Ubuntu #120

Changed the configuration from Ant 1.7.0 to Ant latest. -- same problem on Windows Changed Ant to Standard -- dont find ant.bat changed to ant-1.9.3 -- build runs fine https://builds.apache.org/job/Ivy-tests/jdk=JDK%201.5%20%28latest%29,label=Windows/lastBuild/console The Ubuntu build is

AW: which repo to use, svn or github?

I dont think so. What should the svn-client do with a redirected link which refers to a git repo? Jan -Ursprüngliche Nachricht- Von: André-John Mas [mailto:andrejohn@gmail.com] Gesendet: Freitag, 14. November 2014 20:04 An: Ant Developers List Betreff: Re: which repo to use, svn

AW: Fisheye displaying Ant/Ivy/IvyDe' git repositories

Fine, thanks. Jan -Ursprüngliche Nachricht- Von: Antoine Levy-Lambert [mailto:anto...@gmx.de] Gesendet: Samstag, 29. November 2014 21:30 An: dev@ant.apache.org Betreff: Fisheye displaying Ant/Ivy/IvyDe' git repositories Hi, An Atlassian Fisheye instance is now tracking

Jenkins

I changed the used Java version for the Jenkins job from 1.5 to 1.6 because the last few builds failed due a UnsupportedClassVersion error. https://builds.apache.org/job/Ant_BuildFromPOMs This was easier than searching which of the jars was 1.6+ based ;)

AW: [CANCELED][VOTE] Release Ivy 2.4.0

The ideal solutions to all this headaches would probably to have everything in git (including ivy's website), unfortunatly as far as i know we can't publish website via git @ASF for the moment. Infra offers a gitpubsub feature but i read somewhere that we can't use it to publish websites. Would a

AW: [CANCELED][VOTE] Release Ivy 2.4.0

Security hint: 'pushing' is not as secure as 'polling' here ... Maybe passwords have to be configured... Jan -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] Gesendet: Mittwoch, 10. Dezember 2014 07:57 An: 'Ant Developers List' Betreff: AW: [CANCELED][VOTE

AW: ant git commit: Arrays.copyOf is Java 1.6 only

right, we are tied to Java1.5 http://ant.apache.org/faq.html#java-version http://www.oracle.com/technetwork/java/eol-135779.html End of public updates: Java5: Oct 2009 Java6: Feb 2013 Java7: Apr 2015 (maybe later) Java8: Mar 2017 (maybe later) Extended support: Java5: May 2015 !!! Java6: Dec

Jenkins

I added a touchstone build on the matrix project. The matrix job [1] builds Ant for Windows+Ubuntu for Java 1.5, 1.6 and 1.8. The whole matrix starts now after a successful run on Java1.5@Ubuntu. Or do want to get the other builds done in any way? Jan [1]

AW: Generating EasyAnt website

BTW here some issues regarding the EA website https://issues.apache.org/jira/browse/EASYANT-66 https://issues.apache.org/jira/browse/EASYANT-74 https://issues.apache.org/jira/browse/EASYANT-63 Jan -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] Gesendet

AW: Generating EasyAnt website

I'll tried that also $ easyant publish-shared But xooki requires Java 1.6 and I failed to get it running ... On Windows cmd.exe with Java 1.6: xooki:generate: [xooki:generate] processing 65 source files... [generate] script file ./sources/xooki/xooki.js is not found [generate] Result: 11

ant.project.invoked-targets

The magic property ant.project.invoked-targets is set when the targets are executed. That means, that you can't use this property in the implicit target project echo${ant.project.invoked-targets}/echo target name=one/ target name=two/ /project You could use that only inside a

AW: ant.project.invoked-targets

Ok, I've updated the manual. Jan -Ursprüngliche Nachricht- Von: Stefan Bodewig [mailto:bode...@apache.org] Gesendet: Montag, 23. Februar 2015 16:34 An: dev@ant.apache.org Betreff: Re: ant.project.invoked-targets On 2015-02-23, Jan Matèrne (jhm) wrote: The magic property

AW: question about an IDE

Hello Benjamin, I use Eclipse or JBoss Developer Studio (which is basically a pimped Eclipse). It is true, that some (I know one) Ant committer is or was involved in the development of Netbeans. But Netbeans is not developed by the Ant project. Never heard of jGrasp, so I can't tell anything

AW: ant git commit: don't forget to remove the temporary branch

I like #21 ;-) Good job updating that file (git, reporter.a.o) Jan -Ursprüngliche Nachricht- Von: bode...@apache.org [mailto:bode...@apache.org] Gesendet: Donnerstag, 4. Juni 2015 06:27 An: notificati...@ant.apache.org Betreff: ant git commit: don't forget to remove the temporary

AW: [VOTE] Release Ant 1.9.5 based on RC1

+1 Jan -Ursprüngliche Nachricht- Von: Nicolas Lalevée [mailto:nicolas.lale...@hibnet.org] Gesendet: Mittwoch, 3. Juni 2015 10:54 An: Ant Developers List Betreff: Re: [VOTE] Release Ant 1.9.5 based on RC1 +1 Nicolas Le 31 mai 2015 à 16:46, Stefan Bodewig bode...@apache.org

AW: Doing a quick 1.9.5.1? (was Re: ant git commit: COMPRESS-317 ArrayIndexOutOfBoundsException in ZipArchiveEntry#getMergedFields)

Same for me. Can't judge over the extra field. But we should keep 3-part version numbers. Jan -Ursprüngliche Nachricht- Von: Nicolas Lalevée [mailto:nicolas.lale...@hibnet.org] Gesendet: Mittwoch, 10. Juni 2015 18:55 An: Ant Developers List Betreff: Re: Doing a quick 1.9.5.1? (was

WG: [Bug 13048] Add an optional containsall attribute to LineContains

While going through the buglist I found this one. If I understand the comments right, the code was integrated in 1.5.1. But it is not present in 1.9.6/trunk. Should we integrate that code? We should close that issue ;) Jan -Ursprüngliche Nachricht- Von: bugzi...@apache.org

AW: Doing a quick 1.9.5.1? (was Re: ant git commit: COMPRESS-317 ArrayIndexOutOfBoundsException in ZipArchiveEntry#getMergedFields)

Jan, I see you are fixing a few things, should I give you some time to finish your selected bugs? Yes, thanks. I'll ping you if I have finished. Most of the work is closing old issues. Some require more attention ... Jan -

AW: Doing a quick 1.9.5.1? (was Re: ant git commit: COMPRESS-317 ArrayIndexOutOfBoundsException in ZipArchiveEntry#getMergedFields)

Actually my time is over and I'll have to do some other work. So I can't invest more at the moment. So, Stefan, you could start a release. ;) Jan -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] Gesendet: Freitag, 12. Juni 2015 13:53 An: 'Ant Developers

AW: Planning 1.9.5

I had some fixes for the manual which I'll push today. We have two files for listing contributors: - CONTRIBUTORS - contributors.xml I haven't seen an instruction in ReleaseInstructions nor a xslt in the build.xml to generate the first file from the last. (But I also haven't find a xslt file for

AW: Planning 1.9.5

I pushed my changes, nothing more on my list, so I am out. ;) Jan -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] Gesendet: Donnerstag, 28. Mai 2015 09:02 An: 'Ant Developers List' Betreff: AW: Planning 1.9.5 I had some fixes for the manual which I'll

AW: Aspiring contributor here

I think that the most recent bugs are the changes with the most response. https://bz.apache.org/bugzilla/buglist.cgi?component=Core=bug_id%20DESC=Ant_based_on=_format=advanced=--- Choose a bug where you are interested in, read the bug comments, start a discussion on (this) dev list, open a PR on

AW: ReleaseNotes

Oh yes - just the step before "mine". I must be blind ... I'll revert that. Jan > -Ursprüngliche Nachricht- > Von: Stefan Bodewig [mailto:bode...@apache.org] > Gesendet: Dienstag, 1. Dezember 2015 15:16 > An: dev@ant.apache.org > Betreff: Re: ReleaseNotes > > On 2015-12-01, Jan

AW: ant git commit: build.xml: undo last change as it doesnt bring the desired result

I am working on bringing the Ant-Nightly back to work. So I am "deactivating" not (yet) working tools ... Jan > -Ursprüngliche Nachricht- > Von: j...@apache.org [mailto:j...@apache.org] > Gesendet: Freitag, 27. Mai 2016 10:11 > An: notificati...@ant.apache.org > Betreff: ant git commit:

AW: Build failed in Jenkins: AntLib-antunit #25

I try to understand, why AntUnit is failing on the CI ... (Works on my Win7 machine). Jan > -Ursprüngliche Nachricht- > Von: Apache Jenkins Server [mailto:jenk...@builds.apache.org] > Gesendet: Freitag, 24. Juni 2016 12:40 > An: notificati...@ant.apache.org > Betreff: Build failed in

AW: [VOTE] Adopt Java8 as Baseline for 1.10 on master Branch

+1 for Java8. For old java versions we have the 1.9-branch. Jan > -Ursprüngliche Nachricht- > Von: Roger and Beth Whitcomb [mailto:rogerandb...@rbwhitcomb.com] > Gesendet: Dienstag, 22. März 2016 18:14 > An: dev@ant.apache.org > Betreff: Re: [VOTE] Adopt Java8 as Baseline for 1.10 on

compatibility matrix

What is with http://ant.apache.org/faq.html#java-version Jan > -Ursprüngliche Nachricht- > Von: Stefan Bodewig [mailto:bode...@apache.org] > Gesendet: Dienstag, 22. März 2016 19:05 > An: dev@ant.apache.org > Betreff: Re: [VOTE] Adopt Java8 as Baseline for 1.10 on master Branch > > On

AW: [RESULT] Adopt Java8 as Baseline for 1.10 on master Branch

I added some notes to Stefans list. Some more to do? Jan * create a branch 1.9.x that we use for Java5 compatible maintenance releases * create Jenkins Matrix Build: win/linux java5-8 * create Gump Job Java5+Ant1.9.x * change the version number of the master branch to 1.10.0alpha (-SNAPSHOT,

AW: ant git commit: requires Ant 1.10+. For the (nightly) build it is not that important.

> > requires Ant 1.10+. For the (nightly) build it is not > that important. > > Shouldn't the nightly builds just use the bootstrapped version of Ant > rather than an installed one? Yeah, but playing with the Jenkins config requires lot of time as the current load is huge ... Have to rework

AW: Regexp mapper + Zip task on Windows

The URLs have changed. Currently the nightly build job at ASF is at https://builds.apache.org/view/All/job/Ant_Nightly/ But the last one failed BUILD FAILED /home/jenkins/jenkins-slave/workspace/Ant_Nightly/build.xml:1182: The following error occurred while executing this line:

AW: archiving EasyAnt

Retire: Issue Tracker - If the subproject/component has its own issue tracker we have to close that. It is enough to make it read-only, so these information are longer available. --> open; use Jira EASYANT --> asked infra per https://issues.apache.org/jira/browse/INFRA-13225

AW: Multi-Release JARs

I did a simple version using plain and . Jan > -Ursprüngliche Nachricht- > Von: Stefan Bodewig [mailto:bode...@apache.org] > Gesendet: Sonntag, 18. September 2016 12:21 > An: dev@ant.apache.org > Betreff: Re: Multi-Release JARs > > On 2016-09-17, Ja

AW: Multi-Release JARs

is inside the class file. Any idea? Jan > -Ursprüngliche Nachricht- > Von: Stefan Bodewig [mailto:bode...@apache.org] > Gesendet: Mittwoch, 21. September 2016 19:03 > An: dev@ant.apache.org > Betreff: Re: Multi-Release JARs > > On 2016-09-21, Jan Matèrne (jhm

AW: Multi-Release JARs

In the current "Java Spectrum" there is an article about some Java9 topics, including the multi-release-jar. They point to a Maven proof of concept. So we could (should) have a look there, too. https://github.com/hboutemy/maven-jep238 > Things I see we could do (and I'm sure this list is not

AW: Build failed in Jenkins: Ivy-tests » JDK 1.5 (latest),Windows #157

I dont have any idea why this build doesnt work. Have tried changing the label from (each) ubuntu to every ubuntu without H12 (where the last builds were). Finally I "copied" the job (without email-notification) https://builds.apache.org/job/Ivy-tests-matrix

AW: DISCUSS How to retire a subproject/component

There aren't as many comments as I hoped to get ... A main comment was that we also need a process of reactivating a subproject. So here are the updated proposals for the two processes/todo-lists. Again - please comment. Jan -- The retirenment of a

AW: VOTE Retire IvyDE

> Considering the current discussion around IvyDE and the involvement of > Gintas, maybe we could cancel this vote, at least postpone it ? > > Nicolas Yes, I agree. The discussion and the vote about retiring IvyDE had brought much more activity than the months before (as I recognized). But I

AW: VOTE Retire EasyAnt subproject - RESULT

The vote about archiving EasyAnt starts on 05.December 2016 [1]. The result is: * binding votes +1: Jan, Stefan, Nicolas, Conor, Jean-Louis, Dominique 0: -- -1: -- * non binding votes +1: -- 0: -- -1: -- The vote passed and EasyAnt including all its subcomponents will be

AW: VOTE Retire IvyDE - RESULT

The vote about archiving IvyDE starts on 05.December 2016 [1]. The result is: * binding votes +1: (Jan), (Nicolas), Jean-Louis, Dominique, 0: Stefan -1: -- asks for cancelling: Nicolas [3], Jan [4] * non binding votes +1: -- 0: -- -1: Gintas [2] I interpret the asks for

archiving EasyAnt

The vote about archiving EasyAnt passed [1]. So according to [2] the todo list is: Retire: Version Control --- Most of our source code is in git, only "site" and "sandbox" use subversion. --> only git for sources. Homepage in svn. We place a marker RETIRED_PROJECT file on

AW: IvyDE status

changed that, thanks Jan > -Ursprüngliche Nachricht- > Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com] > Gesendet: Freitag, 16. Dezember 2016 18:22 > An: Ant Developers List > Betreff: Re: IvyDE status > > One more thing: http://ant.apache.org/git.html still links to >

AW: VOTE Retire IvyDE

> Very well, how does one revive a project? > > Gintas If you ask for the process of reactivating it after archiving, that's documented at http://ant.apache.org/processes.html. But ATM it is still alive - but sleeping. ;-) Jan

AW: Thoughts on Next Release

Yep. Jan > -Ursprüngliche Nachricht- > Von: Maarten Coene [mailto:maarten_co...@yahoo.com.INVALID] > Gesendet: Freitag, 13. Januar 2017 13:42 > An: Ant Developers List > Betreff: Re: Thoughts on Next Release > > Agreed. > Maarten > > > Van: Stefan Bodewig >

AW: DISCUSS How to retire a subproject/component

> > - release further resources > > > > Maybe a subproject locks further resources (update-site, ...). So we have > > to release them? > > I don’t understand this. How a retirement of a sub project should > trigger the release of a related project ? This is a misunderstanding in my wording.

AW: Ivy - any future or is it also going to be retired?

> I thought Ivy was used extensively by Gradle? I see generated ivy.xml > files after running a normal Gradle build, so it still seems to be > important in that space. I don't know. But haven't thought to retire Ivy itself. Jan

AW: Ivy - any future or is it also going to be retired?

> If you want to push Ivy, you need integrations with IDE. Yes, I agree. But the problem getting developers to improve IvyDE. > IMHO, IvyDE works well with Eclipse; IvyDE will be available as it is. We don't delete releases as they are archived in the Apache archive. > perhaps its

VOTE Retire IvyDE

I start a vote for retiring IvyDE. The last release was in 11/2013. The last 'real' code activity was in 08/2014. It seems that we havent the community, committers and PMC to hold this subproject. The general procedure is described in http://ant.apache.org/processes.html. I start

VOTE Retire EasyAnt subproject

I start a vote for retiring EasyAnt and all its components: - core - buildtypes - plugins - skeletons - tasks - easyant4e We never had a real release after the incubator. The last 'real' activity in vcs was in 09/2015 for EA-Core and 07/2013 for EA4E. It seems that we havent the

AW: Ivy - any future or is it also going to be retired?

We see Ivy as a widely used component. We use archiving some components to recalibrate our focus. I don't think that we want to archive Ivy in the near future. Instead we try to push Ivy. If you want to help with Ivy, you're welcome. "It's already a challenge to stick with Ivy build system

AW: DISCUSS How to retire a subproject/component

Thanks for feedback. > Since some of the subtitles are common between « Retire » and « > Reactivate », there are duplicate anchors, so some links are not > working as expected. Fixed by adding a prefix "retire: " / "reactivate: " > In http://materne.de/ant/processes.html#mailing list >

AW: DISCUSS How to retire a subproject/component

November 2016 13:35 > An: dev@ant.apache.org > Betreff: Re: DISCUSS How to retire a subproject/component > > On 2016-11-30, Jan Matèrne (jhm) wrote: > > >> This topic raises another question. What should we do about the > >> artifact released in dist ? I gue

AW: archiving EasyAnt

Back from holiday I want to do more about archiving EasyAnt. My todo-list now is... there are some questions open I couldnt answer ... Jan Retire: Version Control --- Most of our source code is in git, only "site" and "sandbox" use subversion. --> only git for sources.

[ANN] Retirement of Ant subproject 'EasyAnt'

The Ant PMC voted [1] to archive the EasyAnt subproject and all its modules. This means that all its resources are removed or made read only and no further development will be done. It also means that, if a community grows, the subproject could reactivated [2]. Happy new year Jan Matèrne,

AW: archiving EasyAnt

Current status: Jan Retire: Version Control --- Most of our source code is in git, only "site" and "sandbox" use subversion. --> only git for sources. Homepage in svn. --> update EA-homepage --> Should we only place a note on the hp or completely remove them. I prefer

<    1   2   3   4   5   6   7   >