[jira] (MANTTASKS-237) artifact:dependencies/ Task only checks Maven Repo Servers
[ https://jira.codehaus.org/browse/MANTTASKS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=325528#comment-325528 ] Thomas Pasch commented on MANTTASKS-237: I was fuzzy with point 2. Here's an more detailed description what should be done: 2. a) For Release dependencies: Check local cache. If dependency is not there, download it from remote repository server(s) to the cache. b) For SNAPSHOT dependencies: Check local cache and remote repository server(s) to find out which SHAPSHOT build is the newest. If the newest build is in cache, use it. Else, download it from server to cache and use it. The problem with Maven 2.x Ant Tasks Version 2.1.3 is that only the remote server(s) are queried about dependencies. Hence, it there is a local cached SNAPSHOT build that is newer than the one on the server(s), it will _not_ be used. artifact:dependencies/ Task only checks Maven Repo Servers Key: MANTTASKS-237 URL: https://jira.codehaus.org/browse/MANTTASKS-237 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: dependencies task Affects Versions: 2.1.3 Environment: Ubuntu Raring/13.04 64bit, but most probably OS independant Reporter: Thomas Pasch Priority: Minor artifact:dependencies/ Task only checks Maven Repo Servers. This is wrong and best seen with SNAPSHOT dependencies. The dependency task should (also) take into account (in this proper sequence): 1. The current maven reactor, i.e. the modules to build currently. (This should be none, as the dependency task rather will build nothing.) 2. The local maven artifact cache (normally situated under ~/.m2/repository. 3. The repo servers defined in the pom.xml (and the default repo servers). (This is the only thing done currently.) -- 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] (MANTTASKS-234) artifact:dependencies does not download latest version SNAPSHOT dependency if already present locally
[ https://jira.codehaus.org/browse/MANTTASKS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=325529#comment-325529 ] Thomas Pasch commented on MANTTASKS-234: This is a little different from my own findings in MANTTASKS-237, where I concluded that more recent SNAPSHOT builds in cache are _never_ considered. However, I would agree that there is something wrong with artifact:dependencies... artifact:dependencies does not download latest version SNAPSHOT dependency if already present locally - Key: MANTTASKS-234 URL: https://jira.codehaus.org/browse/MANTTASKS-234 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: dependencies task Affects Versions: 2.1.3 Environment: Windows Reporter: Justin Rowe We are using artifact:dependencies to trigger download of an artifact from a remote repo to the local repo. When the dependency is a SNAPSHOT dependency, it only seems to check that the dependency exists in the local repo, it does not check that there is a more recent snapshot in the remote repo. So the snapshot artifact does not get updated with the latest version. My workaround is to call this artifact:dependencies, delete the artifact that is referred to in the property that gets set by this task, and then call artifact:dependencies again to ensure that we have the correct version. -- 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] (MANTTASKS-237) artifact:dependencies/ Task only checks Maven Repo Servers
[ https://jira.codehaus.org/browse/MANTTASKS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=325532#comment-325532 ] Thomas Pasch commented on MANTTASKS-237: MANTTASKS-234 also reports problems with artifact:dependencies/ but has different findings. MANTTASKS-233 suggests to use a more recent version of the maven-dependency-plugin (and mvn3). MANTTASKS-232 suggests to use mvn3 (instead of mvn2). I would consent to both (and I guess that the problem reported here would be gone with this change(s)). As a workaround one could use the [dependency:copy|https://maven.apache.org/plugins/maven-dependency-plugin/copy-mojo.html] task from the maven-dependency-plugin directly. But this is more or less the advice to abstain from using Maven 2.x Ant Tasks completely. artifact:dependencies/ Task only checks Maven Repo Servers Key: MANTTASKS-237 URL: https://jira.codehaus.org/browse/MANTTASKS-237 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: dependencies task Affects Versions: 2.1.3 Environment: Ubuntu Raring/13.04 64bit, but most probably OS independant Reporter: Thomas Pasch Priority: Minor artifact:dependencies/ Task only checks Maven Repo Servers. This is wrong and best seen with SNAPSHOT dependencies. The dependency task should (also) take into account (in this proper sequence): 1. The current maven reactor, i.e. the modules to build currently. (This should be none, as the dependency task rather will build nothing.) 2. The local maven artifact cache (normally situated under ~/.m2/repository. 3. The repo servers defined in the pom.xml (and the default repo servers). (This is the only thing done currently.) -- 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] (MANTTASKS-237) artifact:dependencies/ Task only checks Maven Repo Servers
Thomas Pasch created MANTTASKS-237: -- Summary: artifact:dependencies/ Task only checks Maven Repo Servers Key: MANTTASKS-237 URL: https://jira.codehaus.org/browse/MANTTASKS-237 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: dependencies task Affects Versions: 2.1.3 Environment: Ubuntu Raring/13.04 64bit, but most probably OS independant Reporter: Thomas Pasch Priority: Minor artifact:dependencies/ Task only checks Maven Repo Servers. This is wrong and best seen with SNAPSHOT dependencies. The dependency task should (also) take into account (in this proper sequence): 1. The current maven reactor, i.e. the modules to build currently. (This should be none, as the dependency task rather will build nothing.) 2. The local maven artifact cache (normally situated under ~/.m2/repository. 3. The repo servers defined in the pom.xml (and the default repo servers). (This is the only thing done currently.) -- 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] (MANTTASKS-237) artifact:dependencies/ Task only checks Maven Repo Servers
[ https://jira.codehaus.org/browse/MANTTASKS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=325474#comment-325474 ] Thomas Pasch commented on MANTTASKS-237: As addition, an 'offline' mode for the dependency task would come in handy. This would abolish step 3. artifact:dependencies/ Task only checks Maven Repo Servers Key: MANTTASKS-237 URL: https://jira.codehaus.org/browse/MANTTASKS-237 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: dependencies task Affects Versions: 2.1.3 Environment: Ubuntu Raring/13.04 64bit, but most probably OS independant Reporter: Thomas Pasch Priority: Minor artifact:dependencies/ Task only checks Maven Repo Servers. This is wrong and best seen with SNAPSHOT dependencies. The dependency task should (also) take into account (in this proper sequence): 1. The current maven reactor, i.e. the modules to build currently. (This should be none, as the dependency task rather will build nothing.) 2. The local maven artifact cache (normally situated under ~/.m2/repository. 3. The repo servers defined in the pom.xml (and the default repo servers). (This is the only thing done currently.) -- 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] (MJAVADOC-362) aggregate-jar: javadoc build on multi-module maven project in parent pom does not aggreate classpath
Thomas Pasch created MJAVADOC-362: - Summary: aggregate-jar: javadoc build on multi-module maven project in parent pom does not aggreate classpath Key: MJAVADOC-362 URL: https://jira.codehaus.org/browse/MJAVADOC-362 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.9 Environment: Ubuntu 12.04/quantal 64-bit Reporter: Thomas Pasch When building aggregated javadocs for a multi-module maven project in parent pom, maven-javadoc-plugin does not aggreate classpath. Maybe this is the same problem as reported as MJAVADOC-116 . You can see the the problem at https://bitbucket.org/nuclos/nuclos-api (git repository, branch master, commits *before* 2bda1542282a7bac52d0c929c51a4a0546583bcb). With commit 2bda1542282a7bac52d0c929c51a4a0546583bcb, I fixed the problem by hard-wiring the needed dependency into the parent pom (well, this is really a HACK). This is the actual output in the error case: [...] Generating /var/lib/jenkins/jobs/nuclos-api-trunk/workspace/target/apidocs/constant-values.html... Generating /var/lib/jenkins/jobs/nuclos-api-trunk/workspace/target/apidocs/serialized-form.html... 134 warnings [INFO] [INFO] Reactor Summary: [INFO] [INFO] Nuclos API FAILURE [23.216s] [INFO] nuclos-rigid-api .. SKIPPED [INFO] nuclos-common-api . SKIPPED [INFO] nuclos-server-api . SKIPPED [INFO] nuclos-client-api . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 23.380s [INFO] Finished at: Tue Mar 19 15:15:13 CET 2013 [INFO] Final Memory: 15M/981M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9:aggregate-jar (aggregate-jar) on project nuclos-api: MavenReportException: Error while creating archive: [ERROR] Exit code: 1 - /var/lib/jenkins/jobs/nuclos-api-trunk/workspace/nuclos-common-api/src/main/java/org/nuclos/api/service/UserSettingsService.java:19: package javax.annotation.security does not exist [ERROR] import javax.annotation.security.RolesAllowed; [ERROR] ^ [ERROR] /var/lib/jenkins/jobs/nuclos-api-trunk/workspace/nuclos-common-api/src/main/java/org/nuclos/api/service/UserSettingsService.java:31: cannot find symbol [ERROR] symbol : class RolesAllowed [ERROR] location: interface org.nuclos.api.service.UserSettingsService [ERROR] @RolesAllowed(Login) [ERROR] ^ [ERROR] /var/lib/jenkins/jobs/nuclos-api-trunk/workspace/nuclos-common-api/src/main/java/org/nuclos/api/service/UserSettingsService.java:39: cannot find symbol [ERROR] symbol : class RolesAllowed [ERROR] location: interface org.nuclos.api.service.UserSettingsService [ERROR] @RolesAllowed(Login) [ERROR] ^ [ERROR] javadoc: warning - Error fetching URL: http://commons.apache.org/lang/api-release/package-list [ERROR] javadoc: warning - Error fetching URL: http://commons.apache.org/collections/api-release/package-list [ERROR] javadoc: warning - Error fetching URL: http://commons.apache.org/dbcp/api-1.4/package-list [ERROR] javadoc: warning - Error fetching URL: http://commons.apache.org/codec/api-release/package-list [ERROR] /var/lib/jenkins/jobs/nuclos-api-trunk/workspace/nuclos-common-api/src/main/java/org/nuclos/api/statemodel/State.java:12: warning - Tag @link: reference not found: StatemodelProvider [ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc [ERROR] at com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46) [ERROR] at com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:811) [ERROR] at com.sun.tools.doclets.formats.html.SubWriterHolderWriter.printIndexComment(SubWriterHolderWriter.java:101) [ERROR] at com.sun.tools.doclets.formats.html.SubWriterHolderWriter.printSummaryLinkComment(SubWriterHolderWriter.java:137) [ERROR] at com.sun.tools.doclets.formats.html.AbstractMemberWriter.writeMemberSummary(AbstractMemberWriter.java:407) [ERROR] at com.sun.tools.doclets.internal.toolkit.builders.MemberSummaryBuilder.buildSummary(MemberSummaryBuilder.java:309) [ERROR] at com.sun.tools.doclets.internal.toolkit.builders.MemberSummaryBuilder.buildMethodsSummary(MemberSummaryBuilder.java:260) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [ERROR] at
[jira] (MANTTASKS-201) artifact:mvn generates org.apache.tools.ant.ExitException: Permission (java.lang.RuntimePermission exitVM) was not granted when fork=false
[
https://jira.codehaus.org/browse/MANTTASKS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=302554#comment-302554
]
Thomas Pasch commented on MANTTASKS-201:
This is really great. Ant sets a security police on 'exitVM' just in order to
throw an Exception and ... exit! It strongly feels like ant bug.
On the other site, perhaps somebody could force a introduction of an command
line option that forces mvn *not* to call exit at all...
artifact:mvn generates org.apache.tools.ant.ExitException: Permission
(java.lang.RuntimePermission exitVM) was not granted when fork=false
Key: MANTTASKS-201
URL: https://jira.codehaus.org/browse/MANTTASKS-201
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: mvn task
Affects Versions: 2.1.1
Reporter: Matt McHenry
Priority: Minor
Using this simple ant target:
{code:xml} target name=mvn.invoke description=invokes maven
property environment=env/
artifact:mvn pom=pom.xml mavenHome=${env.M2_HOME} fork=true
arg value=${mvn.goal}/
/artifact:mvn
/target{code}
I get the correct behaviour:
{noformat}
$ M2_HOME=`cygpath -w $M2_HOME` ant -Dmvn.goal=-version mvn.invoke
Searching for build.xml ...
Buildfile: c:\Users\mmchenry\svn\cli\trunk\runtime\maven\build.xml
mvn.setversion:
mvn.invoke:
[artifact:mvn] Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
[artifact:mvn] Java version: 1.6.0_17
[artifact:mvn] Java home: c:\Program Files\Java\jdk1.6.0_17\jre
[artifact:mvn] Default locale: en_US, platform encoding: Cp1252
[artifact:mvn] OS name: windows 7 version: 6.1 arch: amd64 Family:
windows
BUILD SUCCESSFUL
Total time: 0 seconds{noformat}
But if I set fork=false, then I get:
{noformat}
[artifact:mvn] Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
[artifact:mvn] Java version: 1.6.0_17
[artifact:mvn] Java home: c:\Program Files\Java\jdk1.6.0_17\jre
[artifact:mvn] Default locale: en_US, platform encoding: Cp1252
[artifact:mvn] OS name: windows 7 version: 6.1 arch: amd64 Family:
windows
[artifact:mvn] org.apache.tools.ant.ExitException: Permission
(java.lang.RuntimePermission exitVM) was not granted.
[artifact:mvn] at
org.apache.tools.ant.types.Permissions$MySM.checkExit(Permissions.java:196)
[artifact:mvn] at java.lang.Runtime.exit(Runtime.java:88)
[artifact:mvn] at java.lang.System.exit(System.java:904)
[artifact:mvn] at org.codehaus.classworlds.Launcher.main(Launcher.java:376)
[artifact:mvn] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[artifact:mvn] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[artifact:mvn] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[artifact:mvn] at java.lang.reflect.Method.invoke(Method.java:597)
[artifact:mvn] at
org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217)
[artifact:mvn] at
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152)
[artifact:mvn] at org.apache.tools.ant.taskdefs.Java.run(Java.java:764)
[artifact:mvn] at
org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:218)
[artifact:mvn] at
org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:132)
[artifact:mvn] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:105)
[artifact:mvn] at org.apache.maven.artifact.ant.Mvn.execute(Mvn.java:81)
[artifact:mvn] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[artifact:mvn] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[artifact:mvn] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[artifact:mvn] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[artifact:mvn] at java.lang.reflect.Method.invoke(Method.java:597)
[artifact:mvn] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[artifact:mvn] at org.apache.tools.ant.Task.perform(Task.java:348)
[artifact:mvn] at org.apache.tools.ant.Target.execute(Target.java:357)
[artifact:mvn] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[artifact:mvn] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
[artifact:mvn] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[artifact:mvn] at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[artifact:mvn] at
org.apache.tools.ant.Project.executeTargets(Project.java:1189)
[artifact:mvn] at org.apache.tools.ant.Main.runBuild(Main.java:758)
[artifact:mvn] at org.apache.tools.ant.Main.startAnt(Main.java:217)
[artifact:mvn]
[jira] (MANTTASKS-201) artifact:mvn generates org.apache.tools.ant.ExitException: Permission (java.lang.RuntimePermission exitVM) was not granted when fork=false
[
https://jira.codehaus.org/browse/MANTTASKS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=302554#comment-302554
]
Thomas Pasch edited comment on MANTTASKS-201 at 7/3/12 3:45 AM:
This is really great. Ant sets a security police on 'exitVM' just in order to
throw an Exception and ... exit! It strongly feels like an ant bug.
On the other site, perhaps somebody could force a introduction of an command
line option that forces mvn *not* to call exit at all...
was (Author: aannoo):
This is really great. Ant sets a security police on 'exitVM' just in order
to throw an Exception and ... exit! It strongly feels like ant bug.
On the other site, perhaps somebody could force a introduction of an command
line option that forces mvn *not* to call exit at all...
artifact:mvn generates org.apache.tools.ant.ExitException: Permission
(java.lang.RuntimePermission exitVM) was not granted when fork=false
Key: MANTTASKS-201
URL: https://jira.codehaus.org/browse/MANTTASKS-201
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: mvn task
Affects Versions: 2.1.1
Reporter: Matt McHenry
Priority: Minor
Using this simple ant target:
{code:xml} target name=mvn.invoke description=invokes maven
property environment=env/
artifact:mvn pom=pom.xml mavenHome=${env.M2_HOME} fork=true
arg value=${mvn.goal}/
/artifact:mvn
/target{code}
I get the correct behaviour:
{noformat}
$ M2_HOME=`cygpath -w $M2_HOME` ant -Dmvn.goal=-version mvn.invoke
Searching for build.xml ...
Buildfile: c:\Users\mmchenry\svn\cli\trunk\runtime\maven\build.xml
mvn.setversion:
mvn.invoke:
[artifact:mvn] Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
[artifact:mvn] Java version: 1.6.0_17
[artifact:mvn] Java home: c:\Program Files\Java\jdk1.6.0_17\jre
[artifact:mvn] Default locale: en_US, platform encoding: Cp1252
[artifact:mvn] OS name: windows 7 version: 6.1 arch: amd64 Family:
windows
BUILD SUCCESSFUL
Total time: 0 seconds{noformat}
But if I set fork=false, then I get:
{noformat}
[artifact:mvn] Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
[artifact:mvn] Java version: 1.6.0_17
[artifact:mvn] Java home: c:\Program Files\Java\jdk1.6.0_17\jre
[artifact:mvn] Default locale: en_US, platform encoding: Cp1252
[artifact:mvn] OS name: windows 7 version: 6.1 arch: amd64 Family:
windows
[artifact:mvn] org.apache.tools.ant.ExitException: Permission
(java.lang.RuntimePermission exitVM) was not granted.
[artifact:mvn] at
org.apache.tools.ant.types.Permissions$MySM.checkExit(Permissions.java:196)
[artifact:mvn] at java.lang.Runtime.exit(Runtime.java:88)
[artifact:mvn] at java.lang.System.exit(System.java:904)
[artifact:mvn] at org.codehaus.classworlds.Launcher.main(Launcher.java:376)
[artifact:mvn] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[artifact:mvn] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[artifact:mvn] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[artifact:mvn] at java.lang.reflect.Method.invoke(Method.java:597)
[artifact:mvn] at
org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217)
[artifact:mvn] at
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152)
[artifact:mvn] at org.apache.tools.ant.taskdefs.Java.run(Java.java:764)
[artifact:mvn] at
org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:218)
[artifact:mvn] at
org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:132)
[artifact:mvn] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:105)
[artifact:mvn] at org.apache.maven.artifact.ant.Mvn.execute(Mvn.java:81)
[artifact:mvn] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[artifact:mvn] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[artifact:mvn] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[artifact:mvn] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[artifact:mvn] at java.lang.reflect.Method.invoke(Method.java:597)
[artifact:mvn] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[artifact:mvn] at org.apache.tools.ant.Task.perform(Task.java:348)
[artifact:mvn] at org.apache.tools.ant.Target.execute(Target.java:357)
[artifact:mvn] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[artifact:mvn] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
[artifact:mvn] at
[jira] Updated: (MASSEMBLY-588) Build fails because of 'ls -1nlaR /'
[ https://jira.codehaus.org/browse/MASSEMBLY-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Pasch updated MASSEMBLY-588: --- Attachment: partial_log.bz2 Build fails because of 'ls -1nlaR /' Key: MASSEMBLY-588 URL: https://jira.codehaus.org/browse/MASSEMBLY-588 Project: Maven 2.x Assembly Plugin Issue Type: Bug Environment: Ubuntu 11.10 (oneiric) Reporter: Thomas Pasch Attachments: partial_log.bz2 This is a report again org.apache.maven.plugins:maven-assembly-plugin:2.2.2:single (package-assembly) used in conjunction with maven 3.0.3. I'm trying to build ebml-viewer from svn r126 (lastest) at http://code.google.com/p/ebml-viewer/source/checkout . Build fails on Linux, but the developer of ebml-viewer reports that it builds fine on Windows. Last lines of output from failed build with 'mvn -DskipTests -X -e package 21 | tee log': [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2:37.924s [INFO] Finished at: Tue Dec 06 20:30:47 CET 2011 [INFO] Final Memory: 8M/216M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.2:single (package-assembly) on project ebml-viewer: Failed to create assembly: Error creating assembly archive bin: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.2:single (package-assembly) on project ebml-viewer: Failed to create assembly: Error creating assembly archive bin: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error creating assembly archive bin: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:504) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error creating assembly archive bin: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:189) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:445) ... 21 more Caused by: org.codehaus.plexus.archiver.ArchiverException: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' at org.codehaus.plexus.archiver.AbstractArchiver$1.hasNext(AbstractArchiver.java:439) at
[jira] Commented: (MASSEMBLY-588) Build fails because of 'ls -1nlaR /'
[ https://jira.codehaus.org/browse/MASSEMBLY-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285050#comment-285050 ] Thomas Pasch commented on MASSEMBLY-588: Issue at ebml-viewer: http://code.google.com/p/ebml-viewer/issues/detail?id=1 Build fails because of 'ls -1nlaR /' Key: MASSEMBLY-588 URL: https://jira.codehaus.org/browse/MASSEMBLY-588 Project: Maven 2.x Assembly Plugin Issue Type: Bug Environment: Ubuntu 11.10 (oneiric) Reporter: Thomas Pasch Attachments: partial_log.bz2 This is a report again org.apache.maven.plugins:maven-assembly-plugin:2.2.2:single (package-assembly) used in conjunction with maven 3.0.3. I'm trying to build ebml-viewer from svn r126 (lastest) at http://code.google.com/p/ebml-viewer/source/checkout . Build fails on Linux, but the developer of ebml-viewer reports that it builds fine on Windows. Last lines of output from failed build with 'mvn -DskipTests -X -e package 21 | tee log': [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2:37.924s [INFO] Finished at: Tue Dec 06 20:30:47 CET 2011 [INFO] Final Memory: 8M/216M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.2:single (package-assembly) on project ebml-viewer: Failed to create assembly: Error creating assembly archive bin: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.2:single (package-assembly) on project ebml-viewer: Failed to create assembly: Error creating assembly archive bin: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error creating assembly archive bin: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:504) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error creating assembly archive bin: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:189) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:445) ... 21 more Caused by: org.codehaus.plexus.archiver.ArchiverException: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' at
