There is a know issue with Git and release plugin 2.4.2 and something to do
with SCM version bundled in Maven 3.1.1? (or maybe 3.1.x) Olivier may know
more.
On 9 December 2013 02:40, Mark Derricutt m...@talios.com wrote:
Hey all,
Just encountered a strange issue with the
Hi
thank you for seeing this through. I am glad that the plugin I originally made
for Maven 1,
and later for Maven 2 is in good hands. I am sure that if I ever need it again,
I will come
back to it and possibly re-contribute to it.
For now, good luck with it.
Regards
Mark Donszelmann
On
I was speaking with Olivier on IRC earlier, so far I've managed to work around
the issue by adding a dependency/ on the latest maven-scm-providers-gitexe
inside my maven-release-plugin plugin/ block and that seems to have resolved
the issue.
Simply dropping back to 2.3.2 of the release plugin
yeah your subsequent reply where you identified the change in git behaviour
would lead to that solution...
On 9 December 2013 09:48, Mark Derricutt m...@talios.com wrote:
I was speaking with Olivier on IRC earlier, so far I've managed to work
around the issue by adding a dependency/ on the
On 9 December 2013 20:48, Mark Derricutt m...@talios.com wrote:
I was speaking with Olivier on IRC earlier, so far I've managed to work
around the issue by adding a dependency/ on the latest
maven-scm-providers-gitexe inside my maven-release-plugin plugin/ block and
that seems to have
I answered to their 5 page questionaire and did not read their 200 page
license agreement, which all allowed me download their JDK (This probably
means IBM now own any further kids I may choose to have...)
The IBM jdk does appear to support concurrent classloading. There is
probably some subtle
Hi,
Here's a list of the maven-release-plugin and the matching SCM versions.
m-release-plugin:2.3.2 depends on scm:1.7
m-release-plugin:2.4 depends on scm:1.8 (standard upgrade, incl. SCM-686)
m-release-plugin:2.4.1 depends on scm:1.7 (back due to MRELEASE-830,
SCM-709 )
Thanks David,
The problem is Maven side as I have clearly explained so not not sure why
I should pursue this on Sonar user list.
Explain to me why you still think it is a Sonar issue.
On 9 December 2013 00:44, David Karr davidmichaelk...@gmail.com wrote:
I suggest you pursue this on the
I agree with David. The Sonar team should be able to help you.
I had a small look at the code of the *plugin*[1], and it doesn't contain
any references to JDBC drivers.
Sonar probably has a trick, which reuses the Maven classpath.
Anyhow, they know the trick, so they should know the solution
OK I see, so we are throwing it over the fence :)
Sonar has very nice solution for it's side which is a folder under lib to
hold jdbc drivers, shame Maven doesn't. Seems I have to stick with hacking
the mvn script file. Thanks guys this is done with.
On 9 December 2013 22:06, Robert Scholte
Hi
I have a project with module A that will be built with or without profile say
-Pnewlib , thus I can have it build with different version of library
dependency let's say by default use libjar-1.0 and when -Pnewlib will use
libjar-2.0.
Then, I have a module B to depends on module A. The
11 matches
Mail list logo
