At 16:28 +0200 06-08-2003, Kaj Hejer wrote:
>At 22:07 +0200 05-08-2003, Kaj Hejer wrote:
>>At 21:17 +0200 09-05-2003, Ulrich Köster wrote:
>>>Hi,
>>>
>>>why not add a RFE for it. It should't be too much work to add this
>>>stuff to the woapplication task. May be an otional attribute for the
>>>chmod command.
>>>
>>>http://sourceforge.net/tracker/?group_id=50507&atid=459970
>>
>>
>>Hi!
>>
>>Thank you for implementing this feature!
>>
>>It seems to me that in woproject 1.0.4 the script that starts thee
>>application (.../myapp.woa/myapp) is chmoded to 754 (-rwxr-xr--) if
>>there isn't any chmod attribute.
>>
>>What about not chmod'ing when there isn't any chmod attribute? Do you
>>think that is a good idea?
>
>
>I have filed a bugreport on this one (#784207).
Hi!
I have added the following comment to this bugreport:
---This bugreporrt is incorrect. I have now been reading the doc at http://objectstyle.org/woproject/ant/woapplication.html which says:
"chmod | Optional value for the chmod command executed by the WOApplication task. The default is "gu+x". The chmod command is only executed on the first build of the application and only on "Unix" platforms. "
That mean that woproject is bahaving as it is described in the documentaion and this is no bug.
What might be an issue is that the defaultvalue for the chmod-command should be something else than "gu+x", f.x. 750 since then you would be sure what the access rights would be after installing and app which you don't know if you use "gu+x" since that would depend on what they where before the chmod.
---
-Kaj :)
This archive was generated by hypermail 2.0.0 : Mon Aug 11 2003 - 07:53:17 EDT