[
https://issues.apache.org/jira/browse/MJAR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957246#comment-17957246
]
Matthias Bünger commented on MJAR-168:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-jar-plugin#332|https://github.com/apache/maven-jar-plugin/issues/332].
> Update to latest plexus-archiver
> --------------------------------
>
> Key: MJAR-168
> URL: https://issues.apache.org/jira/browse/MJAR-168
> Project: Maven JAR Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 2.4
> Environment: Any Unix system that has some ldap groups
> Reporter: Osvaldo Pinali Doederlein
> Assignee: Karl Heinz Marbaise
> Priority: Major
> Fix For: 2.5
>
>
> maven-jar-plugin regresses horribly with JDK 7 compared to JDK 6. The cause
> is well known and already fixed in plexus-io, PLXCOMP-203, but the fixed
> version of plexus-io has yet to be used by maven-jar-plugin. Here's some
> benchmark from y project:
> Standard build with maven 3.0.x or 3.1-alpha1:
> [INFO] Total time: 3:03.048s
> [INFO] Finished at: Tue Jul 09 15:22:02 EDT 2013
> [INFO] Final Memory: 40M/221M
> After rebuilding maven-jar-plugin, changing its POM to use plexus-archiver
> 2.4.1 (which in turn uses the latest plexus-io):
> [INFO] Total time: 41.786s
> [INFO] Finished at: Tue Jul 09 15:28:26 EDT 2013
> [INFO] Final Memory: 47M/403M
> It seems like a trivial fix, all maven-jar unit tests pass.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
