Well, yeah... I know that you can just set restricted="false" - I said as much. But this opens the flood gates for all kinds of malicious behavior. As far as I know, javadoc should be safe enough to run in restricted mode.
It would be nice to be able to run javadoc _without_ having to set restricted to "false". On Mon, Mar 23, 2009 at 9:15 AM, Archie Cobbs <[email protected]> wrote: > You can do this already. You just have to set restricted="false" in your > configuration of the packager resolver. Documentation is > here<http://ant.apache.org/ivy/history/latest-milestone/resolver/packager.html> > . > > -Archie > > On Sun, Mar 22, 2009 at 2:28 PM, Stephen Woods <[email protected]> wrote: > >> The packager resolver limits the types of ant commands a packager uses >> to build its appropriate artifacts. Many of the source distributions >> do not bundle pre-generated javadoc, but they do bundle source. It >> would be nice to be able to run the javadoc ant task during the >> packaging process in order to make javadoc artifacts without needing >> to set the restricted attribute to "false". Is it even possible to >> compromise a system by running javadoc? >> >> Just a thought for future ivy releases... >> > > > > -- > Archie L. Cobbs >
