I haven't found the best answer for that. Yes: it would be best to update the mojo-site and the plugin-site at once
No: the plugin is *only* staged, not yet released. It's not yet available at maven-central. This would make things confusing. - Robert From: [email protected] Date: Thu, 9 Sep 2010 16:26:55 +0200 To: [email protected] Subject: Re: [mojo-dev] [VOTE] Sonar maven plugin 1.0-beta-2 Something is missing in documentation : when the mojo version should be updated in mojo site ? I suppose before staging the release. On Thu, Sep 9, 2010 at 4:12 PM, Simon Brandhof <[email protected]> wrote: Cool ! But it fails during release:perform with maven 2.2.1 : [INFO] [site:deploy {execution: default-deploy}] WAGON_VERSION: 1.0-beta-2 https://dav.codehaus.org/mojo/sonar-maven-plugin - Session: Disconnecting https://dav.codehaus.org/mojo/sonar-maven-plugin - Session: Disconnected [FATAL ERROR] org.apache.maven.plugins.site.SiteDeployMojo#execute() caused a linkage error (java.lang.ExceptionInInitializerError) and may be out-of-date. Check the realms: [FATAL ERROR] Plugin realm = app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1.1] urls[0] = file:/Users/simonbrandhof/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1.1/maven-site-plugin-2.1.1.jar urls[1] = file:/Users/simonbrandhof/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar urls[2] = file:/Users/simonbrandhof/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.3/doxia-module-xhtml-1.1.3.jar urls[3] = file:/Users/simonbrandhof/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.3/doxia-core-1.1.3.jar urls[4] = file:/Users/simonbrandhof/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar urls[5] = file:/Users/simonbrandhof/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar urls[6] = file:/Users/simonbrandhof/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar urls[7] = file:/Users/simonbrandhof/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar urls[8] = file:/Users/simonbrandhof/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar urls[9] = file:/Users/simonbrandhof/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar urls[10] = file:/Users/simonbrandhof/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.3/doxia-module-apt-1.1.3.jar urls[11] = file:/Users/simonbrandhof/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.3/doxia-module-xdoc-1.1.3.jar urls[12] = file:/Users/simonbrandhof/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.3/doxia-module-fml-1.1.3.jar urls[13] = file:/Users/simonbrandhof/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.3/doxia-decoration-model-1.1.3.jar urls[14] = file:/Users/simonbrandhof/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.3/doxia-site-renderer-1.1.3.jar urls[15] = file:/Users/simonbrandhof/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar urls[16] = file:/Users/simonbrandhof/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar urls[17] = file:/Users/simonbrandhof/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar urls[18] = file:/Users/simonbrandhof/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar urls[19] = file:/Users/simonbrandhof/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar urls[20] = file:/Users/simonbrandhof/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.2.1/maven-doxia-tools-1.2.1.jar urls[21] = file:/Users/simonbrandhof/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar urls[22] = file:/Users/simonbrandhof/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar urls[23] = file:/Users/simonbrandhof/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar urls[24] = file:/Users/simonbrandhof/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar urls[25] = file:/Users/simonbrandhof/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar [FATAL ERROR] Container realm = plexus.core urls[0] = file:/Users/simonbrandhof/software/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] null Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.ExceptionInInitializerError at org.apache.webdav.lib.WebdavSession.getSessionInstance(WebdavSession.java:145) at org.apache.webdav.lib.WebdavSession.getSessionInstance(WebdavSession.java:127) at org.apache.webdav.lib.WebdavResource.setClient(WebdavResource.java:1273) at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1298) at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1320) at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1408) at org.apache.webdav.lib.WebdavResource.<init>(WebdavResource.java:290) at org.apache.maven.wagon.providers.webdav.CorrectedWebdavResource.<init>(CorrectedWebdavResource.java:54) at org.apache.maven.wagon.providers.webdav.WebDavWagon.openConnection(WebDavWagon.java:143) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:207) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:142) at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:212) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.)) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.apache.commons.httpclient.HttpClient.<clinit>(HttpClient.java:69) ... 31 more Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) ... 35 more Caused by: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385) ... 36 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2 minutes 27 seconds [INFO] Finished at: Thu Sep 09 16:10:23 CEST 2010 [INFO] Final Memory: 146M/332M [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Maven execution failed, exit code: '1' Any ideas ? On Thu, Sep 9, 2010 at 3:58 PM, Robert Scholte <[email protected]> wrote: Absolutely. I've already succeeded with the two parent pom's, yours would be the first jar (isn't it exciting ;) ) I already noticed you followed the instructions. I hope everything is clear enough, otherwise let me know. cheers, - Robert From: [email protected] Date: Thu, 9 Sep 2010 15:53:24 +0200 To: [email protected] Subject: Re: [mojo-dev] [VOTE] Sonar maven plugin 1.0-beta-2 Robert, sonar mojo is now upgraded to mojo-parent 25. I would like to be sure that codehaus staging repositories are ready to be used now. Can I stage the release before restarting the vote ? Thank you On Mon, Aug 30, 2010 at 10:43 PM, Robert Scholte <[email protected]> wrote: The voting for the nexus/new parent should be in a separate thread as well. Right now the voting for the sonar-m-p is a bit spoiled... - Robert From: [email protected] Date: Mon, 30 Aug 2010 21:58:11 +0200 To: [email protected] Subject: Re: [mojo-dev] [VOTE] Sonar maven plugin 1.0-beta-2 ok, +1 too. You should maybe send a new email outside this thread. The "right person" you're looking for is maybe not interested in sonar ;-) On Mon, Aug 30, 2010 at 8:03 PM, Julien Ponge <[email protected]> wrote: Same as Evgeny: +1 on all items. Cheers On Mon, Aug 30, 2010 at 6:49 PM, Evgeny Mandrikov <[email protected]> wrote: > Hi guys, > +1 for using nexus (staging and deploying) and for release mojo parent. > > On Mon, Aug 30, 2010 at 20:34, Robert Scholte <[email protected]> wrote: >> >> Hi Simon, >> >> Last week I've asked Juven Xu to prepare the nexus repository of codehaus >> for staging and deploying the mojo projects[1] >> He has finished his part, so now it's up to us to finalize our part[2] >> So before you can deploy the sonar-m-p, I think we have to update the >> mojo-parent[3], which requires a vote as well. >> I'd hoped one of the despots or someone with staging experience could pick >> up MOJO-1553. We just have to make sure everyone is informed correctly, not >> just by some wild guesses from me because the docs say so. >> This shouldn't be a problem, it's just about finding the right person who >> wants to do this. >> >> - Robert >> >> [1] http://jira.codehaus.org/browse/HAUS-2000 >> [2] http://jira.codehaus.org/browse/MOJO-1553 >> [3] >> http://docs.codehaus.org/display/HAUSMATES/Codehaus+Maven+Repository+Usage+Guide#CodehausMavenRepositoryUsageGuide-6.POMandsettingsconfig >> >> >> ________________________________ >> From: [email protected] >> Date: Mon, 30 Aug 2010 17:03:46 +0200 >> To: [email protected] >> Subject: [mojo-dev] [VOTE] Sonar maven plugin 1.0-beta-2 >> >> Hi everyone, >> This new version makes sonar configuration easier when using a maven proxy >> like Nexus or Archiva. Indeed no additional settings are required anymore ! >> Let's remind that the current version 1.0-beta-1 needs to declare a mirror >> in maven settings (see the section "declare the maven internal repository >> into Nexus"). >> This improvement requires Sonar 2.2+. It is automatically disabled when >> using sonar 2.1 or less. The snapshot has been deployed. >> Release notes: >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11062&version=16625 >> The vote is open for 72 hours with a lazy consensus as usual. >> Thanks >> >> Simon Brandhof >> SonarSource.org >> SonarSource.com >> --- > > > > -- > Best regards, > Evgeny Mandrikov aka Godin <http://godin.net.ru> > http://twitter.com/_godin_ > -- http://izpack.org/ http://jpz-log.info/ http://julien.ponge.info/ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
