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
On 26 April 2012 23:18, Stephen Connolly wrote:
>
>
> On 26 April 2012 23:13, Robert Scholte wrote:
>
>> Op Thu, 26 Apr 2012 14:57:14 +0200 schreef Stephen Connolly <
>> stephen.alan.connolly@gmail.**com >:
>>
>>
>> On 26 April 2012 13:40, Anders Hammar wrote:
>>>
>>> > I would argue that thos
On 26 April 2012 23:13, Robert Scholte wrote:
> Op Thu, 26 Apr 2012 14:57:14 +0200 schreef Stephen Connolly <
> stephen.alan.connolly@gmail.**com >:
>
>
> On 26 April 2012 13:40, Anders Hammar wrote:
>>
>> > I would argue that those are broken projects. You should pretty much
>>> always
>>> >
Op Thu, 26 Apr 2012 14:57:14 +0200 schreef Stephen Connolly
:
On 26 April 2012 13:40, Anders Hammar wrote:
> I would argue that those are broken projects. You should pretty much
always
> use mrm if you are using invoker for testing a maven plugin. There are
> cases where you might use invok
Hi,
The vote has passed with the following result :
+1 (binding): Hervé Boutemy, Olivier Lamy, Vincent Siveton, Dennis Lundberg
+1 (non binding): Lukas Theussl
I will promote the artifacts to the central repo.
Thanks to all voters!
On 2012-04-23 22:30, Dennis Lundberg wrote:
> Hi,
>
> We solve
+1 from me
On 2012-04-23 22:30, Dennis Lundberg wrote:
> Hi,
>
> We solved 9 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146&styleName=Html&version=17454
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=tr
Hi,
I'd like to release Apache Maven SCM 1.7.
We fixed 18 issues ( http://s.apache.org/SCM-1.7 )
One new feature is the support of Jazz Scm (thanks to Chris Graham !)
The staging repository is available here:
https://repository.apache.org/content/repositories/maven-112/
The staging site: http://
ok in order to try make all happy :-) I will make that configurable.
@Anders I have pushed a snapshot with a new flag called
mergeUserSettings. Can you try with your use case ?
2012/4/26 Stephen Connolly :
> On 26 April 2012 13:57, Stephen Connolly
> wrote:
>
>> On 26 April 2012 13:40, Anders Ham
On 26 April 2012 13:57, Stephen Connolly wrote:
> On 26 April 2012 13:40, Anders Hammar wrote:
>
>> > I would argue that those are broken projects. You should pretty much
>> always
>> > use mrm if you are using invoker for testing a maven plugin. There are
>> > cases where you might use invoker f
On 26 April 2012 13:40, Anders Hammar wrote:
> > I would argue that those are broken projects. You should pretty much
> always
> > use mrm if you are using invoker for testing a maven plugin. There are
> > cases where you might use invoker for something else, in which case you
> > should not be s
> I would argue that those are broken projects. You should pretty much always
> use mrm if you are using invoker for testing a maven plugin. There are
> cases where you might use invoker for something else, in which case you
> should not be specifying a custom settings.xml.
I might be wrong, but t
On 26 April 2012 12:01, Anders Hammar wrote:
> The problem I have with using the mrm-maven-plugin is that it would
> then require the pom to be updated.
>
> Here's a scenario:
> In an environment with no direct access to central but an internal MRM
> is used, which is configured in settings.xml.
The problem I have with using the mrm-maven-plugin is that it would
then require the pom to be updated.
Here's a scenario:
In an environment with no direct access to central but an internal MRM
is used, which is configured in settings.xml. I download some open
source project that uses the m-invoke
So vote cancelled again :-).
I will make this merge optional (off by default).
2012/4/26 Stephen Connolly :
> I actually think the merge feature is a step backwards and I am toying with
> being -1 on the commit.
>
> for proxies I think mrm-maven-plugin @ mojo is the way to go.
>
> invoker is a dif
I actually think the merge feature is a step backwards and I am toying with
being -1 on the commit.
for proxies I think mrm-maven-plugin @ mojo is the way to go.
invoker is a different use case from release, so passing through the
settings is, in general, a bad thing. If you make the merge an opt
Good catch on the warning for activated profiles.
They are activated in the maven build so the invoker plugin merge
those setting with those eventually defined in the mojo configuration
field ( ).
What I can do is made this merge feature optional (off by default and
add a debug flag to display it f
16 matches
Mail list logo
