[jira] Commented: (TRINIDAD-2042) Trinidad TagDoc report plugin does not allow mvn site:site target to run
[ https://issues.apache.org/jira/browse/TRINIDAD-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13000972#comment-13000972 ] Scott O'Bryan commented on TRINIDAD-2042: - In addition to my fixes, this does not seem to run with Mvn 2.2.x.. If you run it under MVN 3.0, everything works. I believe this will become part of our overall build strategy. Trinidad TagDoc report plugin does not allow mvn site:site target to run Key: TRINIDAD-2042 URL: https://issues.apache.org/jira/browse/TRINIDAD-2042 Project: MyFaces Trinidad Issue Type: Bug Components: Plugins Reporter: Scott O'Bryan Assignee: Scott O'Bryan When running 'mvn site:site' on main, the following error is thrown: 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.LogFactory.getLog(LogFactory.java:370) at org.apache.commons.digester.Digester.init(Digester.java:304) at org.apache.myfaces.trinidadbuild.plugin.tagdoc.TagdocReport.readIndex(TagdocReport.java:1673) at org.apache.myfaces.trinidadbuild.plugin.tagdoc.TagdocReport.processIndex(TagdocReport.java:1592) at org.apache.myfaces.trinidadbuild.plugin.tagdoc.TagdocReport.executeReport(TagdocReport.java:105) It looks like there is an incompatible logger version or the logger has been declared multiple times in the environment. This must be fixed before the maven site can be generated. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TRINIDAD-2042) Trinidad TagDoc report plugin does not allow mvn site:site target to run
[ https://issues.apache.org/jira/browse/TRINIDAD-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12997924#comment-12997924 ] Scott O'Bryan commented on TRINIDAD-2042: - This was due to some local references to Log4J and commons logging in the tagdoc plugin. If those are removed, everything seems to work fine. I have checked the changes into the 2.0 plugins branch and am working on getting the fix to reference the snapshot checked into trinidad trunk. This will mean that a new version of the plugins will need to be released before the next version of trinidad. Trinidad TagDoc report plugin does not allow mvn site:site target to run Key: TRINIDAD-2042 URL: https://issues.apache.org/jira/browse/TRINIDAD-2042 Project: MyFaces Trinidad Issue Type: Bug Components: Plugins Reporter: Scott O'Bryan Assignee: Scott O'Bryan When running 'mvn site:site' on main, the following error is thrown: 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.LogFactory.getLog(LogFactory.java:370) at org.apache.commons.digester.Digester.init(Digester.java:304) at org.apache.myfaces.trinidadbuild.plugin.tagdoc.TagdocReport.readIndex(TagdocReport.java:1673) at org.apache.myfaces.trinidadbuild.plugin.tagdoc.TagdocReport.processIndex(TagdocReport.java:1592) at org.apache.myfaces.trinidadbuild.plugin.tagdoc.TagdocReport.executeReport(TagdocReport.java:105) It looks like there is an incompatible logger version or the logger has been declared multiple times in the environment. This must be fixed before the maven site can be generated. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
