[jira] (MPIR-251) Artifact ###### has no file error regression.
[
https://jira.codehaus.org/browse/MPIR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314461#comment-314461
]
Fred Cooke commented on MPIR-251:
-
I also get this with Maven 3.0.4, maven-project-info-reports-plugin 2.6 and
oracle artifacts in the dependency tree. Additionally, I noticed that my CPU
usage went low for a while while Dependencies report just hung waiting for
something. Through the rest of the build it hogged a core (which is fine). If I
can help by testing snapshots of the plugin, I'll gladly do so.
> Artifact ## has no file error regression.
> -
>
> Key: MPIR-251
> URL: https://jira.codehaus.org/browse/MPIR-251
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.5
>Reporter: Ian Brandt
>Priority: Minor
> Attachments: pom.xml
>
>
> It appears that MPIR-158 has regressed. I'm seeing the same exact issue in
> 2.5 with Maven 3.0.4:
> {noformat}
> [INFO] Generating "Dependencies" report---
> maven-project-info-reports-plugin:2.5
> [ERROR] Artifact: com.sun:tools:jar:1.5.0 has no file.
> [ERROR] Artifact: com.thoughtworks.xstream:xstream:jar:1.3 has no file.
> [ERROR] Artifact: commons-beanutils:commons-beanutils:jar:1.8.0 has no file.
> [ERROR] Artifact: commons-cli:commons-cli:jar:1.1 has no file.
> [ERROR] Artifact: commons-codec:commons-codec:jar:1.3 has no file.
> [ERROR] Artifact: commons-collections:commons-collections:jar:3.2.1 has no
> file.
> [ERROR] Artifact: commons-digester:commons-digester:jar:2.0 has no file.
> [ERROR] Artifact: commons-fileupload:commons-fileupload:jar:1.2.2 has no file.
> ...{noformat}
--
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-503) create a native Java GIT provider using JGit
[ https://jira.codehaus.org/browse/SCM-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314475#comment-314475 ] Frank commented on SCM-503: --- According to http://eclipse.org/jgit/download/ jgit is available in the eclipse maven repository. Can the work proceed now? > create a native Java GIT provider using JGit > > > Key: SCM-503 > URL: https://jira.codehaus.org/browse/SCM-503 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.x > > > JGit is a BSD implementation of GIT in pure Java. > maven-scm-provider-jgit makes use of JGit so we have a Java only stack which > will be a great help on non POSIX conform platforms. -- 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-503) create a native Java GIT provider using JGit
[ https://jira.codehaus.org/browse/SCM-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314477#comment-314477 ] Olivier Lamy commented on SCM-503: -- some has been started here: http://code.google.com/a/apache-extras.org/p/maven-scm-provider-jgit/ If you want to help feel free to provide patches etc... > create a native Java GIT provider using JGit > > > Key: SCM-503 > URL: https://jira.codehaus.org/browse/SCM-503 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.x > > > JGit is a BSD implementation of GIT in pure Java. > maven-scm-provider-jgit makes use of JGit so we have a Java only stack which > will be a great help on non POSIX conform platforms. -- 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] (MDEP-391) Unpack fails on linux with large archives
Benoit Montuelle created MDEP-391: - Summary: Unpack fails on linux with large archives Key: MDEP-391 URL: https://jira.codehaus.org/browse/MDEP-391 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: unpack Affects Versions: 2.6 Environment: Ubuntu 10.04 LTS Reporter: Benoit Montuelle When unpacking "large " archives with numerous files (more than 1024 on this os) I got the following error trace [INFO] Expanding /var/lib/deploy/.m2/repository/com/aprilwaf/wafservice/ihm-packaging-ecg/3.9-finsouscription-SNAPSHOT/ihm-packaging-ecg-3.9-finsouscription-SNAPSHOT-distribution-php.tar.gz to /tmp/tmp5620480517649479513.tar [INFO] Expanding: /tmp/tmp5620480517649479513.tar into /var/lib/deploy/build-deploy/ecg/target/classes org.codehaus.plexus.archiver.ArchiverException: Error while executing chmod. at org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:64) at org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFile(AbstractZipUnArchiver.java:236) at org.codehaus.plexus.archiver.tar.TarUnArchiver.execute(TarUnArchiver.java:92) at org.codehaus.plexus.archiver.tar.TarGZipUnArchiver.execute(TarGZipUnArchiver.java:76) at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:108) at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:122) at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:95) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while executing process. at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:652) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:102) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:89) at org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:45) ... 26 more Caused by: java.io.IOException: Cannot run program "/bin/sh" (in directory "/var/lib/deploy/build-deploy/ecg/target/classes/symfony-1.4/lib/plugins/sfDoctrinePlugin/test/unit/record"): java.io.IOException: error=24, Too many open files at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) at java.lang.Runtime.exec(Runtime.java:593) at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:647) ... 29 more Caused by: java.io.IOException: java.io.IOException: error=24, Too many open files at java.lang.UNIXProcess.(UNIXProcess.java:148) at java.lang.ProcessImpl.start(ProcessImpl.java:65) at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) ... 31 more This error reproduce on every server tested, we already override linux file pointer limitations for our developers systems but can't do this in these servers. I guess 1024+ file pointers open to extract is not a good solution. Btw I noticed t
[jira] (MRELEASE-805) CLONE - scm:cvs dosn't take global .cvsignore from user home dir
Robert Scholte created MRELEASE-805: --- Summary: CLONE - scm:cvs dosn't take global .cvsignore from user home dir Key: MRELEASE-805 URL: https://jira.codehaus.org/browse/MRELEASE-805 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare, prepare-with-pom, scm Affects Versions: 2.3.2 Environment: Win7 x64, mvn 3.0.4 Reporter: Robert Scholte Priority: Critical As in title, then running prepare or prepare-with-pom on project with cvs as scm ,phase 'scm-check-modifications' fails with 'Cannot prepare the release because you have local modifications' showing that I've uncommitted files *.iml (Idea modules files) although I have *.iml in global .cvsignore file in my user home dir. I don't want to configure *.iml in every project whats why I have it in global .cvsignore. -- 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-701) CLONE - scm:cvs dosn't take global .cvsignore from user home dir
[ https://jira.codehaus.org/browse/SCM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte moved MRELEASE-805 to SCM-701: - Complexity: Intermediate Component/s: (was: prepare-with-pom) (was: prepare) (was: scm) maven-scm-provider-cvs Affects Version/s: (was: 2.3.2) 1.8.1 Key: SCM-701 (was: MRELEASE-805) Project: Maven SCM (was: Maven 2.x Release Plugin) > CLONE - scm:cvs dosn't take global .cvsignore from user home dir > > > Key: SCM-701 > URL: https://jira.codehaus.org/browse/SCM-701 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-cvs >Affects Versions: 1.8.1 > Environment: Win7 x64, mvn 3.0.4 >Reporter: Robert Scholte >Priority: Critical > > As in title, then running prepare or prepare-with-pom on project with cvs as > scm ,phase 'scm-check-modifications' fails with 'Cannot prepare the release > because you have local modifications' showing that I've uncommitted files > *.iml (Idea modules files) although I have *.iml in global .cvsignore file in > my user home dir. I don't want to configure *.iml in every project whats why > I have it in global .cvsignore. -- 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-701) scm:cvs dosn't take global .cvsignore from user home dir
[ https://jira.codehaus.org/browse/SCM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-701: --- Summary: scm:cvs dosn't take global .cvsignore from user home dir (was: CLONE - scm:cvs dosn't take global .cvsignore from user home dir) > scm:cvs dosn't take global .cvsignore from user home dir > > > Key: SCM-701 > URL: https://jira.codehaus.org/browse/SCM-701 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-cvs >Affects Versions: 1.8.1 > Environment: Win7 x64, mvn 3.0.4 >Reporter: Robert Scholte >Priority: Critical > > As in title, then running prepare or prepare-with-pom on project with cvs as > scm ,phase 'scm-check-modifications' fails with 'Cannot prepare the release > because you have local modifications' showing that I've uncommitted files > *.iml (Idea modules files) although I have *.iml in global .cvsignore file in > my user home dir. I don't want to configure *.iml in every project whats why > I have it in global .cvsignore. -- 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] (MDEP-391) Unpack fails on linux with large archives
[ https://jira.codehaus.org/browse/MDEP-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314502#comment-314502 ] Kristian Rosenvold commented on MDEP-391: - Can you use lsof -p to get some indication of what files are being leaked ? Please attach the dump here (anonymize if necessary or send me directly if not possible to anonymize) Also, the stack trace seems to indicate we may have a bug wrt the "useJvmChmod" flag of the plugin, can you try setting it to an explicit "true" value and see if that helps ? > Unpack fails on linux with large archives > - > > Key: MDEP-391 > URL: https://jira.codehaus.org/browse/MDEP-391 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: unpack >Affects Versions: 2.6 > Environment: Ubuntu 10.04 LTS >Reporter: Benoit Montuelle > > When unpacking "large " archives with numerous files (more than 1024 on this > os) I got the following error trace > [INFO] Expanding > /var/lib/deploy/.m2/repository/com/aprilwaf/wafservice/ihm-packaging-ecg/3.9-finsouscription-SNAPSHOT/ihm-packaging-ecg-3.9-finsouscription-SNAPSHOT-distribution-php.tar.gz > to /tmp/tmp5620480517649479513.tar > [INFO] Expanding: /tmp/tmp5620480517649479513.tar into > /var/lib/deploy/build-deploy/ecg/target/classes > org.codehaus.plexus.archiver.ArchiverException: Error while executing chmod. > at > org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:64) > at > org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFile(AbstractZipUnArchiver.java:236) > at > org.codehaus.plexus.archiver.tar.TarUnArchiver.execute(TarUnArchiver.java:92) > at > org.codehaus.plexus.archiver.tar.TarGZipUnArchiver.execute(TarGZipUnArchiver.java:76) > at > org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:108) > at > org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) > at > org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:122) > at > org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:95) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while > executing process. > at > org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:652) > at > org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:102) > at > org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:89) > at > org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:45) > ... 26 more > Caused by: java.io.IOException: Cannot run program "/bin/sh" (in directory > "/var/lib/deploy/build-deploy/ecg/target/classes/symfony-1.4/lib/plugins/sfDoctrinePlugin/test/unit/record"): > java.io.IOException: error=24, Too many open files > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at java.lang.Runtime.exec(R
[jira] (MDEP-391) Unpack fails on linux with large archives
[ https://jira.codehaus.org/browse/MDEP-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314511#comment-314511 ] Olivier Lamy commented on MDEP-391: --- http://svn.apache.org/r1414445 use plexus-archiver with useJvmChmod on per default. try with dependency plugin 2.7-SNAPSHOT > Unpack fails on linux with large archives > - > > Key: MDEP-391 > URL: https://jira.codehaus.org/browse/MDEP-391 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: unpack >Affects Versions: 2.6 > Environment: Ubuntu 10.04 LTS >Reporter: Benoit Montuelle > > When unpacking "large " archives with numerous files (more than 1024 on this > os) I got the following error trace > [INFO] Expanding > /var/lib/deploy/.m2/repository/com/aprilwaf/wafservice/ihm-packaging-ecg/3.9-finsouscription-SNAPSHOT/ihm-packaging-ecg-3.9-finsouscription-SNAPSHOT-distribution-php.tar.gz > to /tmp/tmp5620480517649479513.tar > [INFO] Expanding: /tmp/tmp5620480517649479513.tar into > /var/lib/deploy/build-deploy/ecg/target/classes > org.codehaus.plexus.archiver.ArchiverException: Error while executing chmod. > at > org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:64) > at > org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFile(AbstractZipUnArchiver.java:236) > at > org.codehaus.plexus.archiver.tar.TarUnArchiver.execute(TarUnArchiver.java:92) > at > org.codehaus.plexus.archiver.tar.TarGZipUnArchiver.execute(TarGZipUnArchiver.java:76) > at > org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:108) > at > org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) > at > org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:122) > at > org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:95) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while > executing process. > at > org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:652) > at > org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:102) > at > org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:89) > at > org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:45) > ... 26 more > Caused by: java.io.IOException: Cannot run program "/bin/sh" (in directory > "/var/lib/deploy/build-deploy/ecg/target/classes/symfony-1.4/lib/plugins/sfDoctrinePlugin/test/unit/record"): > java.io.IOException: error=24, Too many open files > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at java.lang.Runtime.exec(Runtime.java:593) > at > org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:647) > ... 29 more > Caused by: java.io.IOException: java.io.IOException: error=24, Too many open > files > at java.lang.UNIXProcess.(UNIX
[jira] (MDEP-391) Unpack fails on linux with large archives
[ https://jira.codehaus.org/browse/MDEP-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314512#comment-314512 ] Olivier Lamy commented on MDEP-391: --- @Kristian using the flag ignorePermissions is an other possible option :-) > Unpack fails on linux with large archives > - > > Key: MDEP-391 > URL: https://jira.codehaus.org/browse/MDEP-391 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: unpack >Affects Versions: 2.6 > Environment: Ubuntu 10.04 LTS >Reporter: Benoit Montuelle > > When unpacking "large " archives with numerous files (more than 1024 on this > os) I got the following error trace > [INFO] Expanding > /var/lib/deploy/.m2/repository/com/aprilwaf/wafservice/ihm-packaging-ecg/3.9-finsouscription-SNAPSHOT/ihm-packaging-ecg-3.9-finsouscription-SNAPSHOT-distribution-php.tar.gz > to /tmp/tmp5620480517649479513.tar > [INFO] Expanding: /tmp/tmp5620480517649479513.tar into > /var/lib/deploy/build-deploy/ecg/target/classes > org.codehaus.plexus.archiver.ArchiverException: Error while executing chmod. > at > org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:64) > at > org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFile(AbstractZipUnArchiver.java:236) > at > org.codehaus.plexus.archiver.tar.TarUnArchiver.execute(TarUnArchiver.java:92) > at > org.codehaus.plexus.archiver.tar.TarGZipUnArchiver.execute(TarGZipUnArchiver.java:76) > at > org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:108) > at > org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) > at > org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:122) > at > org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:95) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while > executing process. > at > org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:652) > at > org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:102) > at > org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:89) > at > org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:45) > ... 26 more > Caused by: java.io.IOException: Cannot run program "/bin/sh" (in directory > "/var/lib/deploy/build-deploy/ecg/target/classes/symfony-1.4/lib/plugins/sfDoctrinePlugin/test/unit/record"): > java.io.IOException: error=24, Too many open files > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at java.lang.Runtime.exec(Runtime.java:593) > at > org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:647) > ... 29 more > Caused by: java.io.IOException: java.io.IOException: error=24, Too many open > files > at java.lang.UNIXProcess.(UNIXProcess.java:148) > at java.lang.ProcessImpl.
[jira] (SCM-702) Incorrect documentation for parameter "skip" of goal "check-local-modification" of the plugin
Maarten van Schouwen created SCM-702: Summary: Incorrect documentation for parameter "skip" of goal "check-local-modification" of the plugin Key: SCM-702 URL: https://jira.codehaus.org/browse/SCM-702 Project: Maven SCM Issue Type: Bug Components: documentation, maven-plugin Affects Versions: 1.8.1 Reporter: Maarten van Schouwen Priority: Minor The documentation for the parameter "skip" of goal "check-local-modification" of the plugin is incorrect. Currently it is a copy of the documentation for parameter "errorMessage". -- 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-703) Unclear use of directory parameters for goal "check-local-modification" of the plugin
Maarten van Schouwen created SCM-703: Summary: Unclear use of directory parameters for goal "check-local-modification" of the plugin Key: SCM-703 URL: https://jira.codehaus.org/browse/SCM-703 Project: Maven SCM Issue Type: Bug Components: documentation, maven-plugin Affects Versions: 1.8.1 Reporter: Maarten van Schouwen Priority: Minor The goal "check-local-modification" has parameters "workingDirectory" and "baseDirectory", but it only uses "baseDirectory". This may be confusing for the end user because "mvn scm:help" shows parameters "basedir" and "workingDirectory". You only see "baseDirectory" if you use the goal with "mvn -X". It doesn't seem to be possible to specify any of the three on the command line, by the way. -- 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] (MSHARED-265) add fileset XML descriptor documentation generated from model
Herve Boutemy created MSHARED-265: - Summary: add fileset XML descriptor documentation generated from model Key: MSHARED-265 URL: https://jira.codehaus.org/browse/MSHARED-265 Project: Maven Shared Components Issue Type: Improvement Components: file-management Affects Versions: file-management-1.2.1 Reporter: Herve Boutemy There is a Modello model for fileset with useful information: it will be more precise that only actual example -- 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] (MSHARED-265) add fileset XML descriptor documentation generated from model
[ https://jira.codehaus.org/browse/MSHARED-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSHARED-265. - Resolution: Fixed Fix Version/s: file-management-1.2.2 Assignee: Herve Boutemy done in [r1414493|http://svn.apache.org/viewvc?rev=1414493&view=rev] > add fileset XML descriptor documentation generated from model > - > > Key: MSHARED-265 > URL: https://jira.codehaus.org/browse/MSHARED-265 > Project: Maven Shared Components > Issue Type: Improvement > Components: file-management >Affects Versions: file-management-1.2.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: file-management-1.2.2 > > > There is a Modello model for fileset with useful information: it will be more > precise that only actual example -- 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] (MSHARED-92) Cannot retreive FileNameMapper with MapperUtil
[
https://jira.codehaus.org/browse/MSHARED-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSHARED-92:
-
Description:
I'm trying to use file name mappers inside a maven plugin with the
file-management shared project.
I've added a fileset definition in the plugin's configuration as follow :
{code:xml}
info.flex-mojos
flex-compiler-mojo
true
2.0M11-SNAPSHOT
${basedir}/src
9.0.28
${basedir}/src
**/*.mxml
flatten
{code}
Unfortunately, I get a NPE while trying to retrieve my mapper :
{noformat}java.lang.NullPointerException
at
org.apache.maven.shared.model.fileset.mappers.MapperUtil.getFileNameMapper(MapperUtil.java:114)
at
info.rvin.mojo.flexmojo.compiler.ApplicationMojo.setUp(ApplicationMojo.java:194)
at
info.rvin.mojo.flexmojo.AbstractIrvinMojo.execute(AbstractIrvinMojo.java:178)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375){noformat}
I've checked current trunk on shared/file-management, it seems that the
"initializeBuiltIns" call should initialize implementations but it does not.
I have enclosed a trivial patch which should fix this.
was:
I'm trying to use file name mappers inside a maven plugin with the
file-management shared project.
I've added a fileset definition in the plugin's configuration as follow :
info.flex-mojos
flex-compiler-mojo
true
2.0M11-SNAPSHOT
${basedir}/src
9.0.28
${basedir}/src
**/*.mxml
flatten
Unfortunately, I get a NPE while trying to retrieve my mapper :
java.lang.NullPointerException
at
org.apache.maven.shared.model.fileset.mappers.MapperUtil.getFileNameMapper(MapperUtil.java:114)
at
info.rvin.mojo.flexmojo.compiler.ApplicationMojo.setUp(ApplicationMojo.java:194)
at
info.rvin.mojo.flexmojo.AbstractIrvinMojo.execute(AbstractIrvinMojo.java:178)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(Defau
[jira] (SCM-704) "includes/excludes" not always used by goals "status" and "check-local-modification" of the plugin
Maarten van Schouwen created SCM-704: Summary: "includes/excludes" not always used by goals "status" and "check-local-modification" of the plugin Key: SCM-704 URL: https://jira.codehaus.org/browse/SCM-704 Project: Maven SCM Issue Type: Bug Components: maven-plugin Affects Versions: 1.8.1 Reporter: Maarten van Schouwen Priority: Minor When using Mercurial, the goals "status" and "check-local-modification" do not use the include and exclude patterns. This is because check-local-modification does not use these parameters at all, and because for both goals, the Mercurial implementation returns the status of all files in the repository anyway. According to the documentation of ScmManager.status() that is OK. But include/exclude could still work for all SCM providers if the Mojos use the include/exclude filters after calling ScmManager.status(). -- 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] [Created] (MPOM-39) use only non-aggregate reports in parent pom
Hervé Boutemy created MPOM-39: - Summary: use only non-aggregate reports in parent pom Key: MPOM-39 URL: https://issues.apache.org/jira/browse/MPOM-39 Project: Maven POMs Issue Type: Bug Components: maven Affects Versions: MAVEN-22 Reporter: Hervé Boutemy Assignee: Hervé Boutemy Priority: Critical Fix For: MAVEN-23 Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate previously, aggregate was a parameter). In the maven parent pom, we're explicitely setting a reportSet configuration for m-javadoc-p, which is the first plugin implementing this pattern IIRC. But for other plugins, we don't define reportSets: then by default, every reporting goals are used, ie aggregate and non-aggregate. Now I understand why I'm experiencing twice PMD or Checkstyle runs in components lately... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-39) use only non-aggregate reports in parent pom
[ https://issues.apache.org/jira/browse/MPOM-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-39: -- Description: Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate previously, aggregate was a parameter). In the maven parent pom, we're explicitely setting a reportSet configuration for m-javadoc-p, which is the first plugin implementing this pattern IIRC. But for other plugins, we don't define reportSets: then by default, every reporting goals are used, ie aggregate and non-aggregate. Now I understand why I'm experiencing twice Checkstyle runs in components lately... was: Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate previously, aggregate was a parameter). In the maven parent pom, we're explicitely setting a reportSet configuration for m-javadoc-p, which is the first plugin implementing this pattern IIRC. But for other plugins, we don't define reportSets: then by default, every reporting goals are used, ie aggregate and non-aggregate. Now I understand why I'm experiencing twice PMD or Checkstyle runs in components lately... > use only non-aggregate reports in parent pom > > > Key: MPOM-39 > URL: https://issues.apache.org/jira/browse/MPOM-39 > Project: Maven POMs > Issue Type: Bug > Components: maven >Affects Versions: MAVEN-22 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Critical > Fix For: MAVEN-23 > > > Since some time, we're applying a new pattern where there is a separate > reporting goal for aggregate previously, aggregate was a parameter). > In the maven parent pom, we're explicitely setting a reportSet configuration > for m-javadoc-p, which is the first plugin implementing this pattern IIRC. > But for other plugins, we don't define reportSets: then by default, every > reporting goals are used, ie aggregate and non-aggregate. > Now I understand why I'm experiencing twice Checkstyle runs in components > lately... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (MPOM-39) use only non-aggregate reports in parent pom
[ https://issues.apache.org/jira/browse/MPOM-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-39. - > use only non-aggregate reports in parent pom > > > Key: MPOM-39 > URL: https://issues.apache.org/jira/browse/MPOM-39 > Project: Maven POMs > Issue Type: Bug > Components: maven >Affects Versions: MAVEN-22 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Critical > Fix For: MAVEN-23 > > > Since some time, we're applying a new pattern where there is a separate > reporting goal for aggregate previously, aggregate was a parameter). > In the maven parent pom, we're explicitely setting a reportSet configuration > for m-javadoc-p, which is the first plugin implementing this pattern IIRC. > But for other plugins, we don't define reportSets: then by default, every > reporting goals are used, ie aggregate and non-aggregate. > Now I understand why I'm experiencing twice Checkstyle runs in components > lately... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MPOM-39) use only non-aggregate reports in parent pom
[ https://issues.apache.org/jira/browse/MPOM-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy resolved MPOM-39. --- Resolution: Fixed fixed in [r1414507|http://svn.apache.org/viewvc?rev=1414507&view=rev] > use only non-aggregate reports in parent pom > > > Key: MPOM-39 > URL: https://issues.apache.org/jira/browse/MPOM-39 > Project: Maven POMs > Issue Type: Bug > Components: maven >Affects Versions: MAVEN-22 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Critical > Fix For: MAVEN-23 > > > Since some time, we're applying a new pattern where there is a separate > reporting goal for aggregate previously, aggregate was a parameter). > In the maven parent pom, we're explicitely setting a reportSet configuration > for m-javadoc-p, which is the first plugin implementing this pattern IIRC. > But for other plugins, we don't define reportSets: then by default, every > reporting goals are used, ie aggregate and non-aggregate. > Now I understand why I'm experiencing twice Checkstyle runs in components > lately... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-39) use only non-aggregate reports in parent pom
[ https://issues.apache.org/jira/browse/MPOM-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505205#comment-13505205 ] Hudson commented on MPOM-39: Integrated in maven-parent #127 (See [https://builds.apache.org/job/maven-parent/127/]) [MPOM-39] use only non-aggregate reports in parent pom (Revision 1414507) Result = SUCCESS hboutemy : http://svn.apache.org/viewvc/?view=rev&rev=1414507 Files : * /maven/pom/trunk/maven/pom.xml > use only non-aggregate reports in parent pom > > > Key: MPOM-39 > URL: https://issues.apache.org/jira/browse/MPOM-39 > Project: Maven POMs > Issue Type: Bug > Components: maven >Affects Versions: MAVEN-22 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Critical > Fix For: MAVEN-23 > > > Since some time, we're applying a new pattern where there is a separate > reporting goal for aggregate previously, aggregate was a parameter). > In the maven parent pom, we're explicitely setting a reportSet configuration > for m-javadoc-p, which is the first plugin implementing this pattern IIRC. > But for other plugins, we don't define reportSets: then by default, every > reporting goals are used, ie aggregate and non-aggregate. > Now I understand why I'm experiencing twice Checkstyle runs in components > lately... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-391) Unpack fails on linux with large archives
[ https://jira.codehaus.org/browse/MDEP-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314526#comment-314526 ] Kristian Rosenvold commented on MDEP-391: - @Benoit; I'd be really interested in hearing if 2.7 SNAPSHOT fixes the problem of leaking file handles since that'd give a pretty good pinpoint as to the cause of the problem. > Unpack fails on linux with large archives > - > > Key: MDEP-391 > URL: https://jira.codehaus.org/browse/MDEP-391 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: unpack >Affects Versions: 2.6 > Environment: Ubuntu 10.04 LTS >Reporter: Benoit Montuelle > > When unpacking "large " archives with numerous files (more than 1024 on this > os) I got the following error trace > [INFO] Expanding > /var/lib/deploy/.m2/repository/com/aprilwaf/wafservice/ihm-packaging-ecg/3.9-finsouscription-SNAPSHOT/ihm-packaging-ecg-3.9-finsouscription-SNAPSHOT-distribution-php.tar.gz > to /tmp/tmp5620480517649479513.tar > [INFO] Expanding: /tmp/tmp5620480517649479513.tar into > /var/lib/deploy/build-deploy/ecg/target/classes > org.codehaus.plexus.archiver.ArchiverException: Error while executing chmod. > at > org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:64) > at > org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFile(AbstractZipUnArchiver.java:236) > at > org.codehaus.plexus.archiver.tar.TarUnArchiver.execute(TarUnArchiver.java:92) > at > org.codehaus.plexus.archiver.tar.TarGZipUnArchiver.execute(TarGZipUnArchiver.java:76) > at > org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:108) > at > org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) > at > org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:122) > at > org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:95) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while > executing process. > at > org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:652) > at > org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:102) > at > org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:89) > at > org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:45) > ... 26 more > Caused by: java.io.IOException: Cannot run program "/bin/sh" (in directory > "/var/lib/deploy/build-deploy/ecg/target/classes/symfony-1.4/lib/plugins/sfDoctrinePlugin/test/unit/record"): > java.io.IOException: error=24, Too many open files > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at java.lang.Runtime.exec(Runtime.java:593) > at > org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:647) > ... 29 more > Caused by: java.io.IOException: java.io.IOException: error=2
