[jira] Michael Osipov mentioned you (JIRA)

2016-04-16 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov mentioned you on MPOM-40 --- [~mavendevlist], unfortunately JSR 305 has virtually been ceased and Google's reference

[jira] Michael Osipov mentioned you (JIRA)

2015-12-07 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov mentioned you on MCHECKSTYLE-314 --- This is merely {{@Execute( goal = "check

[jira] [Commented] (MNG-5878) Subversion SCM module URLs incorrectly build when module name != artifactId

2015-08-26 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715455#comment-14715455 ] Hervé Boutemy commented on MNG-5878: feature added in branch [812e1e9d|http://git-wip

[jira] [Commented] (MNG-5878) Subversion SCM module URLs incorrectly build when module name != artifactId

2015-08-26 Thread Jason van Zyl (JIRA)
[ https://issues.apache.org/jira/browse/MNG-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715970#comment-14715970 ] Jason van Zyl commented on MNG-5878: Seems perfectly reasonable. Subversion SCM module

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-15 Thread Stephen Connolly (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698136#comment-14698136 ] Stephen Connolly commented on MPIR-234: --- Say you are looking at a projects site. You

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-14 Thread Stephen Connolly (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696991#comment-14696991 ] Stephen Connolly commented on MPIR-234: --- It should not be displayed, or inferred from

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-14 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697645#comment-14697645 ] Robert Scholte commented on MPIR-234: - I really wonder if we should call it a URL. IMHO

[jira] [Comment Edited] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-14 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697360#comment-14697360 ] Hervé Boutemy edited comment on MPIR-234 at 8/14/15 4:53 PM: - bq

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-14 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697360#comment-14697360 ] Hervé Boutemy commented on MPIR-234: bq. NIT: those checkout instructions do

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-14 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697836#comment-14697836 ] Hervé Boutemy commented on MPIR-234: yes SCM urls can be really complex core needs

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-14 Thread Benson Margulies (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697908#comment-14697908 ] Benson Margulies commented on MPIR-234: --- I am going to put in a fruitless reminder

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-14 Thread Chris Graham (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698032#comment-14698032 ] Chris Graham commented on MPIR-234: --- +1 Making the URL's longer just increases

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-14 Thread Chris Graham (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698029#comment-14698029 ] Chris Graham commented on MPIR-234: --- It should not be displayed, or inferred from any

[jira] [Comment Edited] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-14 Thread Chris Graham (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698029#comment-14698029 ] Chris Graham edited comment on MPIR-234 at 8/15/15 2:16 AM

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-13 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694875#comment-14694875 ] Hervé Boutemy commented on MPIR-234: notice that this is what I already did in MPIR-290

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-13 Thread Chris Graham (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696261#comment-14696261 ] Chris Graham commented on MPIR-234: --- it's a general contract that should be enforcer

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-13 Thread Chris Graham (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696247#comment-14696247 ] Chris Graham commented on MPIR-234: --- I see a general drift towards a Git centric

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-13 Thread Chris Graham (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696274#comment-14696274 ] Chris Graham commented on MPIR-234: --- So the question becomes what do we put on the Source

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-12 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694289#comment-14694289 ] Hervé Boutemy commented on MPIR-234: finally removing scm info from effective model

[jira] [Issue Comment Deleted] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-12 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPIR-234: --- Comment: was deleted (was: finally removing scm info from effective model is IMHO throwing baby

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-12 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694288#comment-14694288 ] Hervé Boutemy commented on MPIR-234: finally removing scm info from effective model

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-12 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694267#comment-14694267 ] Hervé Boutemy commented on MPIR-234: bq. So the question becomes what do we put

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-12 Thread Stephen Connolly (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693414#comment-14693414 ] Stephen Connolly commented on MPIR-234: --- [~hboutemy] So my point is that the scm: URLs

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-12 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693980#comment-14693980 ] Robert Scholte commented on MPIR-234: - I created MNG-5870 for adjustments on core

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-11 Thread Stephen Connolly (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681565#comment-14681565 ] Stephen Connolly commented on MPIR-234: --- Perhaps {{scmParent}} would be better than

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-11 Thread Stephen Connolly (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681545#comment-14681545 ] Stephen Connolly commented on MPIR-234: --- Well in general I see the SCM section being

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-11 Thread Stephen Connolly (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681564#comment-14681564 ] Stephen Connolly commented on MPIR-234: --- Argh! hit Add too soon I wonder should we

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-11 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681370#comment-14681370 ] Hervé Boutemy commented on MPIR-234: we need more generic discussion, not only git

[jira] [Comment Edited] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-11 Thread Stephen Connolly (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681545#comment-14681545 ] Stephen Connolly edited comment on MPIR-234 at 8/11/15 9:49 AM

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-11 Thread Mirko Friedenhagen (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681589#comment-14681589 ] Mirko Friedenhagen commented on MPIR-234: - In regards to [~hboutemy] comment

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-11 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682341#comment-14682341 ] Robert Scholte commented on MPIR-234: - The more I think about it, the more I like

[jira] [Comment Edited] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-11 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682341#comment-14682341 ] Robert Scholte edited comment on MPIR-234 at 8/11/15 7:31 PM

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-11 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14692588#comment-14692588 ] Hervé Boutemy commented on MPIR-234: I don't understand the idea of scm configuration

[jira] [Comment Edited] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-11 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14692588#comment-14692588 ] Hervé Boutemy edited comment on MPIR-234 at 8/12/15 12:07 AM

[jira] [Comment Edited] (MPIR-312) Subversion SCM module URLs incorrectly build when module name != artifactId

2015-08-09 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679111#comment-14679111 ] Hervé Boutemy edited comment on MPIR-312 at 8/9/15 11:53 AM

[jira] [Comment Edited] (MPIR-312) Subversion SCM module URLs incorrectly build when module name != artifactId

2015-08-09 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679111#comment-14679111 ] Hervé Boutemy edited comment on MPIR-312 at 8/9/15 11:54 AM

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-09 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679106#comment-14679106 ] Hervé Boutemy commented on MPIR-234: I'm thinking at this for a long time now, here

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-09 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679242#comment-14679242 ] Robert Scholte commented on MPIR-234: - We need to keep in mind that there's a difference

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-09 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679189#comment-14679189 ] Hervé Boutemy commented on MPIR-234: I'm not a gitweb expert: I don't know if it can

[jira] [Comment Edited] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-09 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679150#comment-14679150 ] Michael Osipov edited comment on MPIR-234 at 8/9/15 1:48 PM

[jira] [Comment Edited] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-09 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679150#comment-14679150 ] Michael Osipov edited comment on MPIR-234 at 8/9/15 1:48 PM

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-09 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679150#comment-14679150 ] Michael Osipov commented on MPIR-234: - Would that actually work with Gitweb? Look how

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-09 Thread JIRA
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679270#comment-14679270 ] Hervé Boutemy commented on MPIR-234: yes, url is a different story from connection

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

2015-08-09 Thread Chris Graham (JIRA)
[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679583#comment-14679583 ] Chris Graham commented on MPIR-234: --- Just too add some more fuel to the fire. :) Jazz

[jira] James Wennmacher mentioned you (JIRA)

2015-05-20 Thread James Wennmacher (JIRA)
[ https://issues.apache.org/jira/browse/MANTTASKS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Wennmacher mentioned you on MANTTASKS-246 --- [~mavendevlist] could probably direct you how to submit a fix

[jira] Subscription: Design Best Practices

2012-05-17 Thread jira
Issue Subscription Filter: Design Best Practices (25 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-05-10 Thread jira
Issue Subscription Filter: Design Best Practices (25 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-05-03 Thread jira
Issue Subscription Filter: Design Best Practices (25 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-04-26 Thread jira
Issue Subscription Filter: Design Best Practices (25 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-04-19 Thread jira
Issue Subscription Filter: Design Best Practices (25 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-04-12 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-04-05 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-03-29 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-03-22 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-03-15 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-03-08 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-03-01 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-02-23 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-02-16 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-02-09 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-02-02 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-01-26 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-01-19 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-01-12 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2012-01-05 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-12-29 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-12-22 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-12-15 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-12-08 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-12-01 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-11-24 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-11-17 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-11-10 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-11-03 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-10-27 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-10-20 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-10-20 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-10-13 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-10-06 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-09-29 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-09-22 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-09-15 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-09-08 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-09-01 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-08-25 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-08-18 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-08-11 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-08-04 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-07-28 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-07-21 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-07-14 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-07-07 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-06-30 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-06-23 Thread jira
Issue Subscription Filter: Design Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

[jira] Subscription: Design Best Practices

2011-06-16 Thread jira
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

[jira] Subscription: Design Best Practices

2011-06-09 Thread jira
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

[jira] Subscription: Design Best Practices

2011-06-02 Thread jira
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

[jira] Subscription: Design Best Practices

2011-05-26 Thread jira
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

[jira] Subscription: Design Best Practices

2011-05-19 Thread jira
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

[jira] Subscription: Design Best Practices

2011-05-12 Thread jira
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

  1   2   3   4   5   6   7   8   9   10   >