Jason,
some questions probably answered elsewhere. 1) Multiple source directories are currently used to get around the lack of a multi-project build or project inheritance. Will this feature be in the new release mentioned? 2) If we remove the 'type' from dependencies, is there someway to specify the dependency is for testing vs runtime vs ??? I prefer one source directory myself :-) -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers Jason van Zyl <jvanzyl@zenpl To: Turbine Maven Developers List ex.com> <[EMAIL PROTECTED]> cc: 05/29/02 05:07 Subject: Any POM problems? AM Please respond to "Turbine Maven Developers List" Hi, I just wanted to try to stimulate a discussion on any of the problems anyone has seen with the POM so far. I would like to cut another release but the next version I would like to promote a little more heavily so it would be nice to get something closer to a final structure. I think we've decided in IRC that: -> one source directory on all fronts -> remove the <type> element from the <dependency> element as the new dep engine will deal with the computation of dependencies -> making the <jar> element in the <dependency> element optional as it can be synthesized from the name and version of the dependency and hopefully we won't need this at all eventually when all the jars are named correctly. So if anyone else has any digs to make lets hear 'em :-) -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED]> For additional commands, e-mail: < mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
