> too error prone as you have to keep the plugin configuration and the
> dependency list in sync. It doesn't sound like a hard task first, but
What about only configure the dependency list with additional field as
plugin configuration such as:
foo
bar
x.y.z
1
-Guo
-
> This is covered in the Maven 3.x compatibility notes:
> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-DependencyResolution
Thanks Wayne for the precise answer! I did read the page few times :(
Just share my test which given 2.x style result with mav
dependency:tree and dependency:list give me different result set on
one of complex project:
* one lib more in dependency:list
* one lib version different compare to dependency:tree
I have plugin which rely on mavenProject.getRuntimeArtifacts() which
return same as dependency:list exclude test scop
> Legacy Maven 2.x API
Thanks Benjamin!
- Guo
On 19 Dec 2010 18:43, "Benjamin Bentmann" wrote:
> Guo Du wrote:
>
>> Is there any logic behind this or those two will be merged some day?
>
> Same concept for diff
Hi list,
I am looking at the repository implementation for artifact and plugins
in maven 3.0.1, both have nearly identical fields, the difference is
the package name. Test code and result at the end of the message.
Is there any logic behind this or those two will be merged some day?
Thanks!
-Gu
On Sun, Dec 12, 2010 at 12:37 PM, Baptiste MATHUS wrote:
> If you think this is a required feature, please file an issue in the
> corresponding JIRA (http://jira.codehaus.org/browse/MPH).
> This is typically how feature request have to go through.
Ticket created with patch against trunk:
http://ji
maven-help-plugin:2.1.1:describe with maven 3.0.1 doesn't show the
parameter Required and Expression status which is essential to run the
goal.
I would like those information included in the help:describe goal.
What do you think?
-Guo
EXAMPLE [ eclipse:configure-workspace ]
===
