[
http://jira.codehaus.org/browse/MSITE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115054
]
Dennis Lundberg commented on MSITE-272:
---------------------------------------
Most of the output doesn't really come from the site-plugin itself. If you see
"Velocity v1.4" in there it's not the site-plugin, because starting with
version 2.0-beta-6 the site-plugin uses Velocity 1.5. It's not apparent where
it's coming from, but I'm pretty sure it's the project-info-reports-plugin. A
lot of work has gone into "silencing" the site-plugin for beta-6. The upcoming
2.1 release of project-info-reports-plugin will do the same for that plugin. If
you want to make sure, you can test with the latest 2.1-SNAPSHOT of
maven-project-info-reports-plugin.
> Too much irrelevant information generated at INFOduring execution of Site goal
> ------------------------------------------------------------------------------
>
> Key: MSITE-272
> URL: http://jira.codehaus.org/browse/MSITE-272
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-5, 2.0-beta-6
> Reporter: William Ferguson
>
> Executing 'mvn site:site' generates a lot of noise, much of it internal
> Velocity engine debug which is output at INFO level in the plugin.
> Example (taken from the staging of 2.0-beta-6):
> {code}
> D:\Modules\hubbub-log4j>mvn site
> [INFO] Scanning for projects...
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Building hubbub-log4j
> [INFO] task-segment: [site]
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for
> updates from maven-staging
> [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for
> updates from central
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.pom
> Downloading:
> http://people.apache.org/~dennisl/staging-repository-site-plugin//org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0
> -beta-6.jar
> 118K downloaded
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] **************************************************************
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using VM library template VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find resou
> rce 'VM_global_library.vm'
> [INFO] Velocimacro : VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] **************************************************************
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using VM library template VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find resou
> rce 'VM_global_library.vm'
> [INFO] Velocimacro : VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] Preparing javadoc:javadoc
> [INFO] No goals needed for project - skipping
> -----------------------------------------------------
> this realm = app0.child-container[org.apache.maven.plugins:maven-site-plugin]
> urls[0] = file:/C:/Documents and
> Settings/wferguson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.jar
> urls[1] = file:/C:/Documents and
> Settings/wferguson/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> Number of imports: 4
> import: [EMAIL PROTECTED]
> import: [EMAIL PROTECTED]
> import: [EMAIL PROTECTED]
> import: [EMAIL PROTECTED]
> this realm = plexus.core
> urls[0] = file:/D:/tools/maven/lib/maven-core-2.0.7-uber.jar
> Number of imports: 4
> import: [EMAIL PROTECTED]
> import: [EMAIL PROTECTED]
> import: [EMAIL PROTECTED]
> import: [EMAIL PROTECTED]
> -----------------------------------------------------
> {code}
> The plugin should really only output at a high level which reports it is
> generating.
> This would reduce tension when generating the site (typically during a
> release when tension is already high) and greatly add debugging of bad site
> generation.
> Most of the current output should be logged at DEBUG not INFO
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
