[jira] Created: (MSHADE-101) ApacheNoticeResourceTransformer NullPointerException for some licenses when no parameters set.
ApacheNoticeResourceTransformer NullPointerException for some licenses when no parameters set. -- Key: MSHADE-101 URL: https://jira.codehaus.org/browse/MSHADE-101 Project: Maven 2.x Shade Plugin Issue Type: Bug Affects Versions: 1.5 Reporter: Robert Burrell Donkin Attachments: ApacheNoticeResourceTransformer-NullPointerException.patch For some dependencies, ApacheNoticeResourceTransformer throws a NullPointerException when no parameters are set. Included in the patch are * an integration test case which demonstrates the problem, * a unit test case (including tests around this problem) and * my proposed (narrow) fix for ApacheNoticeResourceTransformer. ATM no parameter is mandatory. This may indicate an intention to support a basic use case without parameters. So this patch opts for a reasonable default. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MSHADE-100) [DOCS] Describe Available Resource Transformers
[ https://jira.codehaus.org/browse/MSHADE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272077#comment-272077 ] Benson Margulies edited comment on MSHADE-100 at 7/2/11 6:19 AM: - r1142008 | bimargulies | 2011-07-01 13:49:31 -0400 (Fri, 01 Jul 2011) | 4 lines [MSHADE-100]: [DOCS] Describe Available Resource Transformers Submitted by: Robert Burrell Donkin APT edits: add documentation on the provided transformer classes. was (Author: bmargulies): r1142008 | bimargulies | 2011-07-01 13:49:31 -0400 (Fri, 01 Jul 2011) | 2 lines [MSHADE-100]: (Robert Burrell Donkin): add documentation on the provided transformer classes. > [DOCS] Describe Available Resource Transformers > --- > > Key: MSHADE-100 > URL: https://jira.codehaus.org/browse/MSHADE-100 > Project: Maven 2.x Shade Plugin > Issue Type: Improvement >Affects Versions: 1.5 >Reporter: Robert Burrell Donkin >Assignee: Benson Margulies > Fix For: 1.5 > > Attachments: describe-resource-descriptors.patch > > > maven-shade-plugin includes many useful ResourceTransformer implementations. > This patch add descriptions for everyone that worked well for me (expect > patches with test cases later). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MSHADE-88) Pom type dependencies are incorrectly included in dependency reduced pom
[ https://jira.codehaus.org/browse/MSHADE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272056#comment-272056 ] Benson Margulies edited comment on MSHADE-88 at 7/2/11 6:18 AM: r1141937 | bimargulies | 2011-07-01 09:50:47 -0400 (Fri, 01 Jul 2011) | 5 lines [MSHADE-88]: Pom type dependencies are incorrectly included in dependency reduced pom Submitted by: antelder also integration test for antelder's change. Also update to current parent. was (Author: bmargulies): r1141937 | bimargulies | 2011-07-01 09:50:47 -0400 (Fri, 01 Jul 2011) | 3 lines [MSHADE-88]: antelder: fix an interaction between 'createDependencyReducedPom' and 'promoteTransitiveDependencies'. also integration test. Also update to current parent. /Users/benson/asf/mvn/plugins/maven-shade-plugin > Pom type dependencies are incorrectly included in dependency reduced pom > > > Key: MSHADE-88 > URL: https://jira.codehaus.org/browse/MSHADE-88 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.4 >Reporter: ant elder >Assignee: Benson Margulies > Fix For: 1.5 > > Attachments: drpFix.txt, MSHADE-88-2.patch > > > When shading with promoteTransitiveDependencies and > createDependencyReducedPom set to true and using dependencies with a type of > pom then the dependency reduced pom still includes the pom type dependencies, > this is incorrect because the dependencies of the pom type dependency have > already been included in the shaded artifact. > The attached patch (based on trunk) fixes this by not including pom type > dependencies to the dependency reduced pom. There are no existing tests for > dependency reduced pom's or with pom type dependencies but this patch code > does match what is already done for pom type dependencies in the ShadeMojo > execute method at line 409. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-101) ApacheNoticeResourceTransformer NullPointerException for some licenses when no parameters set.
[ https://jira.codehaus.org/browse/MSHADE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272127#comment-272127 ] Benson Margulies commented on MSHADE-101: - Robert, We don't check in files with personal copyrights at Apache. Since you have an ICLA on file, you have in general granted permission for your work to be incorporated with the standard notice. However, in an abundance of caution, I'm holding off committing the repaired notices until I hear from you that you did indeed intend to submit this under the terms of your icla with Apache. > ApacheNoticeResourceTransformer NullPointerException for some licenses when > no parameters set. > -- > > Key: MSHADE-101 > URL: https://jira.codehaus.org/browse/MSHADE-101 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.5 >Reporter: Robert Burrell Donkin > Attachments: > ApacheNoticeResourceTransformer-NullPointerException.patch > > > For some dependencies, ApacheNoticeResourceTransformer throws a > NullPointerException when no parameters are set. > Included in the patch are > * an integration test case which demonstrates the problem, > * a unit test case (including tests around this problem) and > * my proposed (narrow) fix for ApacheNoticeResourceTransformer. > ATM no parameter is mandatory. This may indicate an intention to support a > basic use case without parameters. So this patch opts for a reasonable > default. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MSHADE-101) ApacheNoticeResourceTransformer NullPointerException for some licenses when no parameters set.
[ https://jira.codehaus.org/browse/MSHADE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272127#comment-272127 ] Benson Margulies edited comment on MSHADE-101 at 7/2/11 6:27 AM: - Robert, We don't check in files with personal copyrights at Apache. Since you have an ICLA on file, you have in general granted permission for your work to be incorporated with the standard notice. And you did use a standard notice on the java file, just not on the POM. So I'm going to go ahead and fix the notice and commit. If this is a problem we'll cope. was (Author: bmargulies): Robert, We don't check in files with personal copyrights at Apache. Since you have an ICLA on file, you have in general granted permission for your work to be incorporated with the standard notice. However, in an abundance of caution, I'm holding off committing the repaired notices until I hear from you that you did indeed intend to submit this under the terms of your icla with Apache. > ApacheNoticeResourceTransformer NullPointerException for some licenses when > no parameters set. > -- > > Key: MSHADE-101 > URL: https://jira.codehaus.org/browse/MSHADE-101 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.5 >Reporter: Robert Burrell Donkin >Assignee: Benson Margulies > Attachments: > ApacheNoticeResourceTransformer-NullPointerException.patch > > > For some dependencies, ApacheNoticeResourceTransformer throws a > NullPointerException when no parameters are set. > Included in the patch are > * an integration test case which demonstrates the problem, > * a unit test case (including tests around this problem) and > * my proposed (narrow) fix for ApacheNoticeResourceTransformer. > ATM no parameter is mandatory. This may indicate an intention to support a > basic use case without parameters. So this patch opts for a reasonable > default. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-140) Performance degredation
[
https://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272148#comment-272148
]
Erez Mazor commented on MJAR-140:
-
Any updates on this issue?
> Performance degredation
>
>
> Key: MJAR-140
> URL: https://jira.codehaus.org/browse/MJAR-140
> Project: Maven 2.x JAR Plugin
> Issue Type: Bug
>Affects Versions: 2.3, 2.3.1
>Reporter: Eran Harel
>
> I migrated maven to version 3.0.1 in order to utilize the parallel build
> experimental feature.
> As a result I get the following warning:
> {code}
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that are not marked as *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in DataBuilder:
> [WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
> [WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
> [WARNING] *
> {code}
> I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
> message is gone, but now the builds take much longer: minutes added!!!
> The build takes about x 1.5 longer now.
> I also compared the maven 3 parallel build time with the new jar-plugin VS a
> serial build with the old 2.2 plugin version I had. The results are that
> same, while when using the parallel build with the 2.2 plugin I see a
> significant ~30% performance boost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-140) Performance degredation
[
https://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272150#comment-272150
]
Kristian Rosenvold commented on MJAR-140:
-
Yes, but it's not a simple answer.
The update to PlexusIoResourceCollection was done to achieve file attribute
correctness. So the incorrect behaviour was fast but the correct behaviour is
slower.
But all is not entirely lost. I have published pleus-archiver 2.0, plexus-io
2.0 and plexus-utils 3.0. If you add all of these to your plugin dependencies
you will get an improvement in performance. To get back to the "original" speed
you will actually have to use java 1.7. plexus-io 2.0 supports native file
attributes through the java 1.7 api's. So with java 1.7 you should see little
or no difference in performance from 2.2. For java 1.5/1.6, plexus-io 2.0 now
forks the two "ls" forks in parallel, which should help some on the observed
slowdown.
The slowdown affects all posix compliant systems.
> Performance degredation
>
>
> Key: MJAR-140
> URL: https://jira.codehaus.org/browse/MJAR-140
> Project: Maven 2.x JAR Plugin
> Issue Type: Bug
>Affects Versions: 2.3, 2.3.1
>Reporter: Eran Harel
>
> I migrated maven to version 3.0.1 in order to utilize the parallel build
> experimental feature.
> As a result I get the following warning:
> {code}
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that are not marked as *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in DataBuilder:
> [WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
> [WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
> [WARNING] *
> {code}
> I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
> message is gone, but now the builds take much longer: minutes added!!!
> The build takes about x 1.5 longer now.
> I also compared the maven 3 parallel build time with the new jar-plugin VS a
> serial build with the old 2.2 plugin version I had. The results are that
> same, while when using the parallel build with the 2.2 plugin I see a
> significant ~30% performance boost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-21) share run-its profile with common invoker plugin configuration
share run-its profile with common invoker plugin configuration -- Key: MPOM-21 URL: https://issues.apache.org/jira/browse/MPOM-21 Project: Maven POMs Issue Type: Wish Components: maven-plugins Affects Versions: MAVEN-PLUGINS-21 Reporter: Hervé Boutemy configuration of invoker plugin is the same for majority if not all plugins moving this configuration to parent POM will make documentation and management easier -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSHADE-101) ApacheNoticeResourceTransformer NullPointerException for some licenses when no parameters set.
[ https://jira.codehaus.org/browse/MSHADE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MSHADE-101: Affects Version/s: (was: 1.5) 1.4 Fix Version/s: 1.5 > ApacheNoticeResourceTransformer NullPointerException for some licenses when > no parameters set. > -- > > Key: MSHADE-101 > URL: https://jira.codehaus.org/browse/MSHADE-101 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.4 >Reporter: Robert Burrell Donkin >Assignee: Benson Margulies > Fix For: 1.5 > > Attachments: > ApacheNoticeResourceTransformer-NullPointerException.patch > > > For some dependencies, ApacheNoticeResourceTransformer throws a > NullPointerException when no parameters are set. > Included in the patch are > * an integration test case which demonstrates the problem, > * a unit test case (including tests around this problem) and > * my proposed (narrow) fix for ApacheNoticeResourceTransformer. > ATM no parameter is mandatory. This may indicate an intention to support a > basic use case without parameters. So this patch opts for a reasonable > default. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSHADE-101) ApacheNoticeResourceTransformer NullPointerException for some licenses when no parameters set.
[ https://jira.codehaus.org/browse/MSHADE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MSHADE-101. --- Resolution: Fixed r1142204 | bimargulies | 2011-07-02 07:29:03 -0400 (Sat, 02 Jul 2011) | 3 lines [MSHADE-101] ApacheNoticeResourceTransformer NullPointerException for some licenses when no parameters set. Submitted by: Robert Robert Burrell Donkin > ApacheNoticeResourceTransformer NullPointerException for some licenses when > no parameters set. > -- > > Key: MSHADE-101 > URL: https://jira.codehaus.org/browse/MSHADE-101 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.4 >Reporter: Robert Burrell Donkin >Assignee: Benson Margulies > Fix For: 1.5 > > Attachments: > ApacheNoticeResourceTransformer-NullPointerException.patch > > > For some dependencies, ApacheNoticeResourceTransformer throws a > NullPointerException when no parameters are set. > Included in the patch are > * an integration test case which demonstrates the problem, > * a unit test case (including tests around this problem) and > * my proposed (narrow) fix for ApacheNoticeResourceTransformer. > ATM no parameter is mandatory. This may indicate an intention to support a > basic use case without parameters. So this patch opts for a reasonable > default. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-98) minimizeJar option excludes package-info classes
[ https://jira.codehaus.org/browse/MSHADE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272156#comment-272156 ] Benson Margulies commented on MSHADE-98: I've written an integration test for this; in the future, please consider providing tests with your patches. > minimizeJar option excludes package-info classes > > > Key: MSHADE-98 > URL: https://jira.codehaus.org/browse/MSHADE-98 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.4 >Reporter: Jared Bunting >Assignee: Benson Margulies > Attachments: packageinfo.patch, packageinfo.patch > > > Basically, minimizeJar will never include package-info classes for any > dependencies. It should. I am attaching a patch to include any package-info > class files for any packages that contain included classes, or contain > subpackages that contain included classes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSHADE-98) minimizeJar option excludes package-info classes
[ https://jira.codehaus.org/browse/MSHADE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MSHADE-98. -- Resolution: Fixed Fix Version/s: 1.5 r1142261 | bimargulies | 2011-07-02 14:50:17 -0400 (Sat, 02 Jul 2011) | 7 lines [MSHADE-98] minimizeJar option excludes package-info classes Submitted by: Jared Bunting o Base patch from Jared as attached to JIRA. o integration test (maven-shade-plugin/src/it/mini-jar-package-info) by committer. > minimizeJar option excludes package-info classes > > > Key: MSHADE-98 > URL: https://jira.codehaus.org/browse/MSHADE-98 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.4 >Reporter: Jared Bunting >Assignee: Benson Margulies > Fix For: 1.5 > > Attachments: packageinfo.patch, packageinfo.patch > > > Basically, minimizeJar will never include package-info classes for any > dependencies. It should. I am attaching a patch to include any package-info > class files for any packages that contain included classes, or contain > subpackages that contain included classes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-97) Add the ability to specify "entry points" for minimizeJar
[ https://jira.codehaus.org/browse/MSHADE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272158#comment-272158 ] Benson Margulies commented on MSHADE-97: Could I interest you in adding a test? > Add the ability to specify "entry points" for minimizeJar > -- > > Key: MSHADE-97 > URL: https://jira.codehaus.org/browse/MSHADE-97 > Project: Maven 2.x Shade Plugin > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Jared Bunting > Attachments: entrypoints.patch, entrypoints.patch > > > Currently, the "minimizeJar" option assumes that you want to include all > classes in the current project and those that they depend on. Sometimes, > classes are accessed via reflection, or some other means, and therefore don't > get included. The ability to specify additional entry points (as classes) to > this dependency tree would be useful. > I have added this as a patch that I am attaching. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-95) test-scoped artifact excluded, even if it is also a transitive dep
[
https://jira.codehaus.org/browse/MSHADE-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272159#comment-272159
]
Benson Margulies commented on MSHADE-95:
Any sign of that test case?
> test-scoped artifact excluded, even if it is also a transitive dep
> --
>
> Key: MSHADE-95
> URL: https://jira.codehaus.org/browse/MSHADE-95
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
>Affects Versions: 1.3.2, 1.4
> Environment: (cygwin)
> Apache Maven 3.0.1 (r1038046; 2010-11-23 05:58:32-0500)
> Java version: 1.6.0_23
> Java home: C:\Program Files\Java\jdk1.6.0_23\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
>Reporter: Alan D. Salewski
>
> A test-scoped artifact is excluded from the final jar, even if that artifact
> is also a transitive dependency of some other (non-test-scoped) dep.
> {noformat}
> MY_POM
> |
> |
> +-- dep A (scope: test)
> |
> |
> +-- dep B (scope: compile)
> |
> |
> +-- dep A (scope: compile)
> {noformat}
> In the above scenario, I would expect '{{dep A}}' to be included in the final
> jar, even though it's in the '{{test}}' scope in my POM. The rationale is
> that it is required for '{{dep B}}' to run; its absence will result in a
> {{java.lang.ClassNotFoundException}} at runtime.
> Behavior observed with maven-shade-plugin versions 1.3.2 and 1.4; other
> versions not tested.
> I'll put together a test case later tonight when I have more time and attach
> it here.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-91) Allow failing of build if overlapping classes are detected
[
https://jira.codehaus.org/browse/MSHADE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272160#comment-272160
]
Benson Margulies commented on MSHADE-91:
How about an integration test to go with this?
> Allow failing of build if overlapping classes are detected
> --
>
> Key: MSHADE-91
> URL: https://jira.codehaus.org/browse/MSHADE-91
> Project: Maven 2.x Shade Plugin
> Issue Type: New Feature
>Affects Versions: 1.4
> Environment: N/A
>Reporter: Andrew Swan
> Attachments: MSHADE-91.patch
>
>
> Currently if multiple shaded artifacts contain the same fully-qualified class
> name, the plugin issues a warning on the console like this:
> {code}[WARNING] We have a duplicate foo.bar.Baz.class in
> {code}
> In many cases such duplicates are a serious problem, e.g. when they are not
> the same version of that class.
> It would therefore be useful if the plugin (specifically the DefaultShader
> class) provided the option of failing the build if any duplicates are
> detected. This would be particularly useful in a continuous integration
> environment where there's no human operator to check the console output for
> warnings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSHADE-89) Allow including dependencies of scope:provided
[
https://jira.codehaus.org/browse/MSHADE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MSHADE-89.
--
Resolution: Not A Bug
Assignee: Benson Margulies
This should be discussed on the mailing list as a question, and then perhaps a
JIRA would make sense.
> Allow including dependencies of scope:provided
> --
>
> Key: MSHADE-89
> URL: https://jira.codehaus.org/browse/MSHADE-89
> Project: Maven 2.x Shade Plugin
> Issue Type: Wish
>Affects Versions: 1.4
>Reporter: Grégory Joseph
>Assignee: Benson Margulies
>
> I have a project for which I'd like to create a shaded jar.
> It has a bunch of dependencies in scope:provided, because they really are, in
> the normal use-case of this artifact; it's meant to be deployed as a plugin
> in another app, so, for example, {{myapp-api}} really is "provided".
> The project's assembly depends on these deps to be scope:provided (so they're
> not included in the assembly)
> If a webapp project is made and depends on this project, the scope:provided
> also helps avoiding duplicated dependencies in some cases.
> .. but yes, this project now also needs a standalone/executable jar; some of
> the "provided" dependencies are needed at runtime for this. As far as I can
> tell, the shade plugin currently does not propose any solution for this.
> Is there any way this could be considered for the plugin ? Or am I looking at
> it the wrong way ? I suppose I could split my project and have 2 modules, one
> simply being the standalone/shaded version of the other, but it seems
> overkill, since they're really the same source.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSHADE-86) dependencies of excluded dependencies are included
[ https://jira.codehaus.org/browse/MSHADE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MSHADE-86. -- Resolution: Not A Bug I don't have time to chase this. > dependencies of excluded dependencies are included > -- > > Key: MSHADE-86 > URL: https://jira.codehaus.org/browse/MSHADE-86 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.4 >Reporter: Benson Margulies > > Please let me know if you need a test case here. > Pom has two executions of shade on separate classifiers. One of them uses > excludes to leave some things out. Final jar includes contents of a slew of > other artifacts. Dependency:tree shows those artifacts as being dependencies > of the excluded artifacts, not the included ones. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSHADE-93) Dependency problem in jdependency pom causes failure to download commons-io in Artifactory
[ https://jira.codehaus.org/browse/MSHADE-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MSHADE-93. -- Resolution: Fixed Fix Version/s: 1.5 r1142269 | bimargulies | 2011-07-02 15:08:33 -0400 (Sat, 02 Jul 2011) | 4 lines [MSHADE-93] Dependency problem in jdependency pom causes failure to download commons-io in Artifactory o Made suggested change. > Dependency problem in jdependency pom causes failure to download commons-io > in Artifactory > -- > > Key: MSHADE-93 > URL: https://jira.codehaus.org/browse/MSHADE-93 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.4 >Reporter: Michael Smith >Assignee: Benson Margulies >Priority: Minor > Fix For: 1.5 > > > Fixed in jdependency 0.7. Please bump jdependency version from 0.6 to 0.7. > https://github.com/tcurdt/jdependency/issues/closed#issue/1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-22) configure maven-site-plugin version for Maven 3
configure maven-site-plugin version for Maven 3 --- Key: MPOM-22 URL: https://issues.apache.org/jira/browse/MPOM-22 Project: Maven POMs Issue Type: Improvement Components: asf Affects Versions: ASF-9 Reporter: Hervé Boutemy Assignee: Hervé Boutemy maven-site-plugin 2.3 does not really work with Maven 3 even if maven-site-plugin 3.0-beta-3 is only beta, it's better than 2.3 when run under Maven 3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Deleted] (MPOM-22) configure maven-site-plugin version for Maven 3
[ https://issues.apache.org/jira/browse/MPOM-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy deleted MPOM-22: -- > configure maven-site-plugin version for Maven 3 > --- > > Key: MPOM-22 > URL: https://issues.apache.org/jira/browse/MPOM-22 > Project: Maven POMs > Issue Type: Improvement >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > > maven-site-plugin 2.3 does not really work with Maven 3 > even if maven-site-plugin 3.0-beta-3 is only beta, it's better than 2.3 when > run under Maven 3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5108) Useful information on property inheritance control is not in the pom doc
[ https://jira.codehaus.org/browse/MNG-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272166#comment-272166 ] Herve Boutemy commented on MNG-5108: Author: hboutemy Date: Sat Jul 2 14:28:18 2011 New Revision: 1142230 URL: http://svn.apache.org/viewvc?rev=1142230&view=rev > Useful information on property inheritance control is not in the pom doc > > > Key: MNG-5108 > URL: https://jira.codehaus.org/browse/MNG-5108 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.0.3 >Reporter: Benson Margulies >Assignee: Benson Margulies > > This handy page at sonatype contains data that, I submit, should be part of > the core maven pom reference documentation. > http://www.sonatype.com/people/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-97) Add the ability to specify "entry points" for minimizeJar
[ https://jira.codehaus.org/browse/MSHADE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272167#comment-272167 ] Jared Bunting commented on MSHADE-97: - I'd be happy to, but it may take a day or two. > Add the ability to specify "entry points" for minimizeJar > -- > > Key: MSHADE-97 > URL: https://jira.codehaus.org/browse/MSHADE-97 > Project: Maven 2.x Shade Plugin > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Jared Bunting > Attachments: entrypoints.patch, entrypoints.patch > > > Currently, the "minimizeJar" option assumes that you want to include all > classes in the current project and those that they depend on. Sometimes, > classes are accessed via reflection, or some other means, and therefore don't > get included. The ability to specify additional entry points (as classes) to > this dependency tree would be useful. > I have added this as a patch that I am attaching. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-560) make maven-site-plugin 3.x work both with Maven 2.2 and Maven 3.x
[ https://jira.codehaus.org/browse/MSITE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSITE-560. --- Resolution: Fixed it's working now > make maven-site-plugin 3.x work both with Maven 2.2 and Maven 3.x > - > > Key: MSITE-560 > URL: https://jira.codehaus.org/browse/MSITE-560 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Improvement > Components: Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.0-beta-4 > > > maintaining 2 branches in parallel is not easy, and mojo and reporting code > is exactly the same: there are not so much differences -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-690) create project-specific formatter settings
create project-specific formatter settings -- Key: MECLIPSE-690 URL: https://jira.codehaus.org/browse/MECLIPSE-690 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: Core : Workspace settings Affects Versions: 2.8 Reporter: James Ring Priority: Minor If you specify workspaceCodeStylesURL, maven-eclipse-plugin will set Eclipse's default formatter to the given formatter. However, this really should only be a project-specific setting (there may be other projects with different format rules in the same workspace). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (WAGON-337) invalid md5/sha1 checksum on deploy phase
invalid md5/sha1 checksum on deploy phase - Key: WAGON-337 URL: https://jira.codehaus.org/browse/WAGON-337 Project: Maven Wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-7 Environment: Windows7 64bit JDK1.6.0_22 apache-maven-2.2.1 Reporter: Watanabe Attachments: dummy-0.0.1.jar, dummy-0.0.1.jar.md5, dummy.zip Hi. I tried "mvn clean deploy" to my web-dav server with jackrabbit 1.0-beta-6 and 7. Package and deploy is correct. But the *.jar.md5 and *.jar.sha1 file has invalid value! So, I tried to version down to jackrabbit 1.0-beta-5, I got expected behavior. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
