Hi,
I noticed that my MDEP-300 should be easy to fix, but I would need to
write an IT with a custom packaging type.
That would probably take some time, so I'll pick that up for the 2.7
I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It has a
good patch, although I think that the useBaseVersion should be 'true' by
default. I can fix that today or tomorrow.
thanks,
Robert
Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly
<stephen.alan.conno...@gmail.com>:
We should probably close MDEP-124 as WONT FIX given that there seems no
way
to fix it... or at least the addition of a configuration element to allow
flagging specific dependencies as used even if they seem not.
MDPE-166 also seems like it should just display a different output for
<scope>runtime</scope> namely something like "Unable to determine whether
used or unused as scope is runtime"
I think the above two "solutions" would be quick to implement and would
close the issues out.
On 16 October 2012 14:18, Arnaud HERITIER <aherit...@apache.org> wrote:
Hi all,
i would like to release the dependency plugin soon.
There only too old issues not closed attached to the current version (
http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
)
but I suppose they are migrated release after release without any real
work
on them.
I'm interested especially by this fix to use it as report (
http://jira.codehaus.org/browse/MDEP-366) and it has the perf
improvement
with the plexus-utils upgrade (http://jira.codehaus.org/browse/MDEP-377)
Nobody against it ?
Cheers
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aherit...@gmail.com
Twitter/Skype : aheritier
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
