[jira] (MSOURCES-64) forceCreation=true doesn't create test source package when src/test missing
[ https://jira.codehaus.org/browse/MSOURCES-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MSOURCES-64. Resolution: Fixed Fix Version/s: 2.3 Assignee: Olivier Lamy fixed http://svn.apache.org/r1437781 > forceCreation=true doesn't create test source package when src/test missing > --- > > Key: MSOURCES-64 > URL: https://jira.codehaus.org/browse/MSOURCES-64 > Project: Maven 2.x Source Plugin > Issue Type: Bug >Affects Versions: 2.2.1 >Reporter: Hung Huynh >Assignee: Olivier Lamy > Fix For: 2.3 > > > forceCreation=true should force the creation of -test-sources jar no matter > what -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (WAGON-384) Maven fails to download artifacts larger than 2 GB
Robert Baker created WAGON-384: -- Summary: Maven fails to download artifacts larger than 2 GB Key: WAGON-384 URL: https://jira.codehaus.org/browse/WAGON-384 Project: Maven Wagon Issue Type: Bug Components: wagon-provider-api Affects Versions: 2.2 Environment: This issue is not dependent on the operating system and hardware. Reporter: Robert Baker Attachments: AbstractWagon.java If a Maven build includes a dependency for an artifact that is larger than 2 GB in size, the download of the artifact during the build terminates at 2 GB and the following error is reported by Maven: [WARNING] Checksum validation failed, expected 5b0fafa21f2b3e9c4e3b7ef3c5306f82bcb9fc85 but is e9ef494d39de097b9a02531993688ceebdce39e1 Maven repeats the download a second time with the same error result, then build fails. The failure is caused when the transfer method in AbstractWagon.java receives maxSize parameter, which is an integer, set to Integer.MAX_VALUE, rather than the actual size of the artifact. This value is then decremented to zero, which causes the download to terminate prematurely. The attached file (AbstractWagon.java) contains changes in the transfer method that use the value Integer.MAX_VALUE as a trigger that causes the routine to ignore the maxSize parameter's value and download the artifact until an EOF is detected, regardless of its size. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository root is not the working directory
[
https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317886#comment-317886
]
Darryl L. Miles edited comment on SCM-709 at 1/23/13 4:13 PM:
--
@Tim
cd subdir/in/one/git/repo
git status --porcelain .
Note the use of the "." file name.
This can be used to get SVN like behaviour where only the files changes below
the current directly are shown.
was (Author: dlmiles):
@Tim
cd subdir/in/one/git/repo
git status --porcelain .
can be used to get SVN like behaviour where only the files changes below the
current directly are shown.
> REGRESSION: git status doesn't work if repository root is not the working
> directory
> ---
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.8, 1.8.1
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result
> language independend.
> Without the {{--porcelain}} option files were listed relative to the working
> directory, but with {{--porcelain}} files are listed relative to the
> repository root. In most cases these are the same, but not always.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository root is not the working directory
[
https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317886#comment-317886
]
Darryl L. Miles commented on SCM-709:
-
@Tim
cd subdir/in/one/git/repo
git status --porcelain .
can be used to get SVN like behaviour where only the files changes below the
current directly are shown.
> REGRESSION: git status doesn't work if repository root is not the working
> directory
> ---
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.8, 1.8.1
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result
> language independend.
> Without the {{--porcelain}} option files were listed relative to the working
> directory, but with {{--porcelain}} files are listed relative to the
> repository root. In most cases these are the same, but not always.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-4715) version expression constant
[
https://jira.codehaus.org/browse/MNG-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317883#comment-317883
]
Nathaniel Mishkin commented on MNG-4715:
FWIW, my use case for using properties in specifying the for a
project's component is this: I've created a project whose sole purpose in life
is to create a variant (in this case, signed) of an existing artifact that's
not mine (not produced by any of my projects). In the variant project I've
created I want to do something like this:
4.32
...
x
${x.version}
...
x.variant
${x.version}
...
(In real life the property definition is specified an ancestor POM.)
> version expression constant
> ---
>
> Key: MNG-4715
> URL: https://jira.codehaus.org/browse/MNG-4715
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies, POM
>Affects Versions: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1
> Environment: eclipse linux xp
>Reporter: Faruk
>Priority: Critical
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: untitled.JPG
>
>
> early versions, we define modules versions with expressions, and set them to
> the parent pom,
> simply;
>
> 1.0.1
> 1.0.1
>
> and then, we give this property to modules pom as expression ,
> ik-plug
> jar
> ${ibb-core-util.versionn}
> but know , it gives an error you know like this,
> "[WARNING] Some problems were encountered while building the effective model
> for ibb-parent:ibb-modules-parent:pom:1.0.0
> [WARNING] 'version' contains an expression but should be a constant. @
> ibb-parent:ibb-modules-parent:${ibb-core-jars.version},
> C:\dev\ibb\workspace\core\ibb-modules-parent\pom.xml
> "
> but I think that, this enhancement is causes wrong result,
> think that , if we have i project already developing about 3 years, this
> project has a lot of modules, and this modules have sub modules , and this
> sub modules already bound to some other modules not define in your pom, but
> your updates must be affect them, at this situation, developer want to write
> the existing version numbers with properties to parent pom, and want to
> manage them like this. at the attach file below , the close projects are
> belongs to open projects, but they are the different team developing this. I
> cant force the other developers to cache their versions, I must use this
> versions as initial step
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-197) dependencies no more at classpath
[ https://jira.codehaus.org/browse/MCOMPILER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317880#comment-317880 ] Olivier Lamy commented on MCOMPILER-197: @romain maven version ? > dependencies no more at classpath > - > > Key: MCOMPILER-197 > URL: https://jira.codehaus.org/browse/MCOMPILER-197 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 3.0 >Reporter: Romain manni-Bucau > Attachments: compiler-test.zip > > > before (version 2.5.1) dependencies of compiler plugin were added to javac > classpath, now it seems (didn't check so maybe it is wrong) it is no more the > case > i attached a sample. Running "mvn compile" with version 2.5.1 you'll get a > file target/generated-sources/org/issue/Person_.java. With version 3.0 you > get a folder target/annotations and no more file. > This is really blocking for stuff like openjpa metamodel generation where > with version 3.0 it needs to use an ant task which is not so straight forward. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-199) Plugin 3.0 does not compile src/main/groovy if neither src/main/java nor src/main/resources folders exist
[
https://jira.codehaus.org/browse/MCOMPILER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MCOMPILER-199.
--
Resolution: Fixed
fixed http://svn.apache.org/r1437748
> Plugin 3.0 does not compile src/main/groovy if neither src/main/java nor
> src/main/resources folders exist
> -
>
> Key: MCOMPILER-199
> URL: https://jira.codehaus.org/browse/MCOMPILER-199
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.0
> Environment: mac os, jdk 1.6 and jdk 1.7, Apache Maven 3.0.3
> (r1075438; 2011-02-28 18:31:09+0100)
>Reporter: Roman Stumm
>Assignee: Olivier Lamy
> Fix For: 3.1
>
>
> The previous version 2.5.1 compiled the project that only had groovy-sources,
> but after switching to version 3.0, the created jar was empty and no sources
> had been compiled.
> project-layout
> pom.xml
> src
> main
> groovy
>MyClass.groovy
> After adding a dummy-file into src/main/resources, it works.
> Example output of mvn -o compile with version 3.0
> --
> [INFO] --- groovy-eclipse-compiler:2.7.0-01:add-groovy-build-paths
> (default-add-groovy-build-paths) @ myproject ---
> [INFO] Adding /src/main/groovy to the list of source folders
> [INFO] Adding /src/test/groovy to the list of test source folders
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> myproject ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory ./src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ myproject ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
>
> [INFO] BUILD SUCCESS
> Example output of mvn -o compile with version 2.5.1
> ---
> [INFO] --- groovy-eclipse-compiler:2.7.0-01:add-groovy-build-paths
> (default-add-groovy-build-paths) @ myproject ---
> [INFO] Adding /src/main/groovy to the list of source folders
> [INFO] Adding /src/test/groovy to the list of test source folders
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> myproject ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /Users/roman.stumm/projects/boxx-super/groovy-boxx/myproject/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ myproject
> ---
> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
> [INFO] Classpath:
> [INFO] All args: [-cp, reading and writing
> [11 .class files generated]
> [INFO] Compilation complete.
> The pom.xml
>
>3.0
> 2.7.0-01
> 2.0.4-04
>
> ...
>
>
>
> maven-compiler-plugin
> ${maven-compiler-version}
>
> 1.6
> 1.6
> groovy-eclipse-compiler
> true
>
>
>
> org.codehaus.groovy
> groovy-eclipse-compiler
> ${groovy-compiler-version}
>
>
> org.codehaus.groovy
> groovy-eclipse-batch
> ${groovy-eclipse-batch}
>
>
>
>
> org.codehaus.groovy
> groovy-eclipse-compiler
> ${groovy-compiler-version}
> true
>
>
> org.codehaus.groovy
> groovy-eclipse-batch
> ${groovy-eclipse-batch}
>
>
>
> ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-199) Plugin 3.0 does not compile src/main/groovy if neither src/main/java nor src/main/resources folders exist
[
https://jira.codehaus.org/browse/MCOMPILER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317876#comment-317876
]
Olivier Lamy edited comment on MCOMPILER-199 at 1/23/13 3:25 PM:
-
a bit weird issue.
As a workaround you can add this configuration in the plugin
{code}
src/main/groovy
...
**/*.groovy
{code}
was (Author: olamy):
a bit weird issue.
As a workaround you can add this configuration in the plugin
{code}
**/*.groovy
{code}
> Plugin 3.0 does not compile src/main/groovy if neither src/main/java nor
> src/main/resources folders exist
> -
>
> Key: MCOMPILER-199
> URL: https://jira.codehaus.org/browse/MCOMPILER-199
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.0
> Environment: mac os, jdk 1.6 and jdk 1.7, Apache Maven 3.0.3
> (r1075438; 2011-02-28 18:31:09+0100)
>Reporter: Roman Stumm
>Assignee: Olivier Lamy
> Fix For: 3.1
>
>
> The previous version 2.5.1 compiled the project that only had groovy-sources,
> but after switching to version 3.0, the created jar was empty and no sources
> had been compiled.
> project-layout
> pom.xml
> src
> main
> groovy
>MyClass.groovy
> After adding a dummy-file into src/main/resources, it works.
> Example output of mvn -o compile with version 3.0
> --
> [INFO] --- groovy-eclipse-compiler:2.7.0-01:add-groovy-build-paths
> (default-add-groovy-build-paths) @ myproject ---
> [INFO] Adding /src/main/groovy to the list of source folders
> [INFO] Adding /src/test/groovy to the list of test source folders
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> myproject ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory ./src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ myproject ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
>
> [INFO] BUILD SUCCESS
> Example output of mvn -o compile with version 2.5.1
> ---
> [INFO] --- groovy-eclipse-compiler:2.7.0-01:add-groovy-build-paths
> (default-add-groovy-build-paths) @ myproject ---
> [INFO] Adding /src/main/groovy to the list of source folders
> [INFO] Adding /src/test/groovy to the list of test source folders
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> myproject ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /Users/roman.stumm/projects/boxx-super/groovy-boxx/myproject/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ myproject
> ---
> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
> [INFO] Classpath:
> [INFO] All args: [-cp, reading and writing
> [11 .class files generated]
> [INFO] Compilation complete.
> The pom.xml
>
>3.0
> 2.7.0-01
> 2.0.4-04
>
> ...
>
>
>
> maven-compiler-plugin
> ${maven-compiler-version}
>
> 1.6
> 1.6
> groovy-eclipse-compiler
> true
>
>
>
> org.codehaus.groovy
> groovy-eclipse-compiler
> ${groovy-compiler-version}
>
>
> org.codehaus.groovy
> groovy-eclipse-batch
> ${groovy-eclipse-batch}
>
>
>
>
> org.codehaus.groovy
> groovy-eclipse-compiler
> ${groovy-compiler-version}
> true
>
>
> org.codehaus.groovy
> groovy-eclipse-batch
> ${groovy-eclipse-batch}
>
>
>
> ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-199) Plugin 3.0 does not compile src/main/groovy if neither src/main/java nor src/main/resources folders exist
[
https://jira.codehaus.org/browse/MCOMPILER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317876#comment-317876
]
Olivier Lamy commented on MCOMPILER-199:
a bit weird issue.
As a workaround you can add this configuration in the plugin
{code}
**/*.groovy
{code}
> Plugin 3.0 does not compile src/main/groovy if neither src/main/java nor
> src/main/resources folders exist
> -
>
> Key: MCOMPILER-199
> URL: https://jira.codehaus.org/browse/MCOMPILER-199
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.0
> Environment: mac os, jdk 1.6 and jdk 1.7, Apache Maven 3.0.3
> (r1075438; 2011-02-28 18:31:09+0100)
>Reporter: Roman Stumm
>Assignee: Olivier Lamy
> Fix For: 3.1
>
>
> The previous version 2.5.1 compiled the project that only had groovy-sources,
> but after switching to version 3.0, the created jar was empty and no sources
> had been compiled.
> project-layout
> pom.xml
> src
> main
> groovy
>MyClass.groovy
> After adding a dummy-file into src/main/resources, it works.
> Example output of mvn -o compile with version 3.0
> --
> [INFO] --- groovy-eclipse-compiler:2.7.0-01:add-groovy-build-paths
> (default-add-groovy-build-paths) @ myproject ---
> [INFO] Adding /src/main/groovy to the list of source folders
> [INFO] Adding /src/test/groovy to the list of test source folders
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> myproject ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory ./src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ myproject ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
>
> [INFO] BUILD SUCCESS
> Example output of mvn -o compile with version 2.5.1
> ---
> [INFO] --- groovy-eclipse-compiler:2.7.0-01:add-groovy-build-paths
> (default-add-groovy-build-paths) @ myproject ---
> [INFO] Adding /src/main/groovy to the list of source folders
> [INFO] Adding /src/test/groovy to the list of test source folders
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> myproject ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /Users/roman.stumm/projects/boxx-super/groovy-boxx/myproject/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ myproject
> ---
> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
> [INFO] Classpath:
> [INFO] All args: [-cp, reading and writing
> [11 .class files generated]
> [INFO] Compilation complete.
> The pom.xml
>
>3.0
> 2.7.0-01
> 2.0.4-04
>
> ...
>
>
>
> maven-compiler-plugin
> ${maven-compiler-version}
>
> 1.6
> 1.6
> groovy-eclipse-compiler
> true
>
>
>
> org.codehaus.groovy
> groovy-eclipse-compiler
> ${groovy-compiler-version}
>
>
> org.codehaus.groovy
> groovy-eclipse-batch
> ${groovy-eclipse-batch}
>
>
>
>
> org.codehaus.groovy
> groovy-eclipse-compiler
> ${groovy-compiler-version}
> true
>
>
> org.codehaus.groovy
> groovy-eclipse-batch
> ${groovy-eclipse-batch}
>
>
>
> ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-199) Plugin 3.0 does not compile src/main/groovy if neither src/main/java nor src/main/resources folders exist
[
https://jira.codehaus.org/browse/MCOMPILER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MCOMPILER-199:
---
Fix Version/s: 3.1
> Plugin 3.0 does not compile src/main/groovy if neither src/main/java nor
> src/main/resources folders exist
> -
>
> Key: MCOMPILER-199
> URL: https://jira.codehaus.org/browse/MCOMPILER-199
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.0
> Environment: mac os, jdk 1.6 and jdk 1.7, Apache Maven 3.0.3
> (r1075438; 2011-02-28 18:31:09+0100)
>Reporter: Roman Stumm
>Assignee: Olivier Lamy
> Fix For: 3.1
>
>
> The previous version 2.5.1 compiled the project that only had groovy-sources,
> but after switching to version 3.0, the created jar was empty and no sources
> had been compiled.
> project-layout
> pom.xml
> src
> main
> groovy
>MyClass.groovy
> After adding a dummy-file into src/main/resources, it works.
> Example output of mvn -o compile with version 3.0
> --
> [INFO] --- groovy-eclipse-compiler:2.7.0-01:add-groovy-build-paths
> (default-add-groovy-build-paths) @ myproject ---
> [INFO] Adding /src/main/groovy to the list of source folders
> [INFO] Adding /src/test/groovy to the list of test source folders
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> myproject ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory ./src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ myproject ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
>
> [INFO] BUILD SUCCESS
> Example output of mvn -o compile with version 2.5.1
> ---
> [INFO] --- groovy-eclipse-compiler:2.7.0-01:add-groovy-build-paths
> (default-add-groovy-build-paths) @ myproject ---
> [INFO] Adding /src/main/groovy to the list of source folders
> [INFO] Adding /src/test/groovy to the list of test source folders
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> myproject ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /Users/roman.stumm/projects/boxx-super/groovy-boxx/myproject/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ myproject
> ---
> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
> [INFO] Classpath:
> [INFO] All args: [-cp, reading and writing
> [11 .class files generated]
> [INFO] Compilation complete.
> The pom.xml
>
>3.0
> 2.7.0-01
> 2.0.4-04
>
> ...
>
>
>
> maven-compiler-plugin
> ${maven-compiler-version}
>
> 1.6
> 1.6
> groovy-eclipse-compiler
> true
>
>
>
> org.codehaus.groovy
> groovy-eclipse-compiler
> ${groovy-compiler-version}
>
>
> org.codehaus.groovy
> groovy-eclipse-batch
> ${groovy-eclipse-batch}
>
>
>
>
> org.codehaus.groovy
> groovy-eclipse-compiler
> ${groovy-compiler-version}
> true
>
>
> org.codehaus.groovy
> groovy-eclipse-batch
> ${groovy-eclipse-batch}
>
>
>
> ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-199) Plugin 3.0 does not compile src/main/groovy if neither src/main/java nor src/main/resources folders exist
[
https://jira.codehaus.org/browse/MCOMPILER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy reassigned MCOMPILER-199:
--
Assignee: Olivier Lamy
> Plugin 3.0 does not compile src/main/groovy if neither src/main/java nor
> src/main/resources folders exist
> -
>
> Key: MCOMPILER-199
> URL: https://jira.codehaus.org/browse/MCOMPILER-199
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.0
> Environment: mac os, jdk 1.6 and jdk 1.7, Apache Maven 3.0.3
> (r1075438; 2011-02-28 18:31:09+0100)
>Reporter: Roman Stumm
>Assignee: Olivier Lamy
>
> The previous version 2.5.1 compiled the project that only had groovy-sources,
> but after switching to version 3.0, the created jar was empty and no sources
> had been compiled.
> project-layout
> pom.xml
> src
> main
> groovy
>MyClass.groovy
> After adding a dummy-file into src/main/resources, it works.
> Example output of mvn -o compile with version 3.0
> --
> [INFO] --- groovy-eclipse-compiler:2.7.0-01:add-groovy-build-paths
> (default-add-groovy-build-paths) @ myproject ---
> [INFO] Adding /src/main/groovy to the list of source folders
> [INFO] Adding /src/test/groovy to the list of test source folders
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> myproject ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory ./src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ myproject ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
>
> [INFO] BUILD SUCCESS
> Example output of mvn -o compile with version 2.5.1
> ---
> [INFO] --- groovy-eclipse-compiler:2.7.0-01:add-groovy-build-paths
> (default-add-groovy-build-paths) @ myproject ---
> [INFO] Adding /src/main/groovy to the list of source folders
> [INFO] Adding /src/test/groovy to the list of test source folders
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> myproject ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /Users/roman.stumm/projects/boxx-super/groovy-boxx/myproject/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ myproject
> ---
> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
> [INFO] Classpath:
> [INFO] All args: [-cp, reading and writing
> [11 .class files generated]
> [INFO] Compilation complete.
> The pom.xml
>
>3.0
> 2.7.0-01
> 2.0.4-04
>
> ...
>
>
>
> maven-compiler-plugin
> ${maven-compiler-version}
>
> 1.6
> 1.6
> groovy-eclipse-compiler
> true
>
>
>
> org.codehaus.groovy
> groovy-eclipse-compiler
> ${groovy-compiler-version}
>
>
> org.codehaus.groovy
> groovy-eclipse-batch
> ${groovy-eclipse-batch}
>
>
>
>
> org.codehaus.groovy
> groovy-eclipse-compiler
> ${groovy-compiler-version}
> true
>
>
> org.codehaus.groovy
> groovy-eclipse-batch
> ${groovy-eclipse-batch}
>
>
>
> ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository root is not the working directory
[
https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317874#comment-317874
]
Robert Scholte commented on SCM-709:
SCM-686 broke it
> REGRESSION: git status doesn't work if repository root is not the working
> directory
> ---
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.8, 1.8.1
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result
> language independend.
> Without the {{--porcelain}} option files were listed relative to the working
> directory, but with {{--porcelain}} files are listed relative to the
> repository root. In most cases these are the same, but not always.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository root is not the working directory
[
https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317873#comment-317873
]
Andrei Pozolotin commented on SCM-709:
--
I just remembered that it worked fine with maven-release-plugin v 2.3.2 (and
whatever SCM dependency was there)
is there easy way to see what specific change to v 2.4 (and related SCM) broke
this?
> REGRESSION: git status doesn't work if repository root is not the working
> directory
> ---
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.8, 1.8.1
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result
> language independend.
> Without the {{--porcelain}} option files were listed relative to the working
> directory, but with {{--porcelain}} files are listed relative to the
> repository root. In most cases these are the same, but not always.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository root is not the working directory
[
https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317868#comment-317868
]
Robert Scholte commented on SCM-709:
@Andrei:
1. Although it looks like a hack, this will probably work. It's either knowing
the relative path between the workingdirectory and the repository root and
check the actual file, or get the information from the status-entries. Git
claims that the output of porcelain is consistent. After a chat with Mark we
decided to try this. We have several different CI systems to verify that this
works. I would expect that the status-entry would already have enough
information to decide if the file exists or not.
2. That was another idea, but I'm pretty sure that it will break the tests
right now.
3. Probably not. As a Windows user (probably the most critical OS in this case)
I can confirm that the GIT output is consistent and uses forward slashes.
4. Do we need to check if the file exists, if we better analyze the status
output
5. See 4
6. That was my question to Mark
7. how?
@Tim
Good point. AFAIK scm status expects all modified files inside (relative to?)
the working directory.
> REGRESSION: git status doesn't work if repository root is not the working
> directory
> ---
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.8, 1.8.1
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result
> language independend.
> Without the {{--porcelain}} option files were listed relative to the working
> directory, but with {{--porcelain}} files are listed relative to the
> repository root. In most cases these are the same, but not always.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (WAGON-381) Both Maven 2 and 3 fail to retrieve a that is larger than Integer.MAX_VALUE
[
https://jira.codehaus.org/browse/WAGON-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317860#comment-317860
]
Olivier Lamy commented on WAGON-381:
ok I just need to find a way how to test that.
As adding such huge file in the sources tree for unit test is impossible.
> Both Maven 2 and 3 fail to retrieve a that is larger than
> Integer.MAX_VALUE
>
>
> Key: WAGON-381
> URL: https://jira.codehaus.org/browse/WAGON-381
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.2
>Reporter: Evgeny Goldin
>Assignee: Olivier Lamy
> Fix For: 2.3
>
> Attachments: 1.png, 2.png
>
>
> We have a *{{*.tar}}* file stored in corporate Maven repository, its size is
> *{{2.5Gb}}*. Trying to bring it with Maven (both 2 and 3) causes file of
> *{{2147483647}}* size to be downloaded to local maven repo, which is exactly
> 231-1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (WAGON-381) Both Maven 2 and 3 fail to retrieve a that is larger than Integer.MAX_VALUE
[
https://jira.codehaus.org/browse/WAGON-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317858#comment-317858
]
Ben Douglas commented on WAGON-381:
---
No -- looking at the download information, it stopped downloading then checked
the checksum, it failed, so it retried the download, and kept trying and only
got as far at the ~1G each time, finally failing
> Both Maven 2 and 3 fail to retrieve a that is larger than
> Integer.MAX_VALUE
>
>
> Key: WAGON-381
> URL: https://jira.codehaus.org/browse/WAGON-381
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.2
>Reporter: Evgeny Goldin
>Assignee: Olivier Lamy
> Fix For: 2.3
>
> Attachments: 1.png, 2.png
>
>
> We have a *{{*.tar}}* file stored in corporate Maven repository, its size is
> *{{2.5Gb}}*. Trying to bring it with Maven (both 2 and 3) causes file of
> *{{2147483647}}* size to be downloaded to local maven repo, which is exactly
> 231-1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-197) dependencies no more at classpath
[ https://jira.codehaus.org/browse/MCOMPILER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317857#comment-317857 ] Romain manni-Bucau commented on MCOMPILER-197: -- weird, i have target/generated-sources/org/issue/Person_.java with 2.5.1 > dependencies no more at classpath > - > > Key: MCOMPILER-197 > URL: https://jira.codehaus.org/browse/MCOMPILER-197 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 3.0 >Reporter: Romain manni-Bucau > Attachments: compiler-test.zip > > > before (version 2.5.1) dependencies of compiler plugin were added to javac > classpath, now it seems (didn't check so maybe it is wrong) it is no more the > case > i attached a sample. Running "mvn compile" with version 2.5.1 you'll get a > file target/generated-sources/org/issue/Person_.java. With version 3.0 you > get a folder target/annotations and no more file. > This is really blocking for stuff like openjpa metamodel generation where > with version 3.0 it needs to use an ant task which is not so straight forward. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (WAGON-381) Both Maven 2 and 3 fail to retrieve a that is larger than Integer.MAX_VALUE
[
https://jira.codehaus.org/browse/WAGON-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317856#comment-317856
]
Olivier Lamy commented on WAGON-381:
only checksum fail but artifact is correctly downloaded ?
> Both Maven 2 and 3 fail to retrieve a that is larger than
> Integer.MAX_VALUE
>
>
> Key: WAGON-381
> URL: https://jira.codehaus.org/browse/WAGON-381
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.2
>Reporter: Evgeny Goldin
>Assignee: Olivier Lamy
> Fix For: 2.3
>
> Attachments: 1.png, 2.png
>
>
> We have a *{{*.tar}}* file stored in corporate Maven repository, its size is
> *{{2.5Gb}}*. Trying to bring it with Maven (both 2 and 3) causes file of
> *{{2147483647}}* size to be downloaded to local maven repo, which is exactly
> 231-1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-197) dependencies no more at classpath
[
https://jira.codehaus.org/browse/MCOMPILER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317855#comment-317855
]
Olivier Lamy commented on MCOMPILER-197:
@romain I'm confused :-)
I use your test project.
replace compiler version to 2.5.1
and still nothing in target/generated-sources
{code}
mbp-olamy:compiler-test olamy$ mvn clean verify
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building compiler-test 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ compiler-test ---
[INFO] Deleting /Users/olamy/tmp/compiler-test/target
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (generate-entity-metamodel) @
compiler-test ---
[WARNING] File encoding has not been set, using platform encoding MacRoman,
i.e. build is platform dependent!
[INFO] Compiling 1 source file to /Users/olamy/tmp/compiler-test/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
compiler-test ---
[WARNING] Using platform encoding (MacRoman actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @
compiler-test ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (compile) @ compiler-test ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
compiler-test ---
[WARNING] Using platform encoding (MacRoman actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/Users/olamy/tmp/compiler-test/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @
compiler-test ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ compiler-test ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ compiler-test ---
[INFO] Building jar:
/Users/olamy/tmp/compiler-test/target/compiler-test-1.0-SNAPSHOT.jar
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.136s
[INFO] Finished at: Wed Jan 23 15:34:08 CET 2013
[INFO] Final Memory: 11M/759M
[INFO]
mbp-olamy:compiler-test olamy$ ls -lrt target/generated-sources/
mbp-olamy:compiler-test olamy$
mbp-olamy:compiler-test olamy$ mvn -v
Apache Maven 3.1-SNAPSHOT (57d9c68e56a4bc8d825c7615534023eeda52b9c0; 2013-01-05
00:17:48+0100)
Maven home: /Users/olamy/softs/maven/trunk
Java version: 1.6.0_37, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: fr_FR, platform encoding: MacRoman
OS name: "mac os x", version: "10.8.2", arch: "x86_64", family: "mac"
{code}
> dependencies no more at classpath
> -
>
> Key: MCOMPILER-197
> URL: https://jira.codehaus.org/browse/MCOMPILER-197
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: Romain manni-Bucau
> Attachments: compiler-test.zip
>
>
> before (version 2.5.1) dependencies of compiler plugin were added to javac
> classpath, now it seems (didn't check so maybe it is wrong) it is no more the
> case
> i attached a sample. Running "mvn compile" with version 2.5.1 you'll get a
> file target/generated-sources/org/issue/Person_.java. With version 3.0 you
> get a folder target/annotations and no more file.
> This is really blocking for stuff like openjpa metamodel generation where
> with version 3.0 it needs to use an ant task which is not so straight forward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-138) No way to control the archiver
[
https://jira.codehaus.org/browse/MSHADE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MSHADE-138.
---
Resolution: Not A Bug
Fix Version/s: 2.0.1
I was wrong about the circumstances.
> No way to control the archiver
> --
>
> Key: MSHADE-138
> URL: https://jira.codehaus.org/browse/MSHADE-138
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
>Affects Versions: 1.7.1
>Reporter: Benson Margulies
>Assignee: Benson Margulies
> Fix For: 2.0.1
>
>
> The shade plugin produces jars, but lacks support for:
> {code:xml}
>
>false
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-197) dependencies no more at classpath
[ https://jira.codehaus.org/browse/MCOMPILER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317850#comment-317850 ] Romain manni-Bucau commented on MCOMPILER-197: -- Hi Olivier, with v2.5.1 it was generated. basically any java 6 processor is now skipped (there are workaround with other plugins but that's a regression) > dependencies no more at classpath > - > > Key: MCOMPILER-197 > URL: https://jira.codehaus.org/browse/MCOMPILER-197 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 3.0 >Reporter: Romain manni-Bucau > Attachments: compiler-test.zip > > > before (version 2.5.1) dependencies of compiler plugin were added to javac > classpath, now it seems (didn't check so maybe it is wrong) it is no more the > case > i attached a sample. Running "mvn compile" with version 2.5.1 you'll get a > file target/generated-sources/org/issue/Person_.java. With version 3.0 you > get a folder target/annotations and no more file. > This is really blocking for stuff like openjpa metamodel generation where > with version 3.0 it needs to use an ant task which is not so straight forward. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-197) dependencies no more at classpath
[ https://jira.codehaus.org/browse/MCOMPILER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317847#comment-317847 ] Olivier Lamy commented on MCOMPILER-197: @romain I miss you with the test project. There is no failure and nothing is generated in target/generated-sources (maybe a maven plugin call miss ?) How can I get the failure ? > dependencies no more at classpath > - > > Key: MCOMPILER-197 > URL: https://jira.codehaus.org/browse/MCOMPILER-197 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 3.0 >Reporter: Romain manni-Bucau > Attachments: compiler-test.zip > > > before (version 2.5.1) dependencies of compiler plugin were added to javac > classpath, now it seems (didn't check so maybe it is wrong) it is no more the > case > i attached a sample. Running "mvn compile" with version 2.5.1 you'll get a > file target/generated-sources/org/issue/Person_.java. With version 3.0 you > get a folder target/annotations and no more file. > This is really blocking for stuff like openjpa metamodel generation where > with version 3.0 it needs to use an ant task which is not so straight forward. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-138) No way to control the archiver
[
https://jira.codehaus.org/browse/MSHADE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies reassigned MSHADE-138:
---
Assignee: Benson Margulies
> No way to control the archiver
> --
>
> Key: MSHADE-138
> URL: https://jira.codehaus.org/browse/MSHADE-138
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
>Affects Versions: 1.7.1
>Reporter: Benson Margulies
>Assignee: Benson Margulies
>
> The shade plugin produces jars, but lacks support for:
> {code:xml}
>
>false
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-139) Change the default output file name so that it does not replace the ordinary jar
Benson Margulies created MSHADE-139: --- Summary: Change the default output file name so that it does not replace the ordinary jar Key: MSHADE-139 URL: https://jira.codehaus.org/browse/MSHADE-139 Project: Maven 2.x Shade Plugin Issue Type: Improvement Affects Versions: 2.0 Reporter: Benson Margulies See http://markmail.org/message/kqbvju36nusvydwt We could make incremental builds work righter by not overwriting the base jar by default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
