[jira] Commented: (MSITE-81) Site descriptor resolution never falls back to site.xml
[ http://jira.codehaus.org/browse/MSITE-81?page=comments#action_57307 ] Indrajit Raychaudhuri commented on MSITE-81: The patch is more of a circumvention that a solution. Yes, it's essentially a case of looking into the local filesystem (meaning the ~/.m2/repository) for site.xml when site_en.xml is not available in the same location. I'd imagine mvn --ofline is not same as online mvn without the remote repo avaialble. When we have the second scenario, the regular artifacts build and resolve their dependencies provided I do an 'install' on the dependencies beforehand. Shouldn't it same when building site of the artifact? Site descriptor resolution never falls back to site.xml --- Key: MSITE-81 URL: http://jira.codehaus.org/browse/MSITE-81 Project: Maven 2.x Site Plugin Type: Bug Reporter: Indrajit Raychaudhuri Priority: Critical Attachments: site.log, sitemojo.patch For default locale (i.e., Locale.getDefault() is en) site descriptor for parent project attempt to resolve site_en.xml. But it doesn't fallback to site.xml. -- 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: (MSITE-81) Site descriptor resolution never falls back to site.xml
[ http://jira.codehaus.org/browse/MSITE-81?page=comments#action_57309 ] Indrajit Raychaudhuri commented on MSITE-81: BTW, what's the issue id you mentioned in [MSITE-81#action_57268]? Site descriptor resolution never falls back to site.xml --- Key: MSITE-81 URL: http://jira.codehaus.org/browse/MSITE-81 Project: Maven 2.x Site Plugin Type: Bug Reporter: Indrajit Raychaudhuri Priority: Critical Attachments: site.log, sitemojo.patch For default locale (i.e., Locale.getDefault() is en) site descriptor for parent project attempt to resolve site_en.xml. But it doesn't fallback to site.xml. -- 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] Created: (MSITE-81) Site descriptor resolution never falls back to site.xml
Site descriptor resolution never falls back to site.xml --- Key: MSITE-81 URL: http://jira.codehaus.org/browse/MSITE-81 Project: Maven 2.x Site Plugin Type: Bug Reporter: Indrajit Raychaudhuri Priority: Critical Attachments: sitemojo.patch For default locale (i.e., Locale.getDefault() is en) site descriptor for parent project attempt to resolve site_en.xml. But it doesn't fallback to site.xml. -- 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] Updated: (MSITE-81) Site descriptor resolution never falls back to site.xml
[ http://jira.codehaus.org/browse/MSITE-81?page=all ] Indrajit Raychaudhuri updated MSITE-81: --- Attachment: site.log Site descriptor resolution never falls back to site.xml --- Key: MSITE-81 URL: http://jira.codehaus.org/browse/MSITE-81 Project: Maven 2.x Site Plugin Type: Bug Reporter: Indrajit Raychaudhuri Priority: Critical Attachments: site.log, sitemojo.patch For default locale (i.e., Locale.getDefault() is en) site descriptor for parent project attempt to resolve site_en.xml. But it doesn't fallback to site.xml. -- 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: (MSITE-11) PluginManagement config is not used by plugins enabled in the site generation phase
[ http://jira.codehaus.org/browse/MSITE-11?page=comments#action_53795 ]
Indrajit Raychaudhuri commented on MSITE-11:
Wonderful!
So the reportingManagement/ idea in [#action_53690] _actually_ makes sense to
me now and appears clean enough too.
This also appears to be a candidate for docu. somewhere (maybe in maven-model)
specifying the distinction between buildpluginManagement//build and
reportingManagement/ and what should go where (as part of best-practice).
PluginManagement config is not used by plugins enabled in the site generation
phase
---
Key: MSITE-11
URL: http://jira.codehaus.org/browse/MSITE-11
Project: Maven 2.x Site Plugin
Type: Bug
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_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-1863) Plugin should be configured in reporting not build
[ http://jira.codehaus.org/browse/MNG-1863?page=comments#action_53649 ]
Indrajit Raychaudhuri commented on MNG-1863:
Javadoc plugin config inside {{build.../build}} isn't honored when javadoc
is generated as part of {{site:site}} but it is honored by {{javadoc:javadoc}}.
See a related issue MNG-1857.
Plugin should be configured in reporting not build
--
Key: MNG-1863
URL: http://jira.codehaus.org/browse/MNG-1863
Project: Maven 2
Type: Bug
Components: maven-javadoc-plugin
Versions: 2.0.1
Environment: window xp, jdk 1.5, cygwin
Reporter: Howard M. Lewis Ship
The documentation at
http://maven.apache.org/plugins/maven-javadoc-plugin/configuration.html
indicates that you configure this plugin inside the build element of the
pom; some research revealed that it is part of the reporting element. As a
new Maven (2) user, this really caught me unawares.
--
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]
[jira] Commented: (MNG-1100) next dev version of pom gets release info
[ http://jira.codehaus.org/browse/MNG-1100?page=comments#action_52763 ] Indrajit Raychaudhuri commented on MNG-1100: MNG-1253 seems to have addressed this one. Is there anything else to this that's not covered there? next dev version of pom gets release info --- Key: MNG-1100 URL: http://jira.codehaus.org/browse/MNG-1100 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Fix For: 2.0.2 eg, plugin versions are filled in in the new pom when they weren't before it should match the prior version, with the dependencies, parent and version updated -- 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-1113) Plugin does not support using custom checkstyle XML config file
[ http://jira.codehaus.org/browse/MNG-1113?page=comments#action_52271 ] Indrajit Raychaudhuri commented on MNG-1113: They appear similar (can be linked as 'related' if not 'duplicate'). The description of MNG-587 is more appropriate than the description of this one. +1 with John's plan of action (IMHO, true for MNG-587 as well). For anything else, new issues can be filed appropriately. Plugin does not support using custom checkstyle XML config file --- Key: MNG-1113 URL: http://jira.codehaus.org/browse/MNG-1113 Project: Maven 2 Type: Bug Components: maven-checkstyle-plugin Versions: 2.0-beta-3 Reporter: Vincent Massol Assignee: John Casey Attachments: CheckstyleReport.java, MNG-1113-maven-checkstyle-plugin.patch, checkstyle-config-file.patch, recommended.txt The plugin source code says: /** * Specifies the location of the checkstyle properties that will be used to check the source. * * @parameter */ private File propertiesFile; But in practice it's only loading *properties* and not the XML. The getConfigFile() method is not right and needs to be modified to take into account a custom checkstyle config file. -- 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-1035) javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path
[ http://jira.codehaus.org/browse/MNG-1035?page=comments#action_47860 ] Indrajit Raychaudhuri commented on MNG-1035: Sun Java SDK 1.5.0_04 on Windows XP SP2 I couldn't recreate this specific one on M2-b3 (I had cleaned my .m2 anyway). So Rev 280832, 290370 might not be the entire reason. But having white-space in classpath appears bit unforgiving. Could plexus utils be a suspect? javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path --- Key: MNG-1035 URL: http://jira.codehaus.org/browse/MNG-1035 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Versions: 2.0-beta-3 Reporter: Indrajit Raychaudhuri Fix For: 2.0-beta-4 javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path as it tries to include jars from repository. The same project used to work with M2-beta1. The changes in Revision 280832, 290370 might have something to do with this. -- 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-1035) javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path
[ http://jira.codehaus.org/browse/MNG-1035?page=comments#action_47865 ] Indrajit Raychaudhuri commented on MNG-1035: With a difference :) In MNG-620 the problem is due to white-space in the path of javadoc.exe but this one is due to white-space in the classpath. FWIW my JAVA_HOME is C:\MyHome\Programs\JavaSE\jdk1.5.0_04. So if the path resolution (exe path as well as classpath) is done by the same code then they are possibly related. javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path --- Key: MNG-1035 URL: http://jira.codehaus.org/browse/MNG-1035 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Versions: 2.0-beta-3 Reporter: Indrajit Raychaudhuri Fix For: 2.0-beta-4 javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path as it tries to include jars from repository. The same project used to work with M2-beta1. The changes in Revision 280832, 290370 might have something to do with this. -- 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] Created: (MNG-1035) javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path
javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path --- Key: MNG-1035 URL: http://jira.codehaus.org/browse/MNG-1035 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Versions: 2.0-beta-3 Reporter: Indrajit Raychaudhuri javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path as it tries to include jars from repository. The same project used to work with M2-beta1. The changes in Revision 280832, 290370 might have something to do with this. -- 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-704) javadoc plugin doesn't honor multiple custom tags
[ http://jira.codehaus.org/browse/MNG-704?page=comments#action_47318 ] Indrajit Raychaudhuri commented on MNG-704: --- I had tried tag.usage:a:Usage:, .todo:a:To do something:, .fixme:a:Fixme:/tag before posting the issue but didn't get it to work (maybe I missed the white-spaces in-between :)). It works M2-beta-1 onwards and should serve the purpose. However, having provision to describe each tag separately would make it consistent (can be deferred to 2.1). javadoc plugin doesn't honor multiple custom tags - Key: MNG-704 URL: http://jira.codehaus.org/browse/MNG-704 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Versions: 2.0-alpha-3 Reporter: Indrajit Raychaudhuri Assignee: Vincent Siveton Priority: Minor Fix For: 2.0-beta-4 M2 javaodc plugin doesn't honor multiple tag as it did with M1. In M1 we could specify this in project.properties: maven.javadoc.customtags = usage todo fixme usage.name = .usage usage.description = Usage: usage.enabled = true usage.scope = all todo.name = .todo todo.description = Todo: todo.enabled = false todo.scope = all fixme.name = .fixme fixme.description = Fixme: fixme.enabled = false fixme.scope = all However, in M2 the putting the tag/ switch isn't honor multiple times. Only the last one get passed to the javadoc -tag switch. -- 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] Created: (MNG-704) javadoc plugin doesn't honor multiple custom tags
javadoc plugin doesn't honor multiple custom tags - Key: MNG-704 URL: http://jira.codehaus.org/browse/MNG-704 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-alpha-3 Reporter: Indrajit Raychaudhuri M2 javaodc plugin doesn't honor multiple tag as it did with M1. In M1 we could specify this in project.properties: maven.javadoc.customtags = usage todo fixme usage.name = .usage usage.description = Usage: usage.enabled = true usage.scope = all todo.name = .todo todo.description = Todo: todo.enabled = false todo.scope = all fixme.name = .fixme fixme.description = Fixme: fixme.enabled = false fixme.scope = all However, in M2 the putting the tag/ switch isn't honor multiple times. Only the last one get passed to the javadoc -tag switch. -- 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]
