[
https://jira.codehaus.org/browse/MSONAR-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293944#comment-293944
]
Michael Van Geertruy commented on MSONAR-15:
--------------------------------------------
Olivier suggested I move my builds to mvn 3.x, not 2.2.1 as was stated in the
original ticket.
> sonar-maven-plugin 1.8M1 causes an error: "A required class is missing:
> org/apache/commons/configuration/Configuration"
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: MSONAR-15
> URL: https://jira.codehaus.org/browse/MSONAR-15
> Project: Mojo's Sonar Maven Plugin
> Issue Type: Bug
> Environment: Solaris 10 - 64 bit, RHEL - 64 and 32 bit, java
> 1.6.0_29, Maven 2.2.1
> Reporter: Michael Van Geertruy
> Assignee: Simon Brandhof
>
> Error: On starting the sonar-maven-plugin from maven, I get the
> following message:
> Embedded error: Unable to load the mojo.
> 'org.codehaus.sonar.runtime:sonar-core-maven-plugin:20120220201310:internal'
> in the plugin 'org.codehaus.sonar.runtime:sonar-core-maven-plugin'. A
> required class is missing: org/apache/commons/configuration/Configuration.
> OS: error seen on Linux RH 5.x and Solaris 10
> Java: 1.6.0_29
> Maven: 2.2.1
> Sonar: 2.8
> Sonar-Maven-Plugin: 1.8M1
> Solutions already attempted:
> Removed commons-configuration from both the .m2/repository AND the local
> nexus repository forcing a re-download of that file from repo1.
> Increased the MAVEN_OPTS settings to allow for more memory usage.
> Increased ulimit -n to 1024 (the max).
> Verified the location of JAVA_HOME.
> Verified that mvn -version returned the expected information.
> Because I have duplicated this issue on more than one os, and on
> multiple architectures, I believe this is a bug, or an issue with
> the setup. Olivier suggested I move my builds to Maven 2.2.1, but
> that is not a possibility because of incompatable build issues
> we've experienced. I've attempted to get the source-code for that
> tag, and I can't find it.
> This issue should be fixed because when folks attempt to resolve
> issues of technical debt, moving to the latest and greatest version
> of Maven in order to use this plugin is unrealistic. Instead, this
> bug needs to be fixed either as a documentation issue, or as a code
> improvement where a more descriptive message is reported.
> The 1.8M1 version appears to be the last that was done for maven 2.x.
> If this codebase is made available, I would be happy to maintain and
> improve it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
