Summary: | Task 'get' should should allow alternative paths. | ||
---|---|---|---|
Product: | Ant | Reporter: | Gustav Weber <gustav_weber75> |
Component: | Core tasks | Assignee: | Ant Notifications List <notifications> |
Status: | NEW --- | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Gustav Weber
2008-03-23 06:08:48 UTC
I dont know what the most popular use of <get> is; certainly in my projects its probing webapps I've just deployed. Looking at this and your other list of requirements, I can see you are trying to use <get> for library management. Can I point you at our affiliate project, Ivy, that handles all this for you? > Looking at this and your other list of requirements, I can see you are trying > to use <get> for library management. Yes, but a very very simple management, like it's done in many open source projects like: FreeMarker: http://freemarker.svn.sourceforge.net/viewvc/freemarker/trunk/freemarker/build.xml or even better Click Frameowrk: http://click.sourceforge.net/docs/building.html#ant-targets (see get-deps task) > Can I point you at our affiliate project, > Ivy, that handles all this for you? I'm aware of Ivy(and used it) but I think it's an overkill for most simple projects(and one could have used Maven as well), and for that very simple reason ANT would just do it. I also don't think this would be any duplication with IVY since Ivy would handle complex situations. For very simple projects however were only a few jars are present, the tasks I descibed would solve the problems and would pose no learning barrier to the (new)users (exactly the main argument of ANT over maven). Thank you, Gustav. |