[jira] Updated: (MRELEASE-581) Git relative pathing broken with release plugin

[ https://jira.codehaus.org/browse/MRELEASE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Stabiszewski updated MRELEASE-581: - Attachment: gitexe.zip This is a patch for this issue. It will create relative

[jira] Created: (MJAR-145) Option to automatically seal all packages included in the jar

Option to automatically seal all packages included in the jar - Key: MJAR-145 URL: https://jira.codehaus.org/browse/MJAR-145 Project: Maven 2.x JAR Plugin Issue Type: New Feature

[jira] Commented: (WAGON-343) wagon-scp should remove target area prior to uploading/unzipping new content

[ https://jira.codehaus.org/browse/WAGON-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280648#comment-280648 ] Jamal commented on WAGON-343: - That sounds reasonable. wagon-scp should remove target area prior to

[jira] Commented: (MASSEMBLY-108) Assembly Plugin Implicitly Excludes Empty Directory

[ https://jira.codehaus.org/browse/MASSEMBLY-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280659#comment-280659 ] Julien HENRY commented on MASSEMBLY-108: We are facing the same issue: empty directory

[jira] Created: (MCOMPILER-161) Exclude ignored for sources generated during the generate-sources phase

Exclude ignored for sources generated during the generate-sources phase --- Key: MCOMPILER-161 URL: https://jira.codehaus.org/browse/MCOMPILER-161 Project: Maven 2.x Compiler Plugin

[jira] Created: (MJARSIGNER-21) jars signed using Java 7 have invalid SHA1 signature

jars signed using Java 7 have invalid SHA1 signature -- Key: MJARSIGNER-21 URL: https://jira.codehaus.org/browse/MJARSIGNER-21 Project: Maven 2.x Jar Signer Plugin Issue Type: Bug

[jira] Commented: (MINVOKER-107) mvn deploy of SNAPSHOT failed with maven3 when invoker:run look for current build dependency

[ https://jira.codehaus.org/browse/MINVOKER-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280663#comment-280663 ] Tony Chemit commented on MINVOKER-107: -- I tried to make a IT but could not reproduce the

[jira] Created: (MCOMPILER-162) when annotation processing is disabled by specifying procnone/proc, target/generated-sources/annotations and target/generated-sources/test-annotations directories a

when annotation processing is disabled by specifying procnone/proc, target/generated-sources/annotations and target/generated-sources/test-annotations directories are still created, passed to javac via -s option, and added to project sources dirs

[jira] Created: (WAGON-353) StreamWagon.putFromStream() fails with IllegalStateException

StreamWagon.putFromStream() fails with IllegalStateException Key: WAGON-353 URL: https://jira.codehaus.org/browse/WAGON-353 Project: Maven Wagon Issue Type: Bug

[jira] Commented: (SCM-634) Clearcase provider status keeps displaying Can't load the scm provider. You need to define a connectionUrl parameter but connection node is defined.

[ https://jira.codehaus.org/browse/SCM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280668#comment-280668 ] Justin Bleach commented on SCM-634: --- Looking at the source: Is not the

[jira] Issue Comment Edited: (SCM-634) Clearcase provider status keeps displaying Can't load the scm provider. You need to define a connectionUrl parameter but connection node is defined.

[ https://jira.codehaus.org/browse/SCM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280668#comment-280668 ] Justin Bleach edited comment on SCM-634 at 10/5/11 1:24 PM: Looking at the

[jira] Commented: (SCM-634) Clearcase provider status keeps displaying Can't load the scm provider. You need to define a connectionUrl parameter but connection node is defined.

[ https://jira.codehaus.org/browse/SCM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280669#comment-280669 ] Robert Scholte commented on SCM-634:

duplicate class error with symbolic liked folder

Hi, Each folder in my project has a symbolic link to the folder where the backed files exists. Maven happens to compile the files in the current directory as well as the symbolically linked directory and hence throws duplicate class error. I have tried using exclude in the plugins configuration,

[jira] Created: (MSHADE-105) Classes processed by the relocator still have references to the original classes in their constant pools

Classes processed by the relocator still have references to the original classes in their constant pools Key: MSHADE-105 URL:

[jira] Commented: (MNG-3472) configuration possibilities to limit size of local repository

[ https://jira.codehaus.org/browse/MNG-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280678#comment-280678 ] Lo-Tan commented on MNG-3472: - I also think this should be a configured responsibility of Maven. Maven

[jira] Updated: (MECLIPSE-388) Correct classpath ordering in .classpath

[ https://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Noel Rouvignac updated MECLIPSE-388: - Attachment: ideal.classpath Hi Barrie, Many thanks for your help on this issue. I

[jira] Issue Comment Edited: (MECLIPSE-388) Correct classpath ordering in .classpath

[ https://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280682#comment-280682 ] Jean-Noel Rouvignac edited comment on MECLIPSE-388 at 10/5/11 3:35 PM:

[jira] Commented: (MECLIPSE-388) Correct classpath ordering in .classpath

[ https://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280684#comment-280684 ] Robert Scholte commented on MECLIPSE-388: - Jean-Noël, this is *not* the order Maven will

[jira] Commented: (MCOMPILER-120) Javac compiler plugin doesn't support -Werror

[ https://jira.codehaus.org/browse/MCOMPILER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280686#comment-280686 ] Robert Scholte commented on MCOMPILER-120: -- It's not that hard, but we've provided some

[jira] Commented: (MCOMPILER-120) Javac compiler plugin doesn't support -Werror

[ https://jira.codehaus.org/browse/MCOMPILER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280687#comment-280687 ] Steven Schlansker commented on MCOMPILER-120: - Kristian commented above that the

[jira] Commented: (MCOMPILER-120) Javac compiler plugin doesn't support -Werror

[ https://jira.codehaus.org/browse/MCOMPILER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280688#comment-280688 ] Steven Schlansker commented on MCOMPILER-120: - Ref:

[jira] Created: (MJAVADOC-330) Ability to exclude speciifc classes

Ability to exclude speciifc classes --- Key: MJAVADOC-330 URL: https://jira.codehaus.org/browse/MJAVADOC-330 Project: Maven 2.x Javadoc Plugin Issue Type: New Feature Affects Versions: 2.8

[jira] Commented: (MJAVADOC-330) Ability to exclude speciifc classes

[ https://jira.codehaus.org/browse/MJAVADOC-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280700#comment-280700 ] Gili commented on MJAVADOC-330: --- Please correct the title of this issue. I mistakenly misspelled

[jira] Updated: (MJAVADOC-330) Ability to exclude specific classes

[ https://jira.codehaus.org/browse/MJAVADOC-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MJAVADOC-330: -- Summary: Ability to exclude specific classes (was: Ability to exclude speciifc classes)

[jira] Created: (MPLUGIN-188) .NoSuchMethodError: org.apache.maven.settings.RuntimeInfo.init(Lorg/apache/maven/settings/Settings

.NoSuchMethodError: org.apache.maven.settings.RuntimeInfo.init(Lorg/apache/maven/settings/Settings Key: MPLUGIN-188 URL:

[jira] Commented: (SUREFIRE-770) persistence.xml in src/test/resources/META-INF is not taken into account

[ https://jira.codehaus.org/browse/SUREFIRE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280705#comment-280705 ] Kristian Rosenvold commented on SUREFIRE-770: - Which issue/solutuion are you