[jira] [Commented] (MNG-8015) Control the type of path where each dependency can be placed

[ https://issues.apache.org/jira/browse/MNG-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806293#comment-17806293 ] Martin Desruisseaux commented on MNG-8015: -- Pull request: https://github.com/apach

[jira] [Created] (MNG-8015) Control the type of path where each dependency can be placed

Martin Desruisseaux created MNG-8015: Summary: Control the type of path where each dependency can be placed Key: MNG-8015 URL: https://issues.apache.org/jira/browse/MNG-8015 Project: Maven

[jira] [Commented] (MNG-7855) Dependencies wrongly put on class-path rather than module-path

[ https://issues.apache.org/jira/browse/MNG-7855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759233#comment-17759233 ] Martin Desruisseaux commented on MNG-7855: -- Another area where being on the class-

[jira] [Comment Edited] (MNG-7855) Dependencies wrongly put on class-path rather than module-path

[ https://issues.apache.org/jira/browse/MNG-7855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748556#comment-17748556 ] Martin Desruisseaux edited comment on MNG-7855 at 7/28/23 11:30 AM: -

[jira] [Commented] (MNG-7855) Dependencies wrongly put on class-path rather than module-path

[ https://issues.apache.org/jira/browse/MNG-7855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748556#comment-17748556 ] Martin Desruisseaux commented on MNG-7855: -- Java code for generating workarounds

[jira] [Commented] (SUREFIRE-2097) More configuration for surefire JPMS

[ https://issues.apache.org/jira/browse/SUREFIRE-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748544#comment-17748544 ] Martin Desruisseaux commented on SUREFIRE-2097: --- Thanks for the reply! D

[jira] [Commented] (SUREFIRE-2097) More configuration for surefire JPMS

[ https://issues.apache.org/jira/browse/SUREFIRE-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748204#comment-17748204 ] Martin Desruisseaux commented on SUREFIRE-2097: --- This issue seems relate

[jira] [Created] (MNG-7855) Dependencies wrongly put on class-path rather than module-path

Martin Desruisseaux created MNG-7855: Summary: Dependencies wrongly put on class-path rather than module-path Key: MNG-7855 URL: https://issues.apache.org/jira/browse/MNG-7855 Project: Maven

[jira] [Commented] (MRESOURCES-237) Resource plugin's handling of symbolic links changed in 3.0.x, broke existing behavior

[ https://issues.apache.org/jira/browse/MRESOURCES-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418698#comment-17418698 ] Martin Desruisseaux commented on MRESOURCES-237: Yes, but it may be c

[jira] [Commented] (MRESOURCES-237) Resource plugin's handling of symbolic links changed in 3.0.x, broke existing behavior

[ https://issues.apache.org/jira/browse/MRESOURCES-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418686#comment-17418686 ] Martin Desruisseaux commented on MRESOURCES-237: I had to dowgrade to

[jira] [Commented] (MJAVADOC-329) Allow generation of empty javadoc JARs

[ https://issues.apache.org/jira/browse/MJAVADOC-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16705956#comment-16705956 ] Martin Desruisseaux commented on MJAVADOC-329: -- Well, bug 4492654 is marke

[jira] [Commented] (MJAVADOC-449) javadoc:aggregate fails with JDK 9

[ https://issues.apache.org/jira/browse/MJAVADOC-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599627#comment-16599627 ] Martin Desruisseaux commented on MJAVADOC-449: -- I think that the issue is

[jira] [Created] (MCOMPILER-336) Dependency that should be on modulepath sometime put on classpath

Martin Desruisseaux created MCOMPILER-336: - Summary: Dependency that should be on modulepath sometime put on classpath Key: MCOMPILER-336 URL: https://issues.apache.org/jira/browse/MCOMPILER-336

[jira] [Updated] (MJAVADOC-494) javadoc:aggregate ignores repositories declared in sub-modules

[ https://issues.apache.org/jira/browse/MJAVADOC-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Desruisseaux updated MJAVADOC-494: - Description: Given a multi-modules project with: * A {{… URL A …}} element in t

[jira] [Created] (MJAVADOC-494) [REGRESSION] javadoc:aggregate ignores repositories declared in sub-modules

Martin Desruisseaux created MJAVADOC-494: Summary: [REGRESSION] javadoc:aggregate ignores repositories declared in sub-modules Key: MJAVADOC-494 URL: https://issues.apache.org/jira/browse/MJAVADOC-494

[jira] [Commented] (MJAR-223) classpathLayoutType is not taken into account when building the classpath attribute in the manifest

[ https://issues.apache.org/jira/browse/MJAR-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318942#comment-15318942 ] Martin Desruisseaux commented on MJAR-223: -- Same issue for me. I downgraded to vers

[jira] (MJAVADOC-387) Handle JDK8 -Xdoclint

[ https://jira.codehaus.org/browse/MJAVADOC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345104#comment-345104 ] Martin Desruisseaux commented on MJAVADOC-387: -- A support for {{-Xdoclint}} would be

[jira] (MJAVADOC-368) Can not use a comma (,) in option additionalparam

[ https://jira.codehaus.org/browse/MJAVADOC-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345103#comment-345103 ] Martin Desruisseaux commented on MJAVADOC-368: -- This is also a problem for the new J

[jira] (MNG-5437) Do not load plugins from snapshot JARs

[ https://jira.codehaus.org/browse/MNG-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320112#comment-320112 ] Martin Desruisseaux commented on MNG-5437: -- The proposed patch may help in making Maven buil

[jira] (MNG-5246) Allow inside element

Martin Desruisseaux created MNG-5246: Summary: Allow inside element Key: MNG-5246 URL: https://jira.codehaus.org/browse/MNG-5246 Project: Maven 2 & 3 Issue Type: Improvement C

[jira] Commented: (MJAVADOC-134) Support aggregated reports at each level in the multi-module hierarchy

[ http://jira.codehaus.org/browse/MJAVADOC-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184119#action_184119 ] Martin Desruisseaux commented on MJAVADOC-134: -- Actually I'm interrested in a variant

[jira] Commented: (MJAVADOC-145) If Javadoc is set to aggregate, the build fails inside a Maven plugin module

[ http://jira.codehaus.org/browse/MJAVADOC-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184118#action_184118 ] Martin Desruisseaux commented on MJAVADOC-145: -- Is this bug really fixed? I'm using Ma

[jira] Created: (MECLIPSE-251) Allows prefixing of eclipse project name

Allows prefixing of eclipse project name Key: MECLIPSE-251 URL: http://jira.codehaus.org/browse/MECLIPSE-251 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Components: multiprojec

[jira] Created: (MJAR-61) Manifest classpath ignores the "real" JAR filenames specified in

Manifest classpath ignores the "real" JAR filenames specified in Key: MJAR-61 URL: http://jira.codehaus.org/browse/MJAR-61 Project: Maven 2.x Jar Plugin Issue Type

[jira] Commented: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions

[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_78430 ] Martin Desruisseaux commented on MJAR-28: - Maybe related to this issue: the manifest classpath generated by Maven ignores the "real" JAR name as specified in {{>}}. Fo

[jira] Commented: (MJAVADOC-66) Aggregated Javadoc does not use module-level dependencies

[ http://jira.codehaus.org/browse/MJAVADOC-66?page=comments#action_76148 ] Martin Desruisseaux commented on MJAVADOC-66: - Is this bug really fixed in {{maven-javadoc-plugin}} version 2.0? Aggregated javadoc still fail to find module-l

[jira] Created: (MPJAVADOC-77) allow only one taglet

allow only one taglet -- Key: MPJAVADOC-77 URL: http://jira.codehaus.org/browse/MPJAVADOC-77 Project: maven-javadoc-plugin Issue Type: Bug Reporter: Martin Desruisseaux The {{}} configuration elemen

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

[ http://jira.codehaus.org/browse/MSUREFIRE-43?page=comments#action_65543 ] Martin Desruisseaux commented on MSUREFIRE-43: -- I can confirm that the bug is fixed with Maven 2.0.4 and maven-surefire-plugin 2.1.3. Thanks for yours work! > Surefire

[jira] Updated: (MJAVADOC-28) [EMAIL PROTECTED] foo} doesn't work when "foo" is a package name

[ http://jira.codehaus.org/browse/MJAVADOC-28?page=all ] Martin Desruisseaux updated MJAVADOC-28: Attachment: test.zip > [EMAIL PROTECTED] foo} doesn't work when "foo" is a package name > - > >

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

[ http://jira.codehaus.org/browse/MJAVADOC-36?page=comments#action_60526 ] Martin Desruisseaux commented on MJAVADOC-36: - Thanks for doing all this javadoc work. > Would like a way to get default javadoc behavior > --