You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Oleg Gusakov (JIRA)" <ji...@codehaus.org> on 2008/12/19 19:38:19 UTC
[jira] Created: (MERCURY-65) Implement "old" maven-ant syntax
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
* 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
--
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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159016#action_159016 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/22/08 7:36 PM:
---------------------------------------------------------------
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 <dep /> for now
All 4 syntax samples will works:
{code:xml|title=dependencies from the pom}
<javac src=...>
<classpath>
<dep pom="my-pom.xml"/>
</classpath>
</javac>
{code}
and
{code:xml|title=embedded into embedded classpath}
<javac src=...>
<classpath>
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
</javac>
{code}
and
{code:xml|title=creates a new classpath}
<dep pathid="my-path">
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
<javac classpathref="my-path" ... />
{code}
and
{code:xml|title=embedded into named classpath}
<classpath id="my-path">
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
<javac classpathref="my-path" ... />
{code}
was (Author: olle):
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 <dep /> for now
All 4 syntax samples will works:
{code:xml|title=dependencie in the pom}
<javac src=...>
<classpath>
<dep pom="my-pom.xml"/>
</classpath>
</javac>
{code}
and
{code:xml|title=embedded into embedded classpath}
<javac src=...>
<classpath>
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
</javac>
{code}
and
{code:xml|title=creates a new classpath}
<dep pathid="my-path">
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
<javac classpathref="my-path" ... />
{code}
and
{code:xml|title=embedded into named classpath}
<classpath id="my-path">
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
<javac classpathref="my-path" ... />
{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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159016#action_159016 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/22/08 7:35 PM:
---------------------------------------------------------------
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 <dep /> for now
All 4 syntax samples will works:
{code:xml|title=dependencie in the pom}
<javac src=...>
<classpath>
<dep pom="my-pom.xml"/>
</classpath>
</javac>
{code}
and
{code:xml|title=embedded into embedded classpath}
<javac src=...>
<classpath>
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
</javac>
{code}
and
{code:xml|title=creates a new classpath}
<dep pathid="my-path">
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
<javac classpathref="my-path" ... />
{code}
and
{code:xml|title=embedded into named classpath}
<classpath id="my-path">
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
<javac classpathref="my-path" ... />
{code}
was (Author: olle):
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 <dep /> for now
All 4 syntax samples will works:
{code:xml}
<javac src=...>
<classpath>
<dep pom="my-pom.xml"/>
</classpath>
</javac>
{code}
and
{code:xml}
<javac src=...>
<classpath>
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
</javac>
{code}
and
{code:xml}
<dep pathid="my-path">
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
<javac classpathref="my-path" ... />
{code}
and
{code:xml}
<classpath id="my-path">
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
<javac classpathref="my-path" ... />
{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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159016#action_159016 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/22/08 7:25 PM:
---------------------------------------------------------------
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 <dep /> for now
All 3 syntax samples will works:
{code}
<javac src=...>
<classpath>
<dep pom="my-pom.xml"/>
</classpath>
</javac>
{code}
and
{code}
<javac src=...>
<classpath>
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
</javac>
{code}
and
{code}
<dep pathid="my-path">
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
<javac classpathref="my-path" ... />
{code}
was (Author: olle):
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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159016#action_159016 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/22/08 7:32 PM:
---------------------------------------------------------------
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 <dep /> for now
All 4 syntax samples will works:
{code:xml}
<javac src=...>
<classpath>
<dep pom="my-pom.xml"/>
</classpath>
</javac>
{code}
and
{code:xml}
<javac src=...>
<classpath>
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
</javac>
{code}
and
{code:xml}
<dep pathid="my-path">
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
<javac classpathref="my-path" ... />
{code}
and
{code:xml}
<classpath id="my-path">
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
<javac classpathref="my-path" ... />
{code}
was (Author: olle):
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 <dep /> for now
All 3 syntax samples will works:
{code:xml}
<javac src=...>
<classpath>
<dep pom="my-pom.xml"/>
</classpath>
</javac>
{code}
and
{code:xml}
<javac src=...>
<classpath>
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
</javac>
{code}
and
{code:xml}
<dep pathid="my-path">
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
<javac classpathref="my-path" ... />
{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
[jira] Updated: (MERCURY-65) Implement "old" maven-ant syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Gusakov updated MERCURY-65:
--------------------------------
Description:
* 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 reading resources from repos
was:
* 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
> 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
>
> * 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 reading resources 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
[jira] Updated: (MERCURY-65) Implement "old" maven-ant syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159016#action_159016 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/22/08 7:27 PM:
---------------------------------------------------------------
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 <dep /> for now
All 3 syntax samples will works:
{code:xml}
<javac src=...>
<classpath>
<dep pom="my-pom.xml"/>
</classpath>
</javac>
{code}
and
{code:xml}
<javac src=...>
<classpath>
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
</javac>
{code}
and
{code:xml}
<dep pathid="my-path">
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
<javac classpathref="my-path" ... />
{code}
was (Author: olle):
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 <dep /> for now
All 3 syntax samples will works:
{code}
<javac src=...>
<classpath>
<dep pom="my-pom.xml"/>
</classpath>
</javac>
{code}
and
{code}
<javac src=...>
<classpath>
<dep>
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
</classpath>
</javac>
{code}
and
{code}
<dep pathid="my-path">
<dependency pom="my-pom.xml"/>
<dependency name="asm:asm:[3.0,)"/>
</dep>
<javac classpathref="my-path" ... />
{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
[jira] Commented: (MERCURY-65) Implement "old" maven-ant syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158766#action_158766 ]
Oleg Gusakov commented on MERCURY-65:
-------------------------------------
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{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
>
> * 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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158766#action_158766 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/19/08 2:49 PM:
---------------------------------------------------------------
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* even cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
{code}
was (Author: olle):
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* even cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
> 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
>
> * 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
[jira] Updated: (MERCURY-65) Implement "old" maven-ant syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Gusakov updated MERCURY-65:
--------------------------------
Component/s: Ant tasks
> 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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158766#action_158766 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/19/08 2:57 PM:
---------------------------------------------------------------
*In addition to the existing syntax*, I will introduce default local (*~/.m2/repository*) and remote repos (*central or r.s.o ?*), so if nothing is configured - those will be used, plus new syntax:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal #1}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:[3.0,)"/>
</merc:dependencies>
{code}
* cooler proposal
{code:xml|title=cooler proposal # 2}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:[3.0,)"/>
</merc:dependencies>
</classpath>
{code}
* even cooler proposal
{code:xml|title=even cooler proposal #3}
<classpath>
<dependency name="asm:asm-xml:[3.0,)"/>
</classpath>
{code}
I must evaluate which one is doable and most functional for the user
was (Author: olle):
*In addition to the existing syntax*, I will introduce default local (*~/.m2/repository*) and remote repos (*central or r.s.o ?*), so if nothing is configured - those will be used, plus new syntax:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
{code}
* even cooler proposal
{code:xml|title=even cooler proposal}
<classpath>
<dependency name="asm:asm-xml:3.0"/>
</classpath>
{code}
I must evaluate which one is doable and most functional for the user
> 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
>
> * 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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158766#action_158766 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/19/08 2:48 PM:
---------------------------------------------------------------
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* even cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
was (Author: olle):
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{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
>
> * 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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158766#action_158766 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/19/08 2:53 PM:
---------------------------------------------------------------
*In addition to the existing syntax*, I will introduce default local (!/.m2/repository) and remote repos (central or r.s.o ?), so if nothing is configured - those will be used, plus new syntax:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
{code}
* even cooler proposal
{code:xml|title=even cooler proposal}
<classpath>
<dependency name="asm:asm-xml:3.0"/>
</classpath>
{code}
I must evaluate which one is doable and most functional for the user
was (Author: olle):
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
{code}
* even cooler proposal
{code:xml|title=even cooler proposal}
<classpath>
<dependency name="asm:asm-xml:3.0"/>
</classpath>
{code}
I must evaluate which one is doable and most functional for the user
> 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
>
> * 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
[jira] Updated: (MERCURY-65) Implement "old" maven-ant syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Gusakov updated MERCURY-65:
--------------------------------
Description:
* 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
was:
* 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 reading resources from repos
> 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
>
> * 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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158766#action_158766 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/19/08 2:50 PM:
---------------------------------------------------------------
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
{code}
* even cooler proposal
{code:xml|title=even cooler proposal}
<classpath>
<dependency name="asm:asm-xml:3.0"/>
</classpath>
{code}
was (Author: olle):
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* even cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
{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
>
> * 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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158766#action_158766 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/19/08 2:51 PM:
---------------------------------------------------------------
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
{code}
* even cooler proposal
{code:xml|title=even cooler proposal}
<classpath>
<dependency name="asm:asm-xml:3.0"/>
</classpath>
{code}
I must evaluate which one is doable and most functional for the user
was (Author: olle):
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
{code}
* even cooler proposal
{code:xml|title=even cooler proposal}
<classpath>
<dependency name="asm:asm-xml:3.0"/>
</classpath>
{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
>
> * 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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158766#action_158766 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/19/08 2:53 PM:
---------------------------------------------------------------
*In addition to the existing syntax*, I will introduce default local (*~/.m2/repository*) and remote repos (*central or r.s.o ?*), so if nothing is configured - those will be used, plus new syntax:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
{code}
* even cooler proposal
{code:xml|title=even cooler proposal}
<classpath>
<dependency name="asm:asm-xml:3.0"/>
</classpath>
{code}
I must evaluate which one is doable and most functional for the user
was (Author: olle):
*In addition to the existing syntax*, I will introduce default local (!/.m2/repository) and remote repos (central or r.s.o ?), so if nothing is configured - those will be used, plus new syntax:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
* cooler proposal
{code:xml|title=cooler proposal}
<classpath>
<merc:dependencies>
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
</classpath>
{code}
* even cooler proposal
{code:xml|title=even cooler proposal}
<classpath>
<dependency name="asm:asm-xml:3.0"/>
</classpath>
{code}
I must evaluate which one is doable and most functional for the user
> 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
>
> * 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
[jira] Issue Comment Edited: (MERCURY-65) Implement "old" maven-ant
syntax
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158766#action_158766 ]
Oleg Gusakov edited comment on MERCURY-65 at 12/19/08 2:44 PM:
---------------------------------------------------------------
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{code}
was (Author: olle):
*In addition to the existing syntax*, I will introduce:
* stand-alone <localRepository/>, <remoteRepository/>
* a simpler way to add a classpath:
{code:code:xml|title=proposal}
<merc:dependencies refpathid="myclasspath">
<merc:dependency name="asm:asm-xml:3.0"/>
</merc:dependencies>
{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
>
> * 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