[jira] (MDEP-230) Performance is really bad for large artifacts
[
https://jira.codehaus.org/browse/MDEP-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316942#comment-316942
]
Ivan commented on MDEP-230:
---
My guess is that the implementation of "chmod" is 'inefficient', it seems to
fallback to a Runtime.exec("chmod...") for each file.
(If not using a Java7 jvm)
Here is a jstack:
"main" prio=10 tid=0x4106b000 nid=0x342c in Object.wait()
[0x408fd000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x2aab5b31c890> (a java.lang.UNIXProcess$Gate)
at java.lang.Object.wait(Object.java:485)
at java.lang.UNIXProcess$Gate.waitForExit(UNIXProcess.java:64)
- locked <0x2aab5b31c890> (a java.lang.UNIXProcess$Gate)
at java.lang.UNIXProcess.(UNIXProcess.java:145)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
at java.lang.Runtime.exec(Runtime.java:593)
at
org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:651)
at
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLineAsCallable(CommandLineUtils.java:140)
at
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:111)
at
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:79)
at
org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:92)
at
org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFile(AbstractZipUnArchiver.java:238)
at
org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFileIfIncluded(AbstractZipUnArchiver.java:185)
at
org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.execute(AbstractZipUnArchiver.java:149)
at
org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:119)
at
org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:266)
at
org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:91)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
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:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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)
> Performance is really bad for large artifacts
> -
>
> Key: MDEP-230
> URL: https://jira.codehaus.org/browse/MDEP-230
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: unpack
>Affects Versions: 2.1
> Environment: linux
>Reporter: Jason Chaffee
>
> I have a 300mb tar.gz file that I need to unpack for one of my builds. I
> takes over 10 minutes to unpack with the unpack goal. If I do it on the
> cmd-line it takes less than 1 minute.
--
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-230) Performance is really bad for large artifacts
[
https://jira.codehaus.org/browse/MDEP-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316942#comment-316942
]
Ivan edited comment on MDEP-230 at 1/8/13 3:46 AM:
---
My guess is that the implementation of
org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod is cpu consuming.
Indeed it seems to fallback to a Runtime.exec("chmod...") for each file.
(If not using a Java7 jvm)
Here is a jstack:
"main" prio=10 tid=0x4106b000 nid=0x342c in Object.wait()
[0x408fd000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x2aab5b31c890> (a java.lang.UNIXProcess$Gate)
at java.lang.Object.wait(Object.java:485)
at java.lang.UNIXProcess$Gate.waitForExit(UNIXProcess.java:64)
- locked <0x2aab5b31c890> (a java.lang.UNIXProcess$Gate)
at java.lang.UNIXProcess.(UNIXProcess.java:145)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
at java.lang.Runtime.exec(Runtime.java:593)
at
org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:651)
at
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLineAsCallable(CommandLineUtils.java:140)
at
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:111)
at
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:79)
at
org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:92)
at
org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFile(AbstractZipUnArchiver.java:238)
at
org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFileIfIncluded(AbstractZipUnArchiver.java:185)
at
org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.execute(AbstractZipUnArchiver.java:149)
at
org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:119)
at
org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:266)
at
org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:91)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
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:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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)
was (Author: ebann):
My guess is that the implementation of "chmod" is 'inefficient', it seems
to fallback to a Runtime.exec("chmod...") for each file.
(If not using a Java7 jvm)
Here is a jstack:
"main" prio=10 tid=0x4106b000 nid=0x342c in Object.wait()
[0x408fd000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x2aab5b31c890> (a java.lang.UNIXProcess$Gate)
at java.lang.Object.wait(Object.java:485)
at java.lang.UNIXProcess$Gate.waitForExit(UNIXProcess.java:64)
- locked <0x2aab5b31c890> (a java.lang.UNIXProcess$Gate)
at java.lang.UNIXProcess.(UNIXProcess.java:145)
at java.lang.ProcessImpl.start(ProcessImpl
[jira] (MDOAP-38) property value not interpolated
Simone Tripodi created MDOAP-38:
---
Summary: property value not interpolated
Key: MDOAP-38
URL: https://jira.codehaus.org/browse/MDOAP-38
Project: Maven 2.x DOAP Plugin
Issue Type: Bug
Affects Versions: 1.1
Reporter: Simone Tripodi
I am trying to use the DOAP-plugin in [Apache
Onami|http://svn.apache.org/repos/asf/incubator/onami/trunk/parent/pom.xml] and
noticed that {{shortdesc}} property is not interpolated.
If not specified, the plugin terminates with an error:
{code}
[ERROR] A parameter is required by ASF.
{code}
If I specify as
{code}
${project.description}
{code}
it terminates with the same error message:
{code}
[ERROR] A parameter is required by ASF.
{code}
If I set a value, such as
{code}
Bazinga!
{code}
It goes ok.
Ah, and yes, the ${project.description} property is specified in the pom :P
--
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] (MDOAP-38) property value not interpolated
[
https://jira.codehaus.org/browse/MDOAP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316952#comment-316952
]
Simone Tripodi commented on MDOAP-38:
-
This is my environment:
{code}
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /Applications/apache-maven-3.0.4
Java version: 1.6.0_37, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.8.2", arch: "x86_64", family: "mac"
{code}
> property value not interpolated
> ---
>
> Key: MDOAP-38
> URL: https://jira.codehaus.org/browse/MDOAP-38
> Project: Maven 2.x DOAP Plugin
> Issue Type: Bug
>Affects Versions: 1.1
>Reporter: Simone Tripodi
>
> I am trying to use the DOAP-plugin in [Apache
> Onami|http://svn.apache.org/repos/asf/incubator/onami/trunk/parent/pom.xml]
> and noticed that {{shortdesc}} property is not interpolated.
> If not specified, the plugin terminates with an error:
> {code}
> [ERROR] A parameter is required by
> ASF.
> {code}
> If I specify as
> {code}
>
> ${project.description}
>
> {code}
> it terminates with the same error message:
> {code}
> [ERROR] A parameter is required by
> ASF.
> {code}
> If I set a value, such as
> {code}
>
> Bazinga!
>
> {code}
> It goes ok.
> Ah, and yes, the ${project.description} property is specified in the pom :P
--
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] (MSITE-679) tag within in maven-site-plugin causes NPE
Martin Gainty created MSITE-679: --- Summary: tag within in maven-site-plugin causes NPE Key: MSITE-679 URL: https://jira.codehaus.org/browse/MSITE-679 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: Maven 3 Affects Versions: 3.0-beta-3 Environment: JDK 1.6 mvn 3.0.2 Reporter: Martin Gainty -- 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] (MSITE-679) tag within in maven-site-plugin causes NPE
[ https://jira.codehaus.org/browse/MSITE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316959#comment-316959 ] Martin Gainty commented on MSITE-679: - tag in causes NPE org.apache.maven.plugins maven-site-plugin 3.0-beta-3 org.apache.maven.plugins maven-surefire-plugin 2.9 ...anything within the executions tag causes either ComponentNotFoundException and or NPEs... works (when reportPlugins plugin does not contain iteration tag) org.apache.maven.plugins maven-site-plugin 3.0-beta-3 org.apache.maven.plugins maven-surefire-report-plugin 2.12.4 never C:maven-plugin/maven-android-plugin/trunk/src/test C:/maven-plugin/maven-android-plugin/trunk/target/test-classes -Xmx3192m -XX:MaxPermSize=3192m **/*Test.java > tag within in maven-site-plugin causes NPE > --- > > Key: MSITE-679 > URL: https://jira.codehaus.org/browse/MSITE-679 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3 >Affects Versions: 3.0-beta-3 > Environment: JDK 1.6 mvn 3.0.2 >Reporter: Martin Gainty > -- 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] (MDOAP-38) property value not interpolated
[
https://jira.codehaus.org/browse/MDOAP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316970#comment-316970
]
Simone Tripodi commented on MDOAP-38:
-
I maybe got where my error is, I just noticed the following code snippet:
{code}
// try to get the first 10 words of the description
String sentence = StringUtils.split( shortdesc, "." )[0];
if ( StringUtils.split( sentence, " " ).length > 10 )
{
messages.addMessage( new String[] { "doapOptions", "shortdesc" }, null,
UserMessages.REQUIRED_BY_ASF_OR_RECOMMENDED );
return;
}
{code}
The error message maybe gets users confused because the value could be set but
doesn't match the requirements.
> property value not interpolated
> ---
>
> Key: MDOAP-38
> URL: https://jira.codehaus.org/browse/MDOAP-38
> Project: Maven 2.x DOAP Plugin
> Issue Type: Bug
>Affects Versions: 1.1
>Reporter: Simone Tripodi
>
> I am trying to use the DOAP-plugin in [Apache
> Onami|http://svn.apache.org/repos/asf/incubator/onami/trunk/parent/pom.xml]
> and noticed that {{shortdesc}} property is not interpolated.
> If not specified, the plugin terminates with an error:
> {code}
> [ERROR] A parameter is required by
> ASF.
> {code}
> If I specify as
> {code}
>
> ${project.description}
>
> {code}
> it terminates with the same error message:
> {code}
> [ERROR] A parameter is required by
> ASF.
> {code}
> If I set a value, such as
> {code}
>
> Bazinga!
>
> {code}
> It goes ok.
> Ah, and yes, the ${project.description} property is specified in the pom :P
--
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] (MSITE-640) Maven searches only central repository for imported dependencies
[ https://jira.codehaus.org/browse/MSITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316974#comment-316974 ] Shawn Brown commented on MSITE-640: --- It sounds like the following issue is related: http://jira.codehaus.org/browse/MSITE-663 I spent some time stepping through the site plugin code while troubleshooting that issue, and the root cause seemed to be that the site plugin wasn't giving Maven the full list of repositories to search. > Maven searches only central repository for imported dependencies > > > Key: MSITE-640 > URL: https://jira.codehaus.org/browse/MSITE-640 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3 >Affects Versions: 3.0 > Environment: Windows 7 >Reporter: Markus Tippmann > Attachments: stacktrace.txt > > > We are using dependencyManagement with "import" scope like described here: > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies > Problem occurs only at site generation, not at build time, where it works > perfectly. > The site plugin tries to find the imported artifacts, but searches only the > central repository and ignores the repositories in settings.xml > configuration. Mirror settings work, if "central" is mirrored, but > dependencies need to be resolved from two repositories, so one mirror does > not help here. > I try to attach the relevant parts of the stacktrace. -- 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] (MSITE-663) Build fails with message "Unable to read local module-POM"
[ https://jira.codehaus.org/browse/MSITE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316975#comment-316975 ] Shawn Brown commented on MSITE-663: --- This issue may be related: http://jira.codehaus.org/browse/MSITE-640 > Build fails with message "Unable to read local module-POM" > -- > > Key: MSITE-663 > URL: https://jira.codehaus.org/browse/MSITE-663 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0, 3.1, 3.2 > Environment: MacOS, Cygwin, Linux >Reporter: Shawn Brown > > Copied from > http://stackoverflow.com/questions/11260717/non-resolvable-parent-pom-when-building-maven-3-project-site: > == > I am currently facing the following problem with Maven 3 when I am trying to > build the site. I will appreciate you help on this. > mvn clean site > .. > [INFO] Reactor Summary: > [INFO] > [INFO] Project A . SUCCESS [15.383s] > [INFO] Project B . SUCCESS [2.232s] > [INFO] My Site ... FAILURE [0.105s] > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 24.769s > [INFO] Finished at: Fri Jun 29 14:26:04 AMT 2012 > [INFO] Final Memory: 18M/150M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.1:site (default-site) on project > site: SiteToolException: Unable to read local module-POM: 1 problem was > encountered while building the effective model for my.com:projA:0.1-SNAPSHOT > [ERROR] [FATAL] Non-resolvable parent POM: Could not find artifact > my.com:parent-pom:pom:0.1-SNAPSHOT and 'parent.relativePath' points at no > local POM @ line 12, column 13 > [ERROR] for project my.com:projA:0.1-SNAPSHOT > . > First here is the configuration: > Apache Maven 3.0.4 (r1232337; 2012-01-17 12:44:56+0400) > Java version: 1.7.0_04, vendor: Oracle Corporation > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.7.4", arch: "x86_64", family: "mac" > Nexus repository: 2.0.6 > The parent POM: > 4.0.0 > Parent POM > my.com > parent-pom > 0.1-SNAPSHOT > pom > > > > > org.apache.maven.plugins > maven-site-plugin > 3.1 > > > > org.apache.maven.plugins > > maven-project-info-reports-plugin > 2.4 > > > > > > > > The aggregation project pom: > 4.0.0 > My Site > my.com > site > 0.1-SNAPSHOT > pom > > my.com > parent-pom > 0.1-SNAPSHOT > > > > projA > projB > > The pom of Project A: > 4.0.0 > Project A > my.com > projA > 0.1-SNAPSHOT > > my.com > parent-pom > 0.1-SNAPSHOT > > > The pom of Project B: > 4.0.0 > Project B > my.com > projB > 0.1-SNAPSHOT > > my.com > parent-pom > 0.1-SNAPSHOT > > > Here is the structure of the folder where I run "mvn clean site": > ./pom.xml (aggregation project) > ./projA/pom.xml (Project A) > ./projB/pom.xml (Project B) > parent-pom is successfully deployed to NEXUS repository before the execution > of mvn clean site with following command: > mvn deploy > -DaltDeploymentRepository=snapshots::default::http://MyServer:8081/nexus/content/repositories/snapshots > And finally the problem itself: > When I run mvn clean site right after the deployment of parent-pom site is > built successfully. If I delete the folder (with its content) "my" (it > contains the parent-pom) from the local repository (~/.m2/repository) and > then try to build the site with mvn clean site I am getting the error > described at the beginning. Actually Maven downloads the parent-pom from the > NEXUS. I have compared the downloaded files and files which have been > generated after the deployment and have realized that few are missing, for > instance maven-metadata-local.xml near to "0.1-SNAPSHOT" folder. > So when I am trying to run the site building job from Jenkins I am getting > the error described above, because the parent-pom is not deployed from the > machine where Jenkins run. > == -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA adm
[jira] (MRELEASE-818) release:perform ignores localCheckout=true
[ https://jira.codehaus.org/browse/MRELEASE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MRELEASE-818: --- Assignee: Robert Scholte > release:perform ignores localCheckout=true > -- > > Key: MRELEASE-818 > URL: https://jira.codehaus.org/browse/MRELEASE-818 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Tim Kettler >Assignee: Robert Scholte > Attachments: releasetest.tar.gz > > > When invoking mvn release:perform on a project in a git repositoty the > release plugin always tries to do a remote checkout, ignoring the > 'localCheckout' configuration option. Fixing the version of the plugin to > 2.3.2 solves this. This looks like a regression. > Invoking release:prepare and release:perform on the supplied testproject > shows the issue. -- 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] (MANTTASKS-204) Version 2.1.1 of mvn task without maven install still uses Maven 2.0.10
[
https://jira.codehaus.org/browse/MANTTASKS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316983#comment-316983
]
Justin Wunderle commented on MANTTASKS-204:
---
This is causing a build to fail for me too, due to bad interpolation in Maven
2.0.x. One of my dependencies' parent poms contains something like:
{code:xml}
http://example.com/?foo=bar&baz=quux
${test.property}
{code}
Which causes an exception "Cannot read project model from interpolating filter
of serialized version." in 2.0.x and is fine in 2.2.x
> Version 2.1.1 of mvn task without maven install still uses Maven 2.0.10
> ---
>
> Key: MANTTASKS-204
> URL: https://jira.codehaus.org/browse/MANTTASKS-204
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: mvn task
>Affects Versions: 2.1.1
> Environment: Mac OSX 10.6.4
>Reporter: Kelly Davis
>
> I am running the mvn task and it appears that version 2.1.1 of the Maven Ant
> Tasks is still using version 2.0.10 of Maven when you don't specify a local
> installation.
>
>
>
> results in:
> [artifact:mvn] Maven version: 2.0.10
> [artifact:mvn] Java version: 1.6.0_22
> [artifact:mvn] OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family:
> "mac"
> The current docs indicate that it should be using 2.2.1.
--
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] (MSITE-663) Build fails with message "Unable to read local module-POM"
[
https://jira.codehaus.org/browse/MSITE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MSITE-663:
-
Description:
Copied from
http://stackoverflow.com/questions/11260717/non-resolvable-parent-pom-when-building-maven-3-project-site:
==
I am currently facing the following problem with Maven 3 when I am trying to
build the site. I will appreciate you help on this.
{{mvn clean site}}
{noformat}
..
[INFO] Reactor Summary:
[INFO]
[INFO] Project A . SUCCESS [15.383s]
[INFO] Project B . SUCCESS [2.232s]
[INFO] My Site ... FAILURE [0.105s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 24.769s
[INFO] Finished at: Fri Jun 29 14:26:04 AMT 2012
[INFO] Final Memory: 18M/150M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.1:site (default-site) on project
site: SiteToolException: Unable to read local module-POM: 1 problem was
encountered while building the effective model for my.com:projA:0.1-SNAPSHOT
[ERROR] [FATAL] Non-resolvable parent POM: Could not find artifact
my.com:parent-pom:pom:0.1-SNAPSHOT and 'parent.relativePath' points at no local
POM @ line 12, column 13
[ERROR] for project my.com:projA:0.1-SNAPSHOT
.
{noformat}
First here is the configuration:
{noformat}
Apache Maven 3.0.4 (r1232337; 2012-01-17 12:44:56+0400)
Java version: 1.7.0_04, vendor: Oracle Corporation
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.7.4", arch: "x86_64", family: "mac"
Nexus repository: 2.0.6
{noformat}
The parent POM:
{code:xml}
4.0.0
Parent POM
my.com
parent-pom
0.1-SNAPSHOT
pom
org.apache.maven.plugins
maven-site-plugin
3.1
org.apache.maven.plugins
maven-project-info-reports-plugin
2.4
{code}
The aggregation project pom:
{code:xml}
4.0.0
My Site
my.com
site
0.1-SNAPSHOT
pom
my.com
parent-pom
0.1-SNAPSHOT
projA
projB
{code}
The pom of Project A:
{code:xml}
4.0.0
Project A
my.com
projA
0.1-SNAPSHOT
my.com
parent-pom
0.1-SNAPSHOT
{code}
The pom of Project B:
{code:xml}
4.0.0
Project B
my.com
projB
0.1-SNAPSHOT
my.com
parent-pom
0.1-SNAPSHOT
{code}
Here is the structure of the folder where I run "mvn clean site":
{noformat}
./pom.xml (aggregation project)
./projA/pom.xml (Project A)
./projB/pom.xml (Project B)
{noformat}
parent-pom is successfully deployed to NEXUS repository before the execution of
{{mvn clean site}} with following command:
{{mvn deploy
-DaltDeploymentRepository=snapshots::default::http://MyServer:8081/nexus/content/repositories/snapshots}}
And finally the problem itself:
When I run {{mvn clean site}} right after the deployment of parent-pom site is
built successfully. If I delete the folder (with its content) "my" (it contains
the parent-pom) from the local repository (~/.m2/repository) and then try to
build the site with {{mvn clean site}} I am getting the error described at the
beginning. Actually Maven downloads the parent-pom from the NEXUS. I have
compared the downloaded files and files which have been generated after the
deployment and have realized that few are missing, for instance
maven-metadata-local.xml near to "0.1-SNAPSHOT" folder.
So when I am trying to run the site building job from Jenkins I am getting the
error described above, because the parent-pom is not deployed from the machine
where Jenkins run.
==
was:
Copied from
http://stackoverflow.com/questions/11260717/non-resolvable-parent-pom-when-building-maven-3-project-site:
==
I am currently facing the following problem with Maven 3 when I am trying to
build the site. I will appreciate you help on this.
mvn clean site
..
[INFO] Reactor Summary:
[INFO]
[INFO] Project A . SUCCESS [15.383s]
[INFO] Project B . SUCCESS [2.232s]
[INFO] My Site ... FAILURE [0.105s]
[INFO]
[INFO] BUILD FAILURE
[INFO] ---
[jira] (MRELEASE-818) release:perform ignores localCheckout=true
[ https://jira.codehaus.org/browse/MRELEASE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-818. --- Resolution: Fixed Fix Version/s: 2.4.1 Fixed in [r1430485|http://svn.apache.org/viewvc?rev=1430485&view=rev] > release:perform ignores localCheckout=true > -- > > Key: MRELEASE-818 > URL: https://jira.codehaus.org/browse/MRELEASE-818 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Tim Kettler >Assignee: Robert Scholte > Fix For: 2.4.1 > > Attachments: releasetest.tar.gz > > > When invoking mvn release:perform on a project in a git repositoty the > release plugin always tries to do a remote checkout, ignoring the > 'localCheckout' configuration option. Fixing the version of the plugin to > 2.3.2 solves this. This looks like a regression. > Invoking release:prepare and release:perform on the supplied testproject > shows the issue. -- 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] (SUREFIRE-946) Maven hangs on SIGTERM when using Surefire forking (CommandLineUtils.ProcessHook)
[
https://jira.codehaus.org/browse/SUREFIRE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316986#comment-316986
]
Jesse Glick commented on SUREFIRE-946:
--
Proposed fix works in my case at least.
FYI my test case is: https://github.com/jenkinsci/jenkins/pull/667 (just edit
root {{pom.xml}} to use {{2.14-SNAPSHOT}} then run {{mvn -DskipTests install &&
mvn -f test/pom.xml surefire:test}} and press Ctrl-C after some tests have
started)
> Maven hangs on SIGTERM when using Surefire forking
> (CommandLineUtils.ProcessHook)
> -
>
> Key: SUREFIRE-946
> URL: https://jira.codehaus.org/browse/SUREFIRE-946
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Jesse Glick
> Attachments: stack.txt, SUREFIRE-946.patch
>
>
> Java 7u7, Surefire with JUnit {{forkMode="perthread"}} + {{threadCount="1"}}
> + {{reuseForks="true"}}. After pressing Ctrl-C to stop the Maven test run,
> the process hangs and must be killed with SIGKILL. From the thread dump,
> {{CommandLineUtils.ProcessHook}} and {{StreamFeeder}} look responsible.
--
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] (SUREFIRE-946) Maven hangs on SIGTERM when using Surefire forking (CommandLineUtils.ProcessHook)
[
https://jira.codehaus.org/browse/SUREFIRE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316987#comment-316987
]
Andreas Gudian commented on SUREFIRE-946:
-
Great, thanks for your test.
Then for {{reuseForks=true}} the crash detection and behaviour when terminating
the main process now at least works just as good or bad as for the other forked
test executions in 2.13.4.
> Maven hangs on SIGTERM when using Surefire forking
> (CommandLineUtils.ProcessHook)
> -
>
> Key: SUREFIRE-946
> URL: https://jira.codehaus.org/browse/SUREFIRE-946
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Jesse Glick
> Attachments: stack.txt, SUREFIRE-946.patch
>
>
> Java 7u7, Surefire with JUnit {{forkMode="perthread"}} + {{threadCount="1"}}
> + {{reuseForks="true"}}. After pressing Ctrl-C to stop the Maven test run,
> the process hangs and must be killed with SIGKILL. From the thread dump,
> {{CommandLineUtils.ProcessHook}} and {{StreamFeeder}} look responsible.
--
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] (MDOAP-38) too long value provide better error message
[
https://jira.codehaus.org/browse/MDOAP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MDOAP-38:
--
Summary: too long value provide better error message (was:
property value not interpolated)
> too long value provide better error message
> ---
>
> Key: MDOAP-38
> URL: https://jira.codehaus.org/browse/MDOAP-38
> Project: Maven 2.x DOAP Plugin
> Issue Type: Bug
>Affects Versions: 1.1
>Reporter: Simone Tripodi
>
> I am trying to use the DOAP-plugin in [Apache
> Onami|http://svn.apache.org/repos/asf/incubator/onami/trunk/parent/pom.xml]
> and noticed that {{shortdesc}} property is not interpolated.
> If not specified, the plugin terminates with an error:
> {code}
> [ERROR] A parameter is required by
> ASF.
> {code}
> If I specify as
> {code}
>
> ${project.description}
>
> {code}
> it terminates with the same error message:
> {code}
> [ERROR] A parameter is required by
> ASF.
> {code}
> If I set a value, such as
> {code}
>
> Bazinga!
>
> {code}
> It goes ok.
> Ah, and yes, the ${project.description} property is specified in the pom :P
--
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] (MDOAP-38) too long value provide better error message
[
https://jira.codehaus.org/browse/MDOAP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MDOAP-38.
-
Resolution: Fixed
Fix Version/s: 1.2
Assignee: Olivier Lamy
fixed.
message will be "The first is too long
maximum words number is 10."
> too long value provide better error message
> ---
>
> Key: MDOAP-38
> URL: https://jira.codehaus.org/browse/MDOAP-38
> Project: Maven 2.x DOAP Plugin
> Issue Type: Bug
>Affects Versions: 1.1
>Reporter: Simone Tripodi
>Assignee: Olivier Lamy
> Fix For: 1.2
>
>
> I am trying to use the DOAP-plugin in [Apache
> Onami|http://svn.apache.org/repos/asf/incubator/onami/trunk/parent/pom.xml]
> and noticed that {{shortdesc}} property is not interpolated.
> If not specified, the plugin terminates with an error:
> {code}
> [ERROR] A parameter is required by
> ASF.
> {code}
> If I specify as
> {code}
>
> ${project.description}
>
> {code}
> it terminates with the same error message:
> {code}
> [ERROR] A parameter is required by
> ASF.
> {code}
> If I set a value, such as
> {code}
>
> Bazinga!
>
> {code}
> It goes ok.
> Ah, and yes, the ${project.description} property is specified in the pom :P
--
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] (MNG-5420) Need to be able to specify running a specific execution by id
Sebastien Tardif created MNG-5420: - Summary: Need to be able to specify running a specific execution by id Key: MNG-5420 URL: https://jira.codehaus.org/browse/MNG-5420 Project: Maven 2 & 3 Issue Type: Improvement Affects Versions: 3.0.4 Reporter: Sebastien Tardif The limitation of not been able to specify executing an execution id of a plug-in is often mentioned. It's very obvious to be a missing feature when you are using a plug-ins that is generic like maven-antrun-plugin or maven*groovy. In other words, I may have a tiny ant script deleting some folders, then still also need the maven-antrun-plugin for other things like preparing a DB. It's insane to be stuck with only default-cli mechanism when all my "execution"s already have an identifier. Instead of been stuck with antrun:run, I should be able to do antrun:myExecutionId -- 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
