[jira] [Commented] (MASSEMBLY-781) Execution make-assembly fails: user id is too big
[
https://issues.apache.org/jira/browse/MASSEMBLY-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640544#comment-14640544
]
Matthew Storer commented on MASSEMBLY-781:
--
So, I found a workaround for this. For the purpose of this example, the user
{{localuser}} is a local user account with a low user ID (e.g., 501), while
{{domainuser}} is a domain user with a high user ID (e.g. 1535409742).
Apparently, not only does the executing user need to have a low user ID, but so
apparently do all of the files that are processed during the assembly. Also,
for this example, the group {{sharedgroup}} is a group that is shared between
{{localuser}} and {{domainuser}}.
1. sudo su - localuser
2. cd project directory
3. find . -exec chown localuser {} \;
4. find . -exec chgrp sharedgroup {} \;
5. find . -type d -exec chmod 775 {} \;
6. find . -type f -exec chmod 664 {} \;
7. mvn clean
8. mvn package
Note that I include steps (4), (5), and (6) to ensure that all files are in the
same group, and that all group members have the same access to files and
folders as does the owner. Maybe overkill, but this ensures all files are on
the same page, and that when I exit out of the {{localuser}} shell, back into
the {{domainuser}} shell, that I'll still be able to access and process files
as before.
Execution make-assembly fails: user id is too big
-
Key: MASSEMBLY-781
URL: https://issues.apache.org/jira/browse/MASSEMBLY-781
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.5.5
Environment: Mac OS X 10.10.4 (Yosemite)
Maven 3.3.3
Reporter: Matthew Storer
Labels: assembly, build, maven
maven-assembly-plugin fails make-assembly execution when the executing user's
ID is too big.
While building a multi-module project (X) from the command line using {{mvn
package}}, all defined modules build just fine, but assembling X itself fails
with the following error:
{quote}
[INFO]
[INFO] Building X 1.0
[INFO]
[INFO]
[INFO] --- maven-assembly-plugin:2.5.5:single (make-assembly) @ x ---
[INFO] Reading assembly descriptor: src/assembly/bin-assembly.xml
[INFO] Building tar: /bb/x/target/x-1.0-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Common . SUCCESS [ 3.180
s]
[INFO] A Service .. SUCCESS [ 3.337
s]
[INFO] B Service .. SUCCESS [ 2.186
s]
[INFO] A User Interface ... SUCCESS [ 1.331
s]
[INFO] B User Interface ... SUCCESS [ 1.380
s]
[INFO] X .. FAILURE [ 0.346
s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 19.722 s
[INFO] Finished at: 2015-07-23T16:32:34-04:00
[INFO] Final Memory: 53M/279M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (make-assembly)
on project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742' is too big ( 2097151 ). - [Help 1]
{quote}
Snippet from X multi-module POM that configures maven-assembly-plugin:
{quote}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.5.5/version
configuration
descriptors
descriptorsrc/assembly/bin-assembly.xml/descriptor
descriptorsrc/assembly/src-assembly.xml/descriptor
/descriptors
/configuration
executions
execution
idmake-assembly/id
phasepackage/phase
goals
goalsingle/goal
/goals
/execution
/executions
/plugin
{quote}
Error and stack trace:
{quote}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (make-assembly)
on project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742'
[jira] [Updated] (MEAR-216) Unable to include dependencies of type test-jar
[
https://issues.apache.org/jira/browse/MEAR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Frolov updated MEAR-216:
--
Attachment: test-jar-in-ear-2.zip
The project attached before was not correct.
This one do really shows the error.
Unable to include dependencies of type test-jar
---
Key: MEAR-216
URL: https://issues.apache.org/jira/browse/MEAR-216
Project: Maven Ear Plugin
Issue Type: Improvement
Affects Versions: 2.10
Reporter: Maxim Frolov
Priority: Blocker
Fix For: more-investigation
Attachments: test-jar-in-ear-2.zip, test-jar-in-ear.zip
Please implement support for artifacts of type *test-jar*.
One of the use cases would be to build a test EAR as a mix of production and
test JARs where the test JARs are used to set up the test data used to test
the production code.
Currently including one or more dependencies of type test-jar causes
*LifecycleExecutionException*:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml
(default-generate-application-xml) on project suite-systemtests-common-ear:
Failed to initialize ear modules: Unknown artifact type[test-jar] for
artifact_id - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml
(default-generate-application-xml) on project suite-systemtests-common-ear:
Failed to initialize ear modules
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:320)
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:606)
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
initialize ear modules
at
org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260)
at
org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162)
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.ear.UnknownArtifactTypeException: Unknown
artifact type[test-jar] for common-domain-impl
at
org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88)
at
org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250)
... 22 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MEAR-216) Unable to include dependencies of type test-jar
[
https://issues.apache.org/jira/browse/MEAR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640609#comment-14640609
]
Maxim Frolov commented on MEAR-216:
---
Sorry, the example project showing the error was incorrect.
I have just attached a new project which is the same as the first project but
the dependency in the EAR project to the LIB project is slightly different:
{code:title=classifiertests/classifier works:}
dependency
groupId${project.groupId}/groupId
artifactIdtest-jar-in-ear-lib/artifactId
version${project.version}/version
classifiertests/classifier
/dependency
{code}
{code:title=typetest-jar/type does not work:}
dependency
groupId${project.groupId}/groupId
artifactIdtest-jar-in-ear-lib/artifactId
version${project.version}/version
typetest-jar/type
/dependency
{code}
Below is the full log for {{cd lib mvn -X package}}:
{noformat}
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
Maven home: D:\bin\apache-maven-3.0.5
Java version: 1.8.0_45, vendor: Oracle Corporation
Java home: D:\bin\Java\jdk1.8.0_45\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: dos
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from D:\bin\apache-maven-3.0.5\conf\settings.xml
[DEBUG] Reading user settings from C:\Users\frol\.m2\settings.xml
[DEBUG] Using local repository at D:\.m2\repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for
D:\.m2\repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project frol:test-jar-in-ear-ear:ear:1.0-SNAPSHOT:
(none)
[DEBUG] Looking up lifecyle mappings for packaging ear from
ClassRealm[plexus.core, parent: null]
[DEBUG] === REACTOR BUILD PLAN
[DEBUG] Project: frol:test-jar-in-ear-ear:ear:1.0-SNAPSHOT
[DEBUG] Tasks: [package]
[DEBUG] Style: Regular
[DEBUG] ===
[INFO]
[INFO]
[INFO] Building test-jar-in-ear-ear 1.0-SNAPSHOT
[INFO]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN
[DEBUG] Project: frol:test-jar-in-ear-ear:1.0-SNAPSHOT
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): [test]
[DEBUG] Repositories (dependencies): [artifactory.repo1
(http://example.net:8080/repo1, releases)]
[DEBUG] Repositories (plugins) : [artifactory.repo1
(http://example.net:8080/repo1, releases)]
[DEBUG]
surefire failure JDK 8
Hi, I do not call System.exit() and can compile fine using Gradle - but mvn clean install fails telling me that the surefire plugin has detected a System.exit() call which is not true at all. Also, it seems after running several times, the failure is intermittent - meaning I try deleting my target directory or just running clean, and sometimes that makes the build work and most times it doesn't. I am running JavaSE 8.0_45-b14 Please Help! My company cannot run Java 8 either due to the same failure??? Here is the stack trace: Running org.numenta.nupic.examples.napi.NetworkAPIDemoTest # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x0001073bb1b8, pid=3071, tid=23811 # # JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.45-b02 mixed mode bsd-amd64 compressed oops) # Problematic frame: # V [libjvm.dylib+0x3bb1b8] # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try ulimit -c unlimited before starting Java again # # An error report file with more information is saved as: # /Users/cogmission/git/htm.java/hs_err_pid3071.log # # Compiler replay data is saved as: # /Users/cogmission/git/htm.java/replay_pid3071.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # /bin/sh: line 1: 3071 Abort trap: 6 /Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/jre/bin/java -javaagent:/Users/cogmission/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/Users/cogmission/git/htm.java/target/jacoco.exec -jar /Users/cogmission/git/htm.java/target/surefire/surefirebooter8022026702477323241.jar /Users/cogmission/git/htm.java/target/surefire/surefire7353030015599925387tmp /Users/cogmission/git/htm.java/target/surefire/surefire_07719256945721581516tmp Results : Tests run: 148, Failures: 0, Errors: 0, Skipped: 1 [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 10.630 s [INFO] Finished at: 2015-07-24T16:09:03-05:00 [INFO] Final Memory: 25M/958M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project htm.java: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ? - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project htm.java: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ? at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) 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:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The forked VM terminated without
[jira] [Resolved] (MCHANGES-358) Remove dependency resolution ResolutionScope.TEST from AnnouncementMojo
[
https://issues.apache.org/jira/browse/MCHANGES-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirko Friedenhagen resolved MCHANGES-358.
-
Resolution: Fixed
Fixed with http://svn.apache.org/viewvc?view=revisionrevision=1692576
Remove dependency resolution ResolutionScope.TEST from AnnouncementMojo
Key: MCHANGES-358
URL: https://issues.apache.org/jira/browse/MCHANGES-358
Project: Maven Changes Plugin
Issue Type: Bug
Components: announcement
Affects Versions: 2.11
Reporter: Mirko Friedenhagen
Assignee: Mirko Friedenhagen
Fix For: 2.12
According to
https://github.com/apache/maven-plugins/blob/2ace62dc71387a6f6b7d5fdd203c6570fb16eff1/maven-changes-plugin/src/main/java/org/apache/maven/plugin/announcement/AnnouncementMojo.java#L70
the AnnouncementMojo requires dependency resolution
ResolutionScope.TEST
Because of this it is not possible to run
{{changes:announcement-generate}} in multi module project when the
artifacts are not already installed/deployed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MCHANGES-358) Remove dependency resolution ResolutionScope.TEST from AnnouncementMojo
Mirko Friedenhagen created MCHANGES-358:
---
Summary: Remove dependency resolution ResolutionScope.TEST from
AnnouncementMojo
Key: MCHANGES-358
URL: https://issues.apache.org/jira/browse/MCHANGES-358
Project: Maven Changes Plugin
Issue Type: Bug
Components: announcement
Affects Versions: 2.11
Reporter: Mirko Friedenhagen
Assignee: Mirko Friedenhagen
Fix For: 2.12
According to
https://github.com/apache/maven-plugins/blob/2ace62dc71387a6f6b7d5fdd203c6570fb16eff1/maven-changes-plugin/src/main/java/org/apache/maven/plugin/announcement/AnnouncementMojo.java#L70
the AnnouncementMojo requires dependency resolution
ResolutionScope.TEST
Because of this it is not possible to run
{{changes:announcement-generate}} in multi module project when the
artifacts are not already installed/deployed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MSOURCES-81) allow sources jar to contain Maven descriptor
Peter lynch created MSOURCES-81: --- Summary: allow sources jar to contain Maven descriptor Key: MSOURCES-81 URL: https://issues.apache.org/jira/browse/MSOURCES-81 Project: Maven Source Plugin Issue Type: Bug Affects Versions: 2.4 Reporter: Peter lynch The source:jar mojo explicitly prevents the Maven descriptor from being added to the produced -sources.jar file. https://github.com/apache/maven-plugins/blob/trunk/maven-source-plugin/src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java#L292-292 I could not find an explanation or technical reason why this is done. Adding the maven descriptor to the source jar can help expose valuable information about the build that produced it. Expected: - allow the archiver used to create the source jar to respect the plexus archiver configuration if it is configured to include the Maven descriptor. - preserve the default behaviour of not including the Maven descriptor, for (unknown) backwards compatibility reasons only -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MJAVADOC-431) allow javadoc jar to contain Maven descriptor
Peter lynch created MJAVADOC-431: Summary: allow javadoc jar to contain Maven descriptor Key: MJAVADOC-431 URL: https://issues.apache.org/jira/browse/MJAVADOC-431 Project: Maven Javadoc Plugin Issue Type: Bug Affects Versions: 2.10.3 Reporter: Peter lynch The javadoc:jar mojo explicitly prevents the Maven descriptor from being added to the produced javadoc.jar file. https://github.com/apache/maven-plugins/blob/trunk/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocJar.java#L299-299 I could not find an explanation or technical reason why this is done. Adding the maven descriptor to the javadoc jar can help expose valuable information about the build that produced it and should be at the discretion of the build process. Expected: - allow the archiver used to create the javadoc jar to respect the plexus archiver configuration if it is configured to include the Maven descriptor. - preserve the default behaviour of not including the Maven descriptor, for (unknown) backwards compatibility reasons only -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MASSEMBLY-781) Execution make-assembly fails: user id is too big
[
https://issues.apache.org/jira/browse/MASSEMBLY-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640499#comment-14640499
]
Matthew Storer commented on MASSEMBLY-781:
--
Note : the reason my user ID is so large is because I'm logged into my system
through a domain account, managed by Active Directory. Apparently OS X assigns
ridiculously large user IDs to domain accounts.
Execution make-assembly fails: user id is too big
-
Key: MASSEMBLY-781
URL: https://issues.apache.org/jira/browse/MASSEMBLY-781
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.5.5
Environment: Mac OS X 10.10.4 (Yosemite)
Maven 3.3.3
Reporter: Matthew Storer
Labels: assembly, build, maven
While building a multi-module project (X) from the command line using {{mvn
package}}, all defined modules build just fine, but assembling X itself fails
with the following error:
{quote}
[INFO]
[INFO] Building X 1.0
[INFO]
[INFO]
[INFO] --- maven-assembly-plugin:2.5.5:single (make-assembly) @ x ---
[INFO] Reading assembly descriptor: src/assembly/bin-assembly.xml
[INFO] Building tar: /bb/x/target/x-1.0-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Common . SUCCESS [ 3.180
s]
[INFO] A Service .. SUCCESS [ 3.337
s]
[INFO] B Service .. SUCCESS [ 2.186
s]
[INFO] A User Interface ... SUCCESS [ 1.331
s]
[INFO] B User Interface ... SUCCESS [ 1.380
s]
[INFO] X .. FAILURE [ 0.346
s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 19.722 s
[INFO] Finished at: 2015-07-23T16:32:34-04:00
[INFO] Final Memory: 53M/279M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (make-assembly)
on project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742' is too big ( 2097151 ). - [Help 1]
{quote}
Snippet from X multi-module POM that configures maven-assembly-plugin:
{quote}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.5.5/version
configuration
descriptors
descriptorsrc/assembly/bin-assembly.xml/descriptor
descriptorsrc/assembly/src-assembly.xml/descriptor
/descriptors
/configuration
executions
execution
idmake-assembly/id
phasepackage/phase
goals
goalsingle/goal
/goals
/execution
/executions
/plugin
{quote}
Error and stack trace:
{quote}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (make-assembly)
on project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742' is too big ( 2097151 ). - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single
(make-assembly) on project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742' is too big ( 2097151 ).
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
[jira] [Updated] (MASSEMBLY-781) Execution make-assembly fails: user id is too big
[
https://issues.apache.org/jira/browse/MASSEMBLY-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Storer updated MASSEMBLY-781:
-
Description:
maven-assembly-plugin fails make-assembly execution when the executing user's
ID is too big.
While building a multi-module project (X) from the command line using {{mvn
package}}, all defined modules build just fine, but assembling X itself fails
with the following error:
{quote}
[INFO]
[INFO] Building X 1.0
[INFO]
[INFO]
[INFO] --- maven-assembly-plugin:2.5.5:single (make-assembly) @ x ---
[INFO] Reading assembly descriptor: src/assembly/bin-assembly.xml
[INFO] Building tar: /bb/x/target/x-1.0-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Common . SUCCESS [ 3.180 s]
[INFO] A Service .. SUCCESS [ 3.337 s]
[INFO] B Service .. SUCCESS [ 2.186 s]
[INFO] A User Interface ... SUCCESS [ 1.331 s]
[INFO] B User Interface ... SUCCESS [ 1.380 s]
[INFO] X .. FAILURE [ 0.346 s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 19.722 s
[INFO] Finished at: 2015-07-23T16:32:34-04:00
[INFO] Final Memory: 53M/279M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (make-assembly) on
project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742' is too big ( 2097151 ). - [Help 1]
{quote}
Snippet from X multi-module POM that configures maven-assembly-plugin:
{quote}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.5.5/version
configuration
descriptors
descriptorsrc/assembly/bin-assembly.xml/descriptor
descriptorsrc/assembly/src-assembly.xml/descriptor
/descriptors
/configuration
executions
execution
idmake-assembly/id
phasepackage/phase
goals
goalsingle/goal
/goals
/execution
/executions
/plugin
{quote}
Error and stack trace:
{quote}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (make-assembly) on
project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742' is too big ( 2097151 ). - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (make-assembly) on
project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742' is too big ( 2097151 ).
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
[jira] [Created] (MWAR-352) web.xml not being replaced but plugin configuration
Alex Sebastiao Constancio created MWAR-352: -- Summary: web.xml not being replaced but plugin configuration Key: MWAR-352 URL: https://issues.apache.org/jira/browse/MWAR-352 Project: Maven WAR Plugin Issue Type: Bug Affects Versions: 2.6 Environment: Windows 7 x64, Eclipse Luna, JSF 2 project Reporter: Alex Sebastiao Constancio My pom.xml file has the following in it: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.6/version!--$NO-MVN-MAN-VER$-- configuration webXmlsrc/main/webconfig/release/web.xml/webXml /configuration /plugin /plugins /build As you can see, the web.xml to be used by war plugin when running Maven install is located outside of the webapp folder. This work perfectly if there ins't a web.xml in webapp/WEB-INF folder, but the pluging refuses to use the web.xml from webconfig/release if there is already a file with the same name in webapp/WEB-INF. The issue is that I have to keep one web.xml in webapp/WEB-INF in order to be able publish the application to my local application server for debug. This file has particular settings for a local environment. However, when I want to produce a war to publish in the production server, it has to be another web.xml, the one located in webconfig/release folder. Problem is that the war plugin does not replaces one file by the other when generating the war file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MASSEMBLY-781) Execution make-assembly fails: user id is too big
[
https://issues.apache.org/jira/browse/MASSEMBLY-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Storer updated MASSEMBLY-781:
-
Description:
While building a multi-module project (X) from the command line using {{mvn
package}}, all defined modules build just fine, but assembling X itself fails
with the following error:
{quote}
[INFO]
[INFO] Building X 1.0
[INFO]
[INFO]
[INFO] --- maven-assembly-plugin:2.5.5:single (make-assembly) @ x ---
[INFO] Reading assembly descriptor: src/assembly/bin-assembly.xml
[INFO] Building tar: /bb/x/target/x-1.0-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Common . SUCCESS [ 3.180 s]
[INFO] A Service .. SUCCESS [ 3.337 s]
[INFO] B Service .. SUCCESS [ 2.186 s]
[INFO] A User Interface ... SUCCESS [ 1.331 s]
[INFO] B User Interface ... SUCCESS [ 1.380 s]
[INFO] X .. FAILURE [ 0.346 s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 19.722 s
[INFO] Finished at: 2015-07-23T16:32:34-04:00
[INFO] Final Memory: 53M/279M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (make-assembly) on
project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742' is too big ( 2097151 ). - [Help 1]
{quote}
Snippet from X multi-module POM that configures maven-assembly-plugin:
{quote}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.5.5/version
configuration
descriptors
descriptorsrc/assembly/bin-assembly.xml/descriptor
descriptorsrc/assembly/src-assembly.xml/descriptor
/descriptors
/configuration
executions
execution
idmake-assembly/id
phasepackage/phase
goals
goalsingle/goal
/goals
/execution
/executions
/plugin
{quote}
Error and stack trace:
{quote}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (make-assembly) on
project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742' is too big ( 2097151 ). - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (make-assembly) on
project X: Execution make-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: user id
'1535409742' is too big ( 2097151 ).
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
[jira] [Created] (MJAR-199) Option classifier to goal test-jar
Leo Breuss created MJAR-199: --- Summary: Option classifier to goal test-jar Key: MJAR-199 URL: https://issues.apache.org/jira/browse/MJAR-199 Project: Maven JAR Plugin Issue Type: Improvement Affects Versions: 2.6 Reporter: Leo Breuss Priority: Minor Option classifier to goal test-jar would be convenient and would provide a symmetric implementation to goal jar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
