AFAIK you start CC using a wrapper buildfile which uses <ant> to call the real buildfile.
You could use <java> instead of <ant>, so you could pass <permission>s. (BTW should we add permission-support to <ant>?) Jan >-----Ursprüngliche Nachricht----- >Von: Antoine Levy-Lambert [mailto:[EMAIL PROTECTED] >Gesendet: Donnerstag, 12. Oktober 2006 13:28 >An: Ant Users List >Betreff: Re: How To Jail Ant Script by Options > > >Hi, > >there is no such ant option. > >Maybe with a java security policy file you could achieve this ? >You will need to allow room for temporary files anyway, or set >java.io.tmpdir at startup. > >VM parameters put in the ANT_OPTS environment variable are >used when ant starts from the command line with the supplied >ant.bat or ant scripts. > >I do not know how to do this with CruiseControl, maybe >CruiseControl invokes directly the Ant main class ? > >Regards, >Antoine > >Alexandre CABROL PERALES wrote: >> Hi everybody. >> I use cruise control over Ant. >> And i've many projects managed by cruise control on >different folders. >> How can i avoid that build.xml script can access to upper >folder by an >> ant option. >> >> I cant lock build.xml content so i need to jail each script >execution >> in it folder. >> >> Could you help me? >> >> Thanks, >> Kalden >> Administrator of http://dev.labo-linux.org >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] For >additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
