[
http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Gusakov updated MERCURY-65:
--------------------------------
Component/s: (was: Ant tasks)
Remaining Estimate: 0 minutes
Original Estimate: 0 minutes
Proposal #2 seem to be the most convenient. On one hand it naturally blends
with Ant path, on the other hand - it provides a container for either nested
<dependency> elements or can have an attribute pom="/path/to/pom"
As <dependencies/> has a different sematics in maven-ant, will have to use
something else for the container name: something like <depset />
So it should works like:
{code}
<javac src=...>
<classpath>
<depset pom="my-pom.xml"/>
</classpath>
</javac>
{code}
and
{code}
<javac src=...>
<classpath>
<depset>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</depset>
</classpath>
</javac>
{code}
> Implement "old" maven-ant syntax
> ---------------------------------
>
> Key: MERCURY-65
> URL: http://jira.codehaus.org/browse/MERCURY-65
> Project: Mercury
> Issue Type: Improvement
> Components: Ant tasks
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> * As there are a lot of users that expect some kind of "investment protection"
> * simplify to allow "3 line" solutions for common tasks
> * introduce defaults - default repository, default dependency set
> * merge mercury: deps and mercury:resolve into one dependencies task
> * show how to inline mercury classpath in the build.xml instead of ~/.ant/lib
> * expose "transitive" option from "resolve" task - for non-transitive reading
> from repos
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
