I'd appreciate spinning a release of this. When staged I can test on
my real corporate use cases. Should be very similar to my test on the
snapshot though, so I don't expect any issues.
/Anders
On Wed, May 2, 2012 at 2:17 PM, Anders Hammar and...@hammar.net wrote:
It's not that easy. The
Thanks for the polished ping :-)
I will take care of that this week.
2012/5/21 Anders Hammar and...@hammar.net:
I'd appreciate spinning a release of this. When staged I can test on
my real corporate use cases. Should be very similar to my test on the
snapshot though, so I don't expect any
If no settings specified, the maven invocation will use the default
one (~/.m2/settings.xml)
Actually it will use the settings of the calling process, which could
be something different than the default file-based one.
Due to corporate infrastructure reasons I couldn't test one of my
actual
Hi,
AFAIK no rush :-)
So take the time to test your various use cases.
2012/5/2 Anders Hammar and...@hammar.net:
If no settings specified, the maven invocation will use the default
one (~/.m2/settings.xml)
Actually it will use the settings of the calling process, which could
be something
It's not that easy. The corporate infrastructure only proxies central,
not any snapshot repos. So I can't test a Snapshot version.
So what I've done is verifying that the plugin now works with the new
embedded Maven 3 feature of Hudson. Really my main goal and should be
what I need for the
2012/4/29 Anders Hammar and...@hammar.net:
Yes, I will. Will not happen until Wednesday though. (Holidays here in
Sweden.)
Regarding the flag, inheriting setitngs.xml by default from the
invoking process if no settings.xml is specified in the flugin config
is not implemented? I'm asking
Yes, I will. Will not happen until Wednesday though. (Holidays here in Sweden.)
Regarding the flag, inheriting setitngs.xml by default from the
invoking process if no settings.xml is specified in the flugin config
is not implemented? I'm asking based on mine and Stephen's discussion.
/Anders
On
The buildjob is used to store the results of the invoked runs.
That page describes the schema.
Iirc I was to write a Jenkins plugin to parse them so that you could track
the invoked tests in the trend graph... But I do get pulled every which way
and it can take a while before I return to these
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 (settingsFile ).
What I can do is made this merge feature optional (off by default and
add a debug flag to
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
So vote cancelled again :-).
I will make this merge optional (off by default).
2012/4/26 Stephen Connolly stephen.alan.conno...@gmail.com:
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
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
On 26 April 2012 12:01, Anders Hammar and...@hammar.net 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
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 this
On 26 April 2012 13:40, Anders Hammar and...@hammar.net 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
On 26 April 2012 13:57, Stephen Connolly stephen.alan.conno...@gmail.comwrote:
On 26 April 2012 13:40, Anders Hammar and...@hammar.net 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
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 stephen.alan.conno...@gmail.com:
On 26 April 2012 13:57, Stephen Connolly
Op Thu, 26 Apr 2012 14:57:14 +0200 schreef Stephen Connolly
stephen.alan.conno...@gmail.com:
On 26 April 2012 13:40, Anders Hammar and...@hammar.net 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
On 26 April 2012 23:13, Robert Scholte apa...@sourcegrounds.com wrote:
Op Thu, 26 Apr 2012 14:57:14 +0200 schreef Stephen Connolly
stephen.alan.connolly@gmail.**com stephen.alan.conno...@gmail.com:
On 26 April 2012 13:40, Anders Hammar and...@hammar.net wrote:
I would argue that those
On 26 April 2012 23:18, Stephen Connolly stephen.alan.conno...@gmail.comwrote:
On 26 April 2012 23:13, Robert Scholte apa...@sourcegrounds.com wrote:
Op Thu, 26 Apr 2012 14:57:14 +0200 schreef Stephen Connolly
stephen.alan.connolly@gmail.**com stephen.alan.conno...@gmail.com:
On 26
Hi,
I'd like to release Apache Maven Invoker plugin 1.6.
We fixed 14 issues ( release notes: http://s.apache.org/MINVOKER-1.6 )
Staging repository:
https://repository.apache.org/content/repositories/maven-097/
Staging site: http://maven.apache.org/plugins/maven-invoker-plugin-1.6/
(wait sync)
+1 (non-binding)
/Anders
On Wed, Apr 25, 2012 at 10:53, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release Apache Maven Invoker plugin 1.6.
We fixed 14 issues ( release notes: http://s.apache.org/MINVOKER-1.6 )
Staging repository:
Hi,
-1 (non binding) based on my reported problems...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen
Hi,
i have a question concerning the parameters which given to instances of
the invoker-plugin on command during execution of the integration test:
Based on the files i've taken a look into it looks like there is a
profile activated or added on default so far as i understand this is
based
Hi,
just an other question came to my mind
What is the purpose of the
http://maven.apache.org/plugins/maven-invoker-plugin-1.6/build-job.html
It's given as a link in the docs? But i can't find an explanation which
intention it has ? May be i oversight it simply ?
Can someone enlighten me?
25 matches
Mail list logo
