On 5/25/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Nicolas Chalumeau wrote: > > >There is still a question : Is there any importance that a m2 plugin > >depends on ant ? The idealistic (sorry i like this word;) ) responce > >will be no. but for all plugin, only m2 project hosted one ... Here > >it's just curiousity > > > > > > > I'm not quite sure what you mean. It is not a problem for an m2 plugin > to depend on Ant if it wants to use it, if you want to do that - just > like any other Java dependency. There is no special Ant support in m2 > (except for the tasks we are additionally building), other than access > via scripting languages that support it (but that support is all up to > the scripting languages).
I have similar usecaser to Nicolas, however the ant tasks I'm using are 3rd party ones and there's a lot of logic in them so rewriting doesn't look like an option to me. (there will also be maintainance cost to keep in synch with the changes in the ant tasks). This may be a bit naive question, but my assumption was that I can just call teh ant tasks within java without any additional setup, just have the ant-related jars on classpath. Is that correct or is some setup necessary? If it's not as straightforward as I thought, I guess for me the best way would be to just rewrite the jelly wiring to marmalade. Apart from the ant tasks I use, I also have jelly tag library that I use for more manipulation that was impossible using jelly. That is also reusable using marmelade, I assume? thanks and regards. Milos Kleint --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
