> Piroumian, Konstantin wrote: > > > > > > > IMO, it's not a very good idea to determine which parts of Cocoon > > one need, > > depending on presence of *.jars. So, for example, if in case when I don't > > need some optional component then I have to delete its JAR from my Cocoon > > repository and run build after that. Next time I'll have to copy > > it back to > > try it. > > > > It'll be much better to have a special build option for optional parts. > > Maybe a list of needed extensions in a .property file. E.g.: > > > > build webapp -Dinclude-ext=mini-cocoon.properties > > build webapp -Dinclude-ext=cocoon-with-deli.properties > > etc. > > > > Yes, you're absolutely right and - believe it or not - I tried to put > something like > you suggested into the build system several weeks ago. As you can imagine > without success. The main problem for me was to combine the two conditions: > the availability of the tested optional class and the definition of the > build option. For this something like an "and" condition is required, which > I didn't find in ant - so I gave up... >
I've asked our ant expert and he pointed me out to this doc: http://jakarta.apache.org/ant/manual/CoreTasks/condition.html Maybe you've known about it, but it seems that this is what you are looking for. Konstantin > Carsten > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
