[jira] Commented: (MNG-1857) PluginManagement config is not used by plugins enabled in the site generation phase
[ http://jira.codehaus.org/browse/MNG-1857?page=comments#action_53701 ]
Indrajit Raychaudhuri commented on MNG-1857:
Is there a way to make site reporting honor plugin config in build/?
We can have a reportingManagement/ element to config reporting as such.
But then we would land up in a situation where certain configurations have to
be repeated in pluginManagement/ as well as reportingManagement/.
The solution would serve the purpose but won't be as elegent :)
PluginManagement config is not used by plugins enabled in the site generation
phase
---
Key: MNG-1857
URL: http://jira.codehaus.org/browse/MNG-1857
Project: Maven 2
Type: Bug
Components: maven-site-plugin
Versions: 2.0.2
Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
Reporter: Indrajit Raychaudhuri
Consider the following POM:
{code:xml}
!-- ... ... --
!-- ... ... --
build
pluginManagement
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
authorfalse/author
/configuration
/plugin
/pluginManagement
/build
!-- ... ... --
!-- ... ... --
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
/plugin
/plugins
/reporting
!-- ... ... --
{code}
{{mvn site:site}} doesn't honor the javadoc configuration specified in the
{{pluginManagement/}} section.
However, {{mvn javadoc:javadoc}} honors them.
This is true not just for javadoc but other plugins like checkstyle as well.
I guess, the {{reporting/}} section doesn't use the {{pluginManagement/}}
section at all.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1857) PluginManagement config is not used by plugins enabled in the site generation phase
[ http://jira.codehaus.org/browse/MNG-1857?page=comments#action_53762 ]
Brett Porter commented on MNG-1857:
---
It's intentionally the other way around.
settings in reporting are already applied to build plugins so they don't need
to be duplicated, but build plugins have a more honerous requirement -
specifically they will often fail the build when the reporting plugin won't
during site generation. For this reason, build configuration is not passed to
the reports.
PluginManagement config is not used by plugins enabled in the site generation
phase
---
Key: MNG-1857
URL: http://jira.codehaus.org/browse/MNG-1857
Project: Maven 2
Type: Bug
Components: maven-site-plugin
Versions: 2.0.2
Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
Reporter: Indrajit Raychaudhuri
Consider the following POM:
{code:xml}
!-- ... ... --
!-- ... ... --
build
pluginManagement
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
authorfalse/author
/configuration
/plugin
/pluginManagement
/build
!-- ... ... --
!-- ... ... --
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
/plugin
/plugins
/reporting
!-- ... ... --
{code}
{{mvn site:site}} doesn't honor the javadoc configuration specified in the
{{pluginManagement/}} section.
However, {{mvn javadoc:javadoc}} honors them.
This is true not just for javadoc but other plugins like checkstyle as well.
I guess, the {{reporting/}} section doesn't use the {{pluginManagement/}}
section at all.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1857) PluginManagement config is not used by plugins enabled in the site generation phase
[ http://jira.codehaus.org/browse/MNG-1857?page=comments#action_53569 ]
Indrajit Raychaudhuri commented on MNG-1857:
This might be related to MNG-1855 but it has been raised for checkstyle-plugin
module. It's true for other plugins as well.
PluginManagement config is not used by plugins enabled in the site generation
phase
---
Key: MNG-1857
URL: http://jira.codehaus.org/browse/MNG-1857
Project: Maven 2
Type: Bug
Components: maven-site-plugin
Versions: 2.0.2
Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
Reporter: Indrajit Raychaudhuri
Consider the following POM:
{code:xml}
!-- ... ... --
!-- ... ... --
build
pluginManagement
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
authorfalse/author
/configuration
/plugin
/pluginManagement
/build
!-- ... ... --
!-- ... ... --
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
/plugin
/plugins
/reporting
!-- ... ... --
{code}
{{mvn site:site}} doesn't honor the javadoc configuration specified in the
{{pluginManagement/}} section.
However, {{mvn javadoc:javadoc}} honors them.
This is true not just for javadoc but other plugins like checkstyle as well.
I guess, the {{reporting/}} section doesn't use the {{pluginManagement/}}
section at all.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
