Hi,
concerning the issues i have a few questions:
I have taken a look into the following Issue:
http://jira.codehaus.org/browse/MNG-1563
Question: Is this really a question about a guide how to write
unit/integration test in Maven ?
Or is it more about unit/integration test in relationship
I think it is about how to do integration testing of projects built with maven.
Since we build maven plugins with maven, one of the sub-problems is
how to integration test maven plugins themselves... hence Brian's wiki
link
An overall guide should cover:
failsafe
separate module for integration
Hi Stephen,
first thanks for your explanations...
I think it is about how to do integration testing of projects built with maven.
Since we build maven plugins with maven, one of the sub-problems is
how to integration test maven plugins themselves... hence Brian's wiki
link
An overall guide
Hi,
Ok..So the first step could be to start with a guide of doing
integration tests with usual Maven modules...(Non Plugin developments).
means using failsafe plugin...
I have started a small guide to cover those things on GitHub.
The source and issue system:
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Olivier Lamy wrote:
As asked by Benson, it's probably better to move MPOM from codehaus
jira to ASF jira.
It might make sense to also delete the MPOM project at Codehaus or
disable at least the submission of new issues.
Benjamin
Sure.
Done see http://jira.codehaus.org/browse/HAUS-2047
2011/1/30 Benjamin Bentmann benjamin.bentm...@udo.edu:
Olivier Lamy wrote:
As asked by Benson, it's probably better to move MPOM from codehaus
jira to ASF jira.
It might make sense to also delete the MPOM project at Codehaus
Hello,
I have changed the subject.
As asked by Benson, it's probably better to move MPOM from codehaus
jira to ASF jira.
So I have created a jira entry :
https://issues.apache.org/jira/browse/INFRA-3397
I'd like maven dev give me or add in the jira entry their id.
Thanks !
--
Olivier Lamy
http
you can add me olivier (aheritier)
On Fri, Jan 28, 2011 at 12:41 PM, Olivier Lamy ol...@apache.org wrote:
Hello,
I have changed the subject.
As asked by Benson, it's probably better to move MPOM from codehaus
jira to ASF jira.
So I have created a jira entry :
https://issues.apache.org
I've added you. We should get a full list of the PMC's apache jira
user id's and then any/all of the three of us can add the PMC to the
project role
2011/1/28 Arnaud Héritier arnaud.herit...@exoplatform.com:
you can add me olivier (aheritier)
On Fri, Jan 28, 2011 at 12:41 PM, Olivier Lamy ol
ok,
It's annoying to not have a mapping between LDAP/SVN groups and Jira.
It could be easier to manage
On Fri, Jan 28, 2011 at 2:53 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I've added you. We should get a full list of the PMC's apache jira
user id's and then any/all
a mapping between LDAP/SVN groups and Jira.
It could be easier to manage
On Fri, Jan 28, 2011 at 2:53 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I've added you. We should get a full list of the PMC's apache jira
user id's and then any/all of the three of us can add the PMC
rgoers
snicoll
stephenc
vmassol
vsiveton
wfay
2011/1/28 Arnaud Héritier arnaud.herit...@exoplatform.com:
ok,
It's annoying to not have a mapping between LDAP/SVN groups and Jira.
It could be easier to manage
On Fri, Jan 28, 2011 at 2:53 PM, Stephen Connolly
stephen.alan.conno
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
I had a look both at the code and examples.
IMHO, the bug was in the way the Jira response was stored to the file using
platform encoding, hence the different result when file.encoding value was set.
r1054373 is a fix for this problem.
I'm not absolutely sure if Jira content was properly
Hi Dennis,
Like Benjamin wrote in the issue, a new parameter should not be necessary
since XML is declaring encoding: you just have tu use
ReaderFactory.newXmlReader() to avoid relying on the parser to detect
encoding.
Such an argument is usefull only if Jira generates wrong XML, with content
comment.
Such an argument is usefull only if Jira generates wrong XML, with content
not
consistent with encoding declared in its prolog: such a case would be a bug
in
Jira.
Unfortunately the RSS-feed files that the plugin downloads from JIRA
doesn't have an XML prolog. They are encoded using
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
On 12/07/2010 06:09 PM, Brian Fox wrote:
We'll take a pass and see which are applicable
That's what I meant; of course some will not be.
flag them in some way.
Such as closing them and refiling in MINDEXER? If someone bothered to report a bug, it seems like the least you can do. (And the
On 07/12/2010, at 3:20 AM, Jesse Glick wrote:
On 12/03/2010 10:09 AM, Brett Porter wrote:
I went ahead and created this. http://jira.codehaus.org/browse/MINDEXER
Consider moving at least the open issues relevant to the donated codebase
from:
We'll take a pass and see which are applicable and flag them in some
way. Moving them all will be a needless pita, imo.
On Tue, Dec 7, 2010 at 1:21 PM, Brett Porter br...@apache.org wrote:
On 07/12/2010, at 3:20 AM, Jesse Glick wrote:
On 12/03/2010 10:09 AM, Brett Porter wrote:
I went ahead
Issue Subscription
Filter: Design Best Practices (24 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
Le lundi 29 novembre 2010, Brett Porter a écrit :
On 29 November 2010 09:56, Herve Boutemy (JIRA) j...@codehaus.org wrote:
[
http://jira.codehaus.org/browse/ARCHETYPE-344?page=com.atlassian.jira.plu
gin.system.issuetabpanels:all-tabpanel]
Herve Boutemy closed ARCHETYPE-344
Hi,
With the release coming up, I realised we'd need a JIRA project beyond that. I
can create it... should it be MINDEXER?
Did anyone have plans to import existing issues, or just start fresh?
Cheers,
Brett
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com
Done (MPOM).
- Brett
On 20/11/2010, at 7:03 AM, Benjamin Bentmann wrote:
Hi,
can some JIRA admin please move the MNG component Apache or Maven Parent
poms
http://jira.codehaus.org/browse/MNG/component/14457
out into a separate JIRA project?
Those POMs, just like any Maven plugin
Hi,
can some JIRA admin please move the MNG component Apache or Maven
Parent poms
http://jira.codehaus.org/browse/MNG/component/14457
out into a separate JIRA project?
Those POMs, just like any Maven plugin out there, have no inherent
relation to the Maven core and its issues, nor do
+1
Arnaud
On Nov 19, 2010, at 9:03 PM, Benjamin Bentmann wrote:
Hi,
can some JIRA admin please move the MNG component Apache or Maven Parent
poms
http://jira.codehaus.org/browse/MNG/component/14457
out into a separate JIRA project?
Those POMs, just like any Maven plugin out
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Brett Porter wrote:
I'd like to suggest we move everything in ( 2.2.2, 2.2.x (to be reviewed), Unscheduled )
last updated before 1 Sep 2010 into Issues to be reviewed for 3.x. [...]
Any objections?
Nope
Benjamin
-
To
Ok, done (I didn't spam the issues list).
So, there are 20 current issues in Unscheduled to review.
On 20/09/2010, at 6:08 AM, Benjamin Bentmann wrote:
Brett Porter wrote:
I'd like to suggest we move everything in ( 2.2.2, 2.2.x (to be reviewed),
Unscheduled ) last updated before 1 Sep
Is it possible for users to set the fix version? If it is can we change that so
users can set no fix version and place it in the to be reviewed bucket.
On Sep 20, 2010, at 9:26 AM, Brett Porter wrote:
Ok, done (I didn't spam the issues list).
So, there are 20 current issues in Unscheduled
On 20/09/2010, at 12:02 PM, Jason van Zyl wrote:
Is it possible for users to set the fix version? If it is can we change that
so users can set no fix version and place it in the to be reviewed bucket.
It's not currently, but we can change it to make it possible. It tended to get
abused more
I think it is better to either: default it to To Be Reviewed; or leave it
unassigned. Giving users the ability to set the Fix version to any
arbitrary version will just make a mockery of our bug scrubs
On 20 September 2010 21:54, Brett Porter br...@apache.org wrote:
On 20/09/2010, at 12:02
Agree too.
2010/9/21 Stephen Connolly stephen.alan.conno...@gmail.com:
I think it is better to either: default it to To Be Reviewed; or leave it
unassigned. Giving users the ability to set the Fix version to any
arbitrary version will just make a mockery of our bug scrubs
On 20 September
Being unassigned is a good way for saying it hasn't been reviewed.
You could, if you wanted, assign it to a Maven Developer once
reviewed.
On Mon, Sep 20, 2010 at 5:40 PM, Olivier Lamy ol...@apache.org wrote:
Agree too.
2010/9/21 Stephen Connolly stephen.alan.conno...@gmail.com:
I think it is
Earlier in the year, we had some agreement to clean house on JIRA before Maven
3, but we ran out of collective steam.
I'm still looking at them from time to time, but losing track of what's new.
I'm still finding some useful stuff in the older ones as well, and occasionally
folks pop back up
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (24 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
Issue Subscription
Filter: Design Best Practices (23 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
On 20/05/2010, Marshall Schor m...@schor.com wrote:
Hi,
I've posted earlier on u...@maven.apache.org about a couple of possible
improvements to the
Apache Common Parent POM - used by Apache projects [1].
I'd like to add some Jira issues for these, but I was unable to determine
what
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Hi,
I've posted earlier on u...@maven.apache.org about a couple of possible
improvements to the
Apache Common Parent POM - used by Apache projects [1].
I'd like to add some Jira issues for these, but I was unable to determine what
Jira system to use; which one should I use?
-Marshall Schor
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (22 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
Issue Subscription
Filter: Design Best Practices (22 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
Issue Subscription
Filter: Design Best Practices (22 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
Issue Subscription
Filter: Design Best Practices (22 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
Should this be in 3.1? Seems like adding a new feature post 3.0?
On 31/03/2010, at 2:28 AM, Jason van Zyl (JIRA) wrote:
[
http://jira.codehaus.org/browse/MNG-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-4568
I consider it orthogonal to the CLI and it's not really a new feature per se
and I don't think folks want to wait until 3.1.
On Mar 30, 2010, at 7:31 PM, Brett Porter wrote:
Should this be in 3.1? Seems like adding a new feature post 3.0?
On 31/03/2010, at 2:28 AM, Jason van Zyl (JIRA
On 31/03/2010, at 10:33 AM, Jason van Zyl wrote:
I consider it orthogonal to the CLI and it's not really a new feature per se
and I don't think folks want to wait until 3.1.
Np, as long as we aren't starting to consider 3.1 as too big a deal for small
new things. We're notoriously bad at
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
You should be posting this to the issue itself, replying to the mail won't be
included.
Maven devs - I've changed the Nabble forum to not allow posting to iss...@.
Hopefully that will help.
- Brett
On 16/02/2010, at 10:02 AM, Briankous wrote:
However, you do not include java code in your
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
Issue Subscription
Filter: Design Best Practices (23 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
701 - 800 of 28876 matches
Mail list logo
