Issue Subscription
Filter: Design & Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
htt
On 21/11/2008, at 12:09 AM, Brian E. Fox wrote:
2. switch several plugins to use mercury for resolution
2.1 dependency plugin
?? .. open for suggestions
I commented in the JIRA, but I think this should only live on a
branch
until Mercury is final. It can be a good way to test Mercury,
Jason van Zyl wrote:
> It's moving to the Sonatype Labs where we will support it.
This is actually great news !!
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
If you want to talk to those folks and they sign CLAs then we can take
that plugin and you can integrate it with the existing one. Go for it.
On 20-Nov-08, at 7:38 AM, Paul Gier wrote:
I'd like to add the feature to attach artifacts generated by the
antrun plugin [MANTRUN-100], and possibl
I'd like to add the feature to attach artifacts generated by the antrun plugin
[MANTRUN-100], and possibly add some of the other features from the maven antrun
extended plugin [1]. Just wanted to check if anyone has input on this. The
extended plugin shows the apache license, so I don't thin
>>
>> 2. switch several plugins to use mercury for resolution
>> 2.1 dependency plugin
>> ?? .. open for suggestions
>I commented in the JIRA, but I think this should only live on a branch
>until Mercury is final. It can be a good way to test Mercury, but
>shouldn't get into a release. We hav
