Re: [VOTE] Ant source tree reorganization
Hi, I was just wondering that if you're going to reorganize the whole source tree and have distinct structure for each produced jar, maybe we could use easyant :). Note that the next release of easyant will provide a maven-publisher plugin. Ping me if you want to POC this or have more informations In any case here is my vote : 2010/5/18 Jesse Glick jesse.gl...@oracle.com 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. -- Jean Louis Boudart Independent consultant Project Lead http://www.easyant.org
Re: Ant1.8 copy task gives error Failed to copy with Permission denied
Hi Stefan,
Sounds like you are hitting the problem described in the recently opened
https://issues.apache.org/bugzilla/show_bug.cgi?id=49261
When the above mentioned bug will be fixed?
Stefan Bodewig wrote:
On 2010-05-07, SHAILJA shalja.ru...@gmail.com wrote:
I tried to debug my problem with small example. It seems something has
changed in copy target with ant1.8.0. We change permission of
destination
file after copy. With ant-1.7.1 copy target copied the source file if
source
file is newer than destination file but with ant-1.8.0 copy target
failed.
My small build.xml is
==
/u/kumari/ant less less build.xml
project
target name=install_scripts
copy file=${basedir}/myfile.txt tofile=/u/kumari/myfile.txt/
chmod file=/u/kumari/myfile.txt perm=555/
/target
/project
Sounds like you are hitting the problem described in the recently opened
https://issues.apache.org/bugzilla/show_bug.cgi?id=49261
I haven't found the time to fully look into this but think Ant should
not overwrite read-only files by default - so this part would be a fix
rather than a regression. It probably should do so if the overwrite
attribute has been set to true, but the bug report says ant doesn't do
so either.
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
--
View this message in context:
http://old.nabble.com/Ant1.8-copy-task-gives-error-%22Failed-to-copy%22-with-%22Permission-denied%22-tp28179282p28593129.html
Sent from the Ant - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant source structure and ant*.jar build products
That is not what I meant. I meant dependences for maven pom files. We would have an jar file (for example ant-commons-logging.jar that did not contain any classes) and have a pom file like: project parent groupIdorg.apache.ant/groupId artifactIdant-parent/artifactId relativePath../pom.xml/relativePath version1.8.2/version /parent modelVersion4.0.0/modelVersion groupIdorg.apache.ant/groupId artifactIdant-commons-logging/artifactId version1.8.2alpha/version descriptionAnt Listener based on commons-logging/description dependencies dependency groupIdorg.apache.ant/groupId artifactIdant/artifactId version1.8.2/version scopecompile/scope /dependency dependency groupIdcommons-logging/groupId artifactIdcommons-logging-api/artifactId version1.0.4/version scopecompile/scope /dependency /dependencies /project This would allow maven users to use ant.jar and specify which optional parts are needed. Peter On Tue, May 18, 2010 at 6:17 AM, jan.mate...@rzf.fin-nrw.de wrote: We could have dummy jar's for dependences. Peter You could use https://svn.apache.org/repos/asf/ant/sandbox/mocks ;-) Jan - 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: Ant1.8 copy task gives error Failed to copy with Permission denied
On 2010-05-18, SHAILJA shalja.ru...@gmail.com wrote: Stefan Bodewig wrote: Sounds like you are hitting the problem described in the recently opened https://issues.apache.org/bugzilla/show_bug.cgi?id=49261 When the above mentioned bug will be fixed? Like the bug report says, it is already fixed in trunk and will be fixed in the next release (after 1.8.1). The fix may not be what you expect, though. The next release will never overwrite read-only files with copy unless you explicitly set a force attribute to make it do so. For Ant 1.8.0 and 1.8.1 there is a workaround - make copy use the filtering mode (i.e. add a filterset that doesn't change your files at all) and it will overwrite read-only files just like 1.7.1 did. This workaround won't work anymore with the next release. Stefan - 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 2010-05-18, Jesse Glick jesse.gl...@oracle.com 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. [ ] 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. I have a preference for leave it the way it is but not strong enough to vote against a split. Count that as an abstain. 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. Yes, merge them. We might leave an empty ant-nodeps.jar around if this helps downstream distributors. Stefan - 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 05/18/2010 04:02 AM, Jean-Louis Boudart wrote: I was just wondering that if you're going to reorganize the whole source tree and have distinct structure for each produced jar, maybe we could use easyant I wasn't intending to use EasyAnt, though I imagine that would be a reasonable incremental change later. - 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 17/05/2010 7:11 PM, 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. [ ] 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. Like Stefan, I'm going to abstain. I don't like the reorganization, but recognize that maintaining the selectors as they exist right now is problematic and bug prone. Looking forward to the long-ago promised day that we could break backwards API compatibility with an Ant 2.0 release and reorganize the classes into a more sensible package structure. Ahh well, someday. 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. Big fan of that. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [GUMP@vmgump]: Project test-ant (in module ant) failed
Two failures: [au:antunit] Build File: /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/exec/apply-test.xml [au:antunit] Target: testRedirector13 FAILED [au:antunit]at line 580, column 50 [au:antunit]Message: Expected log to contain '/tmp/testinput/x ERROR!!!' at level info [au:antunit]took 8.816 sec [au:antunit] Build File: /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/xslt-test.xml [au:antunit] Target: testTraceJdk15+ FAILED [au:antunit]at line 170, column 65 [au:antunit]Message: Unexpected log 'Failed to enable tracing' at level info [au:antunit]took 0.014 sec Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
