Re: EasyAnt is graduating
All infra request are now closed. Migration seems over! Long live http://ant.apache.org/easyant/ PS: i think we forgot setuping redirection from incubator.a.o/easyant to ant.a.o/easyant. I will fix this today Le 23 mars 2013 15:25, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Le 16 mars 2013 à 01:39, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Finally ! We're there ! Now we need to move stuff. EasyAnt is graduating like Ivy did, so about the resources, here is the following suggestions. * The svn tree We will move the svn tree of EasyAnt under Ant's one. Everything except 'KEYS' and 'site' under http://svn.apache.org/repos/asf/incubator/easyant/will move into http://svn.apache.org/repos/asf/ant/easyant. done. We'll give write rights to EasyAnt committers on the entire Ant svn tree. We need to give r/w rights to Jérôme Benois (jbenois) and Siddhartha Purkayastha (kpsiddharth). * The website EasyAnt website is using the same publication mechanism as Ant. We'll need to move the svn tree of the site from http://svn.apache.org/repos/asf/incubator/easyant/site/ to http://svn.apache.org/repos/asf/ant/site/easyant. done. The web site will be at http://ant.apache.org/easyant We'll need to create an INFRA ticket about the move: - redirect from incubator/esayant to ant.apache.org/easyant (via http://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess) I'll do as soon as the following infra ticket is closed. - change the svnpubsub https://issues.apache.org/jira/browse/INFRA-6048 * The mailing lists: - easyant-dev@ will be closed in favor of dev@ant.apache.org - easyant-commits@ will be closed in favor of notificati...@ant.apache.org - easyant-private@ just closed. https://issues.apache.org/jira/browse/INFRA-6049 * Jira: No need to do anything I think: https://issues.apache.org/jira/browse/EASYANT Just need to notify the infra that the notification list is now notificati...@ant.apache.org https://issues.apache.org/jira/browse/INFRA-6050 Maybe some changes in the Gump metadata and Jenkins jobs? Good catch. There is nothing in Gump about EasyAnt but there is in Jenkins. I'll update it too. done. Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: EasyAnt is graduating
On 2013-03-27, Jean-Louis Boudart wrote: PS: i think we forgot setuping redirection from incubator.a.o/easyant to ant.a.o/easyant. I will fix this today There may be some cleanup to do inside the Incubator site itself as well. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: EasyAnt is graduating
As far as I can tell, the status of EasyAnt on the incubator pages are up to date, it is not listed anymore as an Incubator project. There was still things in the svn, kept because we needed to wait for the site to be moved. I have just completely deleted it cf r1461470. I also just put in place a redirection of http://incubator.apache.org/easyant to http://ant.apache.org/easyant cf r1461474. Again I am not familiar with the publishing process of the incubator site. So it's not active yet. The last resource standing is the published release. But it needs to stay there until we have a new release here. Nicolas Le 27 mars 2013 à 10:30, Jean-Louis Boudart jeanlouis.boud...@gmail.com a écrit : Do you mean the incubator logo on easyant site? or stuff at http://incubator.apache.org/projects/easyant.html ? 2013/3/27 Stefan Bodewig bode...@apache.org On 2013-03-27, Jean-Louis Boudart wrote: PS: i think we forgot setuping redirection from incubator.a.o/easyant to ant.a.o/easyant. I will fix this today There may be some cleanup to do inside the Incubator site itself as well. 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: svn commit: r1461421 - in /ant/core/trunk/manual/Tasks: ear.html jar.html war.html zip.html
On 03/27/2013 02:02 AM, bode...@apache.org wrote: URL: http://svn.apache.org/viewvc/ant/core/trunk/manual/Tasks/zip.html?rev=1461421r1=1461420r2=1461421view=diff - brPossible values are never, always and not-encodable + brPossible values are never, always and not-encodeable Is this the actual enum value? Because “encodable” would be the correct English spelling. (java.lang.Cloneable was the product of ignorance and seems to have spawned a generation of mistakes.) - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: svn commit: r1461421 - in /ant/core/trunk/manual/Tasks: ear.html jar.html war.html zip.html
On 2013-03-27, Jesse Glick wrote: On 03/27/2013 02:02 AM, bode...@apache.org wrote: URL: http://svn.apache.org/viewvc/ant/core/trunk/manual/Tasks/zip.html?rev=1461421r1=1461420r2=1461421view=diff - brPossible values are never, always and not-encodable + brPossible values are never, always and not-encodeable Is this the actual enum value? yes. Zip.java line 2150 Because “encodable” would be the correct English spelling. (java.lang.Cloneable was the product of ignorance and seems to have spawned a generation of mistakes.) Quite possible. I didn't spell check it when I wrote the code and nobody seems to have spotted it either. Added in 1.8.0. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: svn commit: r1460264 - in /ant/core/trunk: WHATSNEW build.xml src/etc/poms/ant-junit/pom.xml src/etc/poms/ant-junit4/ src/etc/poms/pom.xml
+* the optional ant-junit4.jar has been merged into ant-junit.jar + as Ant now requires JUnit4. Is it really the case that Ant requires JUnit4? The changes I introduced for @Ignore annotations in Ant 1.9.0 shouldn't impact backwards compatibility with JUnit3 and I don't believe any other changes in the 1.9.0 release force users to need the JUnit4 jar whilst running tests. JUnit3 is still available for downloading from various sites and users working against older codebases may still have it bundled in their workspace so it's not infeasible that someone way want to run tests using JUnit3 and Ant 1.9.0 or above. That being said, it should be possible for users to drop the JUnit4 jar in as a direct replacement to the JUnit3 jar in these cases; so we wouldn't be forcing users wanting to upgrade Ant to perform particularly high risk tasks. The real question is: was there a technical reason for making this change or are we just looking to limit limit the dependency on older libraries? If the switch to JUnit4 is intentional then the JUnit task could do with some tidying up to remove Java 1.4 checks, remove the reflection used to guard against JUnit4 not being on the classpath, and merge the split of code used to protect JUnit3 backwards compatibility. I currently have changes pending (for once I get commit access) which will allow the JUnit task to be 'intelligent' about which classes it passes to the JUnit core [1] and am happy to perform a bit of tidy up/refactor of the existing JUnit task code at the same time if we're guaranteeing JUnit4 is on the classpath when the JUnit task if called. Thanks,Michael [1] https://github.com/mc1arke/ant/commits/JUnitNonTestsSkipped
