On Sun, Sep 1, 2013 at 8:21 PM, Hervé BOUTEMY wrote:
> if I read Jazz SCM url format [1], in a multi-module build, scm info
> automatically calculated from root to modules (ie appending artifact-id)
> will
> give wrong scm info, no?
> did you try it?
>
>
All of my testing was for multi module pro
if I read Jazz SCM url format [1], in a multi-module build, scm info
automatically calculated from root to modules (ie appending artifact-id) will
give wrong scm info, no?
did you try it?
there are 2 other parts:
- m-release-p: did you add any logic to deal with plugin scm info modification
whe
no, it's not a wrokaround, it's a real Maven bug that was ignored for a long
time because it didn't cause any failure (wrong user-agent with Maven <=
3.0.3, no user-agent with Maven > 3.0.3)
and only today, with central causing access denied when no user-agent is set,
we find the more global bug
I'll work on a fix for the EclipsePluginIT, so you can specify the Maven
version range.
Robert
Op Sun, 01 Sep 2013 08:44:27 +0200 schreef Kristian Rosenvold
:
Great stuff. I looked around a bit and there does not seem to be a
workaround (like a System property that can be set)...
Kristia
