Re: Ant1.8 copy task gives error "Failed to copy" with "Permission denied"
>> The error is about /u/kumari/main/shailja/bin/share/run_m.pl not the file you mention. Could there be a symbolic link somewhere that Ant tries to traverse but can't? >> Copy task is copying from /u/kumari/main/shailja/src/java/a/jsh/mm/script/run_m.pl to /u/kumari/main/shailja/bin/share/run_m.pl location Before executing copy task /u/kumari/main/shailja/bin/share/run_m.pl does not exists. There is no symlink anywhere in /u/kumari/main/shailja/bin/share, that ant tries to traverse. Anyways this error is comming only with ant1.8.0 not with ant1.7.1. I am not sure about the behavior of ant. :( Stefan Bodewig wrote: > > On 2010-04-08, SHAILJA wrote: > >> When I use ant1.8.0, it gives error like this > >> Failed to copy /u/kumari/main/shailja/src/java/a/jsh/mm/script/run_m.pl >> to >> /u/kumari/main/base/bin/share/run_m.pl due to >> java.io.FileNotFoundException >> /u/kumari/main/shailja/bin/share/run_m.pl (Permission denied) > >> But I have file /u/kumari/main/shailja/src/java/a/jsh/mm/script/run_m.pl >> with correct permission. > > The error is about /u/kumari/main/shailja/bin/share/run_m.pl not the > file you mention. Could there be a symbolic link somewhere that Ant > tries to traverse but can't? > > 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-tp28179282p28188260.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: Ant1.8 copy task gives error "Failed to copy" with "Permission denied"
On 2010-04-08, SHAILJA wrote: > When I use ant1.8.0, it gives error like this > Failed to copy /u/kumari/main/shailja/src/java/a/jsh/mm/script/run_m.pl to > /u/kumari/main/base/bin/share/run_m.pl due to java.io.FileNotFoundException > /u/kumari/main/shailja/bin/share/run_m.pl (Permission denied) > But I have file /u/kumari/main/shailja/src/java/a/jsh/mm/script/run_m.pl > with correct permission. The error is about /u/kumari/main/shailja/bin/share/run_m.pl not the file you mention. Could there be a symbolic link somewhere that Ant tries to traverse but can't? Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Ant 1.8.1
Hi, I was thinking of Ant 1.8.1. I would like to shoot a build next week. Maybe call it 1.8.1_RC1 ? Or directly 1.8.1 We have 16 fixed bugs and 12 other changes already. Thoughts ? Regards, Antoine - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Ant1.8 copy task gives error "Failed to copy" with "Permission denied"
Hi All, I used ant1.8.0 to build my project. In build.xml I have following lines of code. I am putting snippet of code as only copy section gives me error. When I use ant1.8.0, it gives error like this Failed to copy /u/kumari/main/shailja/src/java/a/jsh/mm/script/run_m.pl to /u/kumari/main/base/bin/share/run_m.pl due to java.io.FileNotFoundException /u/kumari/main/shailja/bin/share/run_m.pl (Permission denied) But I have file /u/kumari/main/shailja/src/java/a/jsh/mm/script/run_m.pl with correct permission. Note: The above error is not comming with ant1.7.1 Is it a bug in ant1.8.0 or somewhere I am doing wrong here ? -- View this message in context: http://old.nabble.com/Ant1.8-copy-task-gives-error-%22Failed-to-copy%22-with-%22Permission-denied%22-tp28179282p28179282.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: Augment feature
My opinion is that what we really need is a VOTE thread: > > 1. Are you in favor of adding the augment feature to Ant? > Definitively +1 > 2. Are you in favor of an attribute that allows references to be marked > as final, to avoid augmentation? > If both things ( task and making "final" references) are separated i'm +1 > 3. If a final attribute is decided upon, do you think it should default > to "false"? > +1 As with current code base ant datatypes are currently de-facto mutable we should keep the default value of final attribute to false. -- Jean Louis Boudart Independent consultant Project Lead http://www.easyant.org
Re: Augment feature
Maybe you could spread the discussion in two different parts : > > - adding an augment task > - adding a new attribute final to datatypes > +1 > > With AspectJ it would be possible to add an attribute final and make it be > really enforced by all tasks. > > I am reluctant for complex features also because I am afraid we could start > something that we will not have the time to finish 100% and will deliver > with bugs. Make sense. As the two things (augment task / final attributes on datatypes) can be separated, maybe we could status first on the augment feature which is really simple. Introducing kind of final attribute on datatypes requires some larger discutions (due to the complexity behind). Maybe this means that there should be private references which are only accessible within a certain scope. If I understand well, in easyant you develop standard build files, which > contain datatype instances with id(s) > and you do not want your users to fiddle with these datatype instances. > Even if there is an attribute "final", users who want to change the > datatype instances will find a way around it. > Unless the enforcement of final="true" is at the java runtime level (for > instance with AspectJ). > Most of the time i would like to keep it flexible, easy to use and easily extendable. Being able to augment the fileset, etc... make sense. The task is really appropriate here because it can strongly simplify the user experience to adapt things to their needs. On the other hand, in a few cases we need to provide structuring stuff, and changing this structure requires some reflections. So here limiting this facility by introducing kind of "final=true" make sense. The idea is not to lock the user and to fully restrict the access. If he want to to change structuring things he will still be able to do it but it will not be as simple as just as ing a datatype. Even if we provide some stucturing stuff we should not lock the user in. IMHO, this make particular sense in easyant but could also be applied in the Ant context. Regards, -- Jean Louis Boudart Independent consultant Project Lead http://www.easyant.org
