Re: maven-release-plugin oddity - no git commit under mvn 3.1.1
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 maven-release-plugin, when doing a release:prepare from my machine using Maven 3.1.1, and maven-release-plugin 2.4.2 I get the following output: [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation git add -- pom.xml [INFO] Working directory: /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation [INFO] Executing: /bin/sh -c cd /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation git status [INFO] Working directory: /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation [INFO] Tagging release with the label com.smxemail.translation-13.2.9... [INFO] Executing: /bin/sh -c cd /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation git tag -F /var/folders/bq/jtxn4t511xz7l_t3t4q4c634gn/T/maven-scm-596385603.commit com.smxemail.translation-13.2.9 [INFO] Working directory: /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation [INFO] Executing: /bin/sh -c cd /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation git ls-files [INFO] Working directory: /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation [INFO] Transforming 'com.smxemail.translation'... [INFO] Not removing release POMs [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation git add -- pom.xml [INFO] Working directory: /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation [INFO] Executing: /bin/sh -c cd /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation git status [INFO] Working directory: /Users/amrk/IdeaProjects/securemx/smx3/com.smxemail.translation [INFO] Release preparation complete. [INFO] [INFO] BUILD SUCCESS You can see here that there are no git commit commands being run, this in turn breaks the build. A coworker who is still using Maven 3.0.4 was able to prepare and release the artefact fine however, so I'm wondering if there's some issue at the SCM layer of maven that's breaking when running under 3.1.1 that isn't an issue when using 3.0.4. Has anyone else seen any behaviour like this? Mark
Re: NAR Maven Plugin 3.0.0 released
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 Dec 7, 2013, at 12:24 AM, Curtis Rueden ctrue...@wisc.edu wrote: Hi all! On behalf of the developers working hard on the NAR plugin for Maven, it is my pleasure to announce that it is available on Maven Central now: http://search.maven.org/#artifactdetails|com.github.maven-nar|nar-maven-plugin|3.0.0|maven-plugin To use it, add this to your pom.xml: plugin groupIdcom.github.maven-nar/groupId artifactIdnar-maven-plugin/artifactId version3.0.0/version /plugin Since October 17th, 2010, the date of the last commit of Mark Donszelmann (the original author of the NAR plugin for Maven who is unfortunately unable to maintain it any longer), a lot of things happened. First of all, the plugin found a new home on GitHub: http://maven-nar.github.io/nar-maven-plugin/ with a team of developers and a mailing list/forum at https://groups.google.com/group/maven-nar a Git repository at https://github.com/maven-nar/nar-maven-plugin a bug tracker at https://github.com/maven-nar/nar-maven-plugin/issues and Frequently Asked Questions at https://github.com/maven-nar/nar-maven-plugin/wiki/Frequently_Asked_Questions Since the Git history does a fine job at listing the fine-grained changes, here is a coarse-grained list of changes: * unified Richard Kerr's, Greg Domjan's and SciJava's forks of the maven-nar-plugin (as it was formerly known) * renamed the plugin to conform with Maven's requirements * moved to a new groupId to reflect that we're on GitHub now * switch to deploy to OSS Sonatype (mirrored on Maven Central) * continuous integration testing thanks to BuildHive * merged the cpptasks-parallel code directly into nar-maven-plugin * support for MacOSX 10.9 * support for Microsoft Visual C++ resource and message compilers * support for Java 7's javah * support developing the Java part of projects using the NAR plugin in Eclipse * robust version detection of Microsoft's linkers * boat loads of bug fixes (as in: megatons of bug fixes) This would not have been possible without the tremendous support and contributions of the community. Thank you all! Ciao, Johannes Schindelin, Curtis Rueden and NAR development team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-release-plugin oddity - no git commit under mvn 3.1.1
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 didn't help as that still picked up the older maven-scm version which was looking for a git status output starting with #. Mark On 9 Dec 2013, at 22:00, Stephen Connolly wrote: 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. signature.asc Description: OpenPGP digital signature
Re: maven-release-plugin oddity - no git commit under mvn 3.1.1
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 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 didn't help as that still picked up the older maven-scm version which was looking for a git status output starting with #. Mark On 9 Dec 2013, at 22:00, Stephen Connolly wrote: 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.
Re: maven-release-plugin oddity - no git commit under mvn 3.1.1
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 resolved the issue. Simply dropping back to 2.3.2 of the release plugin didn't help as that still picked up the older maven-scm version which was looking for a git status output starting with #. Yup correct. I hope we avoid such issue when using jgit provider (if it's released one day) Mark On 9 Dec 2013, at 22:00, Stephen Connolly wrote: 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. AFAIK scm is not bundled with core. -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Upgrade to 3.1.1 causes problems
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 difference in internal synchronization mechanisms that is causing this to bork out on IBM JDK. The appropriate path of action here would probably be to simply compare the two different java.lang.ClassLoader implementations and find the difference. I will try to get around to this fairly quickly; if someone wants to do a side-by side walkthrough (maybe comparing with http://www.docjar.com/html/api/java/lang/ClassLoader.java.html), it should be fairly easy to track. Concurrency/synchronization is the thing to check here. Kristian 2013/12/6 Anders Hammar and...@hammar.net Maybe we should set up a core IT build job with IBM JDK? /Anders On Fri, Dec 6, 2013 at 10:17 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: This is probably because you are using the IBM JDK which might have a slightly different take on the whole concurrent class loading feature. It might be that we need to adjust the toggle that we use to activate concurrent class loading slightly. Do let us know how this turns out; it should be fixable. Kristian 2013/12/5 Collins Solutions collins-soluti...@austin.rr.com I have made the replacement that you have suggested. I have ran through several builds with maven 3.1.1 and have not seen the error come back. I will continue to monitor this. On 12/05/2013 12:17 PM, Stuart McCulloch wrote: You could try replacing: maven-3.1.1/boot/plexus-classworlds-2.5.1.jar with: maven-3.0.5/boot/plexus-classworlds-2.4.jar in case the change to use unsynchronised class loading in classworlds 2.5 when running on Java 1.7 is causing the issue. On 5 Dec 2013, at 16:32, Collins Solutions collins-soluti...@austin.rr. com wrote: It is happening on more than one machine. On 12/04/2013 10:14 PM, Wayne Fay wrote: ...well, it looks as though this is only a temporary solution. After I got everything to build successfully once I cleaned out my repository, I got the same error when I ran the build a second time. I tried upgraded my Maven Is this only happening on one machine, or more than one? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-release-plugin oddity - no git commit under mvn 3.1.1
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 ) m-release-plugin:2.4.2 depends on scm:1.7 SCM-686 introduced the porcelain option. However, suddenly all releases where evaluated/tagged from the root of the repository instead of the root of the project. This broke a lot of projects, more compared to the addition of porcelain, so I decided to fall back to 1.7. SCM-709 is probably fixed by now, but I'm still missing the feedback. I've closed it as part of SCM 1.9, so I'll include it with the next m-release-p. Robert Op Mon, 09 Dec 2013 11:56:21 +0100 schreef Olivier Lamy ol...@apache.org: 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 resolved the issue. Simply dropping back to 2.3.2 of the release plugin didn't help as that still picked up the older maven-scm version which was looking for a git status output starting with #. Yup correct. I hope we avoid such issue when using jgit provider (if it's released one day) Mark On 9 Dec 2013, at 22:00, Stephen Connolly wrote: 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. AFAIK scm is not bundled with core. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Sonar with Maven: Fail to connect to database: Cannot loa d JDBC driver class 'oracle.jdbc.OracleDriver'
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 Sonar user list, then. On Sun, Dec 8, 2013 at 11:55 AM, Omar@Gmail omarnet...@googlemail.com wrote: Thanks David, Yes Sonar on separate server. Also please see http://www.mail-archive.com/users@maven.apache.org/msg132123.html On 8 December 2013 18:31, David Karr davidmichaelk...@gmail.com wrote: I assume that your Sonar server is not the box you're running Maven on? What Sonar properties are you setting in your settings.xml? Feel free to omit the value for each if you need to. In the Sonar installation instructions there is a section titled Adding the JDBC Driver which talks about adding the Oracle JDBC driver to the SONAR installation. Have you done this? On Sat, Dec 7, 2013 at 4:33 AM, Omar@Gmail omarnet...@googlemail.com wrote: Objective: Get Maven to publish sonar results to running Sonar server Steps: - Installed and ran Sonar, accessible from browser - The back-end database is Oracle - Installed and configured Maven in settings.xml file to connect to the Oracle db - Invoked: mvn clean install -DSkipTests=true - Invoke: mvn sonar:sonar But getting following mvn sonar:sonar Fail to connect to database: Cannot load JDBC driver class 'oracle.jdbc.OracleDriver' So I need somehow to put the ojdbc6.jar on Maven classpath. Tried placing the ojdbc6.jar in /lib and lib/ext but did not help. Am I missing something here? please help. To fix this I modified *maven113home/bin/mvn*.bat at line 161 and added %MAVEN_JAVA_EXE% %MAVEN_OPTS% -classpath path/to/ojdbc6.jar;... *Which is nasty!* Please suggest a better approach.
Re: Sonar with Maven: Fail to connect to database: Cannot loa d JDBC driver class 'oracle.jdbc.OracleDriver'
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 for you. Robert [1] http://mojo.codehaus.org/sonar-maven-plugin/xref/index.html Op Mon, 09 Dec 2013 22:46:51 +0100 schreef Omar@Gmail omarnet...@googlemail.com: 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 Sonar user list, then. On Sun, Dec 8, 2013 at 11:55 AM, Omar@Gmail omarnet...@googlemail.com wrote: Thanks David, Yes Sonar on separate server. Also please see http://www.mail-archive.com/users@maven.apache.org/msg132123.html On 8 December 2013 18:31, David Karr davidmichaelk...@gmail.com wrote: I assume that your Sonar server is not the box you're running Maven on? What Sonar properties are you setting in your settings.xml? Feel free to omit the value for each if you need to. In the Sonar installation instructions there is a section titled Adding the JDBC Driver which talks about adding the Oracle JDBC driver to the SONAR installation. Have you done this? On Sat, Dec 7, 2013 at 4:33 AM, Omar@Gmail omarnet...@googlemail.com wrote: Objective: Get Maven to publish sonar results to running Sonar server Steps: - Installed and ran Sonar, accessible from browser - The back-end database is Oracle - Installed and configured Maven in settings.xml file to connect to the Oracle db - Invoked: mvn clean install -DSkipTests=true - Invoke: mvn sonar:sonar But getting following mvn sonar:sonar Fail to connect to database: Cannot load JDBC driver class 'oracle.jdbc.OracleDriver' So I need somehow to put the ojdbc6.jar on Maven classpath. Tried placing the ojdbc6.jar in /lib and lib/ext but did not help. Am I missing something here? please help. To fix this I modified *maven113home/bin/mvn*.bat at line 161 and added %MAVEN_JAVA_EXE% %MAVEN_OPTS% -classpath path/to/ojdbc6.jar;... *Which is nasty!* Please suggest a better approach. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Sonar with Maven: Fail to connect to database: Cannot loa d JDBC driver class 'oracle.jdbc.OracleDriver'
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 rfscho...@apache.org wrote: 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 for you. Robert [1] http://mojo.codehaus.org/sonar-maven-plugin/xref/index.html Op Mon, 09 Dec 2013 22:46:51 +0100 schreef Omar@Gmail omarnet...@googlemail.com: 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 Sonar user list, then. On Sun, Dec 8, 2013 at 11:55 AM, Omar@Gmail omarnet...@googlemail.com wrote: Thanks David, Yes Sonar on separate server. Also please see http://www.mail-archive.com/users@maven.apache.org/msg132123.html On 8 December 2013 18:31, David Karr davidmichaelk...@gmail.com wrote: I assume that your Sonar server is not the box you're running Maven on? What Sonar properties are you setting in your settings.xml? Feel free to omit the value for each if you need to. In the Sonar installation instructions there is a section titled Adding the JDBC Driver which talks about adding the Oracle JDBC driver to the SONAR installation. Have you done this? On Sat, Dec 7, 2013 at 4:33 AM, Omar@Gmail omarnet...@googlemail.com wrote: Objective: Get Maven to publish sonar results to running Sonar server Steps: - Installed and ran Sonar, accessible from browser - The back-end database is Oracle - Installed and configured Maven in settings.xml file to connect to the Oracle db - Invoked: mvn clean install -DSkipTests=true - Invoke: mvn sonar:sonar But getting following mvn sonar:sonar Fail to connect to database: Cannot load JDBC driver class 'oracle.jdbc.OracleDriver' So I need somehow to put the ojdbc6.jar on Maven classpath. Tried placing the ojdbc6.jar in /lib and lib/ext but did not help. Am I missing something here? please help. To fix this I modified *maven113home/bin/mvn*.bat at line 161 and added %MAVEN_JAVA_EXE% %MAVEN_OPTS% -classpath path/to/ojdbc6.jar;... *Which is nasty!* Please suggest a better approach. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to resolve right dependency which enabled and built/install with profile?
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 issue is that how can I get the right dependency in module B for libjar? I want to assemble a fat jar so I need to figure out which version of libjar to include. In my test, it seems to me that when mvn -Pnewlib install module A, though it will build with libjar-2.0. but the installed pom do not reflect this. Thus when module B resolve the dependency, it will resolve the dependency as libjar-1.0 ( though when building module B, -Pnewlib is also passed in, But I think this will not pass to the dependent package when resolve the dependency). I don't want to have module B know anything about the libjar-1.0 and libjar-2.0. it should handle by module A, and module B just simply call into module A. Actually, I think this apply the same if A and B are not modules in one project, but standalone projects. In which case B will not define profile at all. So how can I achieve this goal? say, A take care of lib dependency when build and install. B who depends on A, when assembly can retrive the right lib dependency. Best Regards, Raymond Liu - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
