[jira] Created: (MSUREFIRE-43) Surefire fails to start when the local repository and the project (pom.xml) lives in different window drives

Surefire fails to start when the local repository and the project (pom.xml) lives in different window drives Key: MSUREFIRE-43 URL:

[jira] Commented: (MJAVADOC-25) option -locale must be first on the command line.

[ http://jira.codehaus.org/browse/MJAVADOC-25?page=comments#action_54377 ] Martin Desruisseaux commented on MJAVADOC-25: - It still not fixed in maven-javadoc-plugin 2.0-beta-3. We still have the error -locale argument must be first. option

[jira] Created: (MJAVADOC-39) javadoc plugin (beta 3) chdir in 'target/site/apidocs', causing overview parameter to fail

javadoc plugin (beta 3) chdir in 'target/site/apidocs', causing overview parameter to fail Key: MJAVADOC-39 URL: http://jira.codehaus.org/browse/MJAVADOC-39 Project: Maven 2.x

[jira] Commented: (MJAVADOC-19) Overview parameter isn't having backslashes fixed before writing out to arguments

[ http://jira.codehaus.org/browse/MJAVADOC-19?page=comments#action_54379 ] Martin Desruisseaux commented on MJAVADOC-19: - Since this issue as about the path to an overview file, it may be related to MJAVADOC-39. Overview parameter isn't

[jira] Commented: (MNG-1610) locale parameter causes javadoc to fail

[ http://jira.codehaus.org/browse/MNG-1610?page=comments#action_53367 ] Martin Desruisseaux commented on MNG-1610: -- Looks like a duplicate of MNG-1163 locale parameter causes javadoc to fail ---

[jira] Commented: (MNG-1768) excludePackageNames property doesn't work

[ http://jira.codehaus.org/browse/MNG-1768?page=comments#action_53368 ] Martin Desruisseaux commented on MNG-1768: -- The way javadoc plugin currently work (passes the source file names) cause some trouble to us, because it prevent @see and @link

[jira] Commented: (MNG-1163) option -locale must be first on the command line.

[ http://jira.codehaus.org/browse/MNG-1163?page=comments#action_53373 ] Martin Desruisseaux commented on MNG-1163: -- This bug (as well as many other javadoc plugin bugs) doesn't appear to be fixed in Maven 2.0.1. It may be because the Maven plugins

[jira] Commented: (MNG-1610) locale parameter causes javadoc to fail

[ http://jira.codehaus.org/browse/MNG-1610?page=comments#action_53374 ] Martin Desruisseaux commented on MNG-1610: -- According MNG-1163, this bug is fixed since 2.0 RC. But the javadoc plugin doesn't seem to be deployed on ibiblio since 2.0 beta 2.

[jira] Commented: (MNG-1386) Failure to launch Javadoc correctly

[ http://jira.codehaus.org/browse/MNG-1386?page=comments#action_49763 ] Martin Desruisseaux commented on MNG-1386: -- This is duplicated of MNG-1237. Failure to launch Javadoc correctly --- Key: MNG-1386

[jira] Created: (MNG-1237) Regression: javadoc plugin fails when a maxmemory parameter is provided

Regression: javadoc plugin fails when a maxmemory parameter is provided - Key: MNG-1237 URL: http://jira.codehaus.org/browse/MNG-1237 Project: Maven 2 Type: Bug Components:

[jira] Commented: (MNG-1185) Parameter siteDirectory in goal site conflicts with parameter of the same name in goal deploy

[ http://jira.codehaus.org/browse/MNG-1185?page=comments#action_48502 ] Martin Desruisseaux commented on MNG-1185: -- Thanks for taking care of this issue :) (actually, I wonder if the priority should have been something higher than major, since any

[jira] Created: (MNG-1185) Parameter siteDirectory in goal site conflicts with parameter of the same name in goal deploy

Parameter siteDirectory in goal site conflicts with parameter of the same name in goal deploy --- Key: MNG-1185 URL: http://jira.codehaus.org/browse/MNG-1185 Project: Maven 2

[jira] Created: (MNG-1152) Javadoc plugin add a spurious -excludePackageNames option on the javadoc command line

Javadoc plugin add a spurious -excludePackageNames option on the javadoc command line - Key: MNG-1152 URL: http://jira.codehaus.org/browse/MNG-1152 Project: Maven 2 Type: Bug

[jira] Created: (MNG-1154) group parameter seems hard to use

group parameter seems hard to use --- Key: MNG-1154 URL: http://jira.codehaus.org/browse/MNG-1154 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Versions: 2.0-beta-3 Environment: Windows XP Reporter: Martin

[jira] Created: (MNG-1156) Would like a way to get default javadoc behavior

Would like a way to get default javadoc behavior Key: MNG-1156 URL: http://jira.codehaus.org/browse/MNG-1156 Project: Maven 2 Type: Wish Components: maven-javadoc-plugin Versions: 2.0-beta-3 Environment:

[jira] Commented: (MNG-1156) Would like a way to get default javadoc behavior

[ http://jira.codehaus.org/browse/MNG-1156?page=comments#action_48193 ] Martin Desruisseaux commented on MNG-1156: -- One reason why I would like to keep Sun's defauly stylesheet is that I would like to try javadoc prototypes like the one in

[jira] Created: (MNG-1163) option -locale must be first on the command line.

option -locale must be first on the command line. - Key: MNG-1163 URL: http://jira.codehaus.org/browse/MNG-1163 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Versions: 2.0-beta-3 Environment:

[jira] Created: (MNG-1164) additionalparam parameter should not put an -additional on the javadoc command line.

additionalparam parameter should not put an -additional on the javadoc command line. Key: MNG-1164 URL: http://jira.codehaus.org/browse/MNG-1164 Project: Maven 2 Type: Bug

[jira] Created: (MNG-1166) [EMAIL PROTECTED] foo} doesn't work when foo is a package name

[EMAIL PROTECTED] foo} doesn't work when foo is a package name - Key: MNG-1166 URL: http://jira.codehaus.org/browse/MNG-1166 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Versions: 2.0-beta-3