[jira] Created: (MNG-4706) Multithreaded building can create bad files for downloaded artifacts in local repository
Multithreaded building can create bad files for downloaded artifacts in local repository Key: MNG-4706 URL: http://jira.codehaus.org/browse/MNG-4706 Project: Maven 2 & 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0-beta-1 Reporter: Kristian Rosenvold Within a parallel build, modules A and B can start at the same time and decide at the same time that they need to download artifact X. Since X is not available locally, both can start download of X. Both will download X and both will try to write the file for X to disk. On Windows platforms, one of them can fail with file locking problems. On Unixes the contents of the written file can be non-deterministic. This issue is related to MNG-2802 in the sense that it can create a corrupted artifact file in the local repository, and it can happen to ANY file written. But as opposed to MNG-2802 the synhronization needed to fix this issue is basically only within a single running maven process, so regular java mechanisms can apply, whereas MNG-2802 probably needs to use a totally different solution space. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-519) release plugin fails on version ranges
[ http://jira.codehaus.org/browse/MRELEASE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224996#action_224996 ] Jacob Briggs commented on MRELEASE-519: --- We've been hit by the bug whilst attempting to upgrade to release plugin 2.0. 2.0-beta-8 does *not* have this issue, so it seems to affect the later beta and the final. The presence of the artifact in the range locally or remotely does not affect the behaviour. > release plugin fails on version ranges > -- > > Key: MRELEASE-519 > URL: http://jira.codehaus.org/browse/MRELEASE-519 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0 > Environment: Mac OS X 10.6, maven 2.2.1 >Reporter: Stephen Cooper >Priority: Critical > > I have the following dependency in my pom.xml > >com.ften.protocols >protocols >[3.0.0,) >compile > > I downloaded the source for maven-release 2.0 and installed locally. > If I specify 2.0-beta-9, then mvn release:perform functions as it should. If > I specify maven-release-plugin version 2.0, I get the following error: > [INFO] Checking dependencies and plugins for snapshots ... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for com.ften.protocols:protocols > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > com.ften.protocols:protocols > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) > at > org.apache.maven.artifact.DefaultArtifact.isSnapshot(DefaultArtifact.java:562) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-659) eclipse-plugin does not create .classpath and .project files for projects with packaging pom
eclipse-plugin does not create .classpath and .project files for projects with packaging pom Key: MECLIPSE-659 URL: http://jira.codehaus.org/browse/MECLIPSE-659 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Multi-projects Affects Versions: 2.8 Environment: any Reporter: Daniele Dellafiore mvn eclipse:eclipse does not generate eclipse .project and .classpath files from any pom.xml file that has packaging set to POM. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4705) parent pom doesn't get resolved if it is contained in a submodule
[
http://jira.codehaus.org/browse/MNG-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4705.
--
Resolution: Not A Bug
Assignee: Benjamin Bentmann
The POMs are missing the proper {{}} specs for Maven to resolve
the parents.
> parent pom doesn't get resolved if it is contained in a submodule
> -
>
> Key: MNG-4705
> URL: http://jira.codehaus.org/browse/MNG-4705
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Reactor and workspace
>Affects Versions: 3.0-beta-1
>Reporter: Mark Struberg
>Assignee: Benjamin Bentmann
> Attachments: reactorbug-testprj.zip
>
>
> I have the following situation in my project which used to work in maven 2.x
> (2.0.9, 2.1.1):
> I have a 'parents' module with subprojects for frontend, backend etc. Those
> contain only parent poms containing common settings for these kind of projects
> The real frontend wars and backend jars are in separate modules for own areas
> which reference the apropriate frontend-parent or backend-parent from the
> parents module.
> This works well in maven2 but fails to resolve the parent poms in 3.0-beta-1
> The attached sample project will show the problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4705) parent pom doesn't get resolved if it is contained in a submodule
parent pom doesn't get resolved if it is contained in a submodule - Key: MNG-4705 URL: http://jira.codehaus.org/browse/MNG-4705 Project: Maven 2 & 3 Issue Type: Bug Components: Reactor and workspace Affects Versions: 3.0-beta-1 Reporter: Mark Struberg Attachments: reactorbug-testprj.zip I have the following situation in my project which used to work in maven 2.x (2.0.9, 2.1.1): I have a 'parents' module with subprojects for frontend, backend etc. Those contain only parent poms containing common settings for these kind of projects The real frontend wars and backend jars are in separate modules for own areas which reference the apropriate frontend-parent or backend-parent from the parents module. This works well in maven2 but fails to resolve the parent poms in 3.0-beta-1 The attached sample project will show the problems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-128) SCM properties being replaced during release:perform
[
http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224970#action_224970
]
Lars Fischer commented on MRELEASE-128:
---
Hello,
is there a plan to fix this issue?
Regards,
Lars
> SCM properties being replaced during release:perform
>
>
> Key: MRELEASE-128
> URL: http://jira.codehaus.org/browse/MRELEASE-128
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
>Reporter: Craig Dickson
>Assignee: Emmanuel Venisse
>Priority: Critical
> Fix For: 2.1
>
> Attachments: after-release-perform-pom.xml,
> after-release-prepre-pom.xml, MNG-128-maven-release-manager.patch,
> MRELEASE-128_cvs_hack_RewritePomsForDevelopmentPhase.java.patch,
> original-pom.xml
>
>
> The section of a pom in CVS for a pom archetype project looks like this
> prior to executing release:prepare :
>
> ${base.cvs.url}:commons-maven/uber-pom
>
> ${base.cvs.url}:commons-maven/uber-pom
> ${base.viewcvs.url}/commons-maven/uber-pom
>
> Then after executing release:prepare, the pom in CVS looks like this (new
> tag is only difference):
>
> ${base.cvs.url}:commons-maven/uber-pom
>
> ${base.cvs.url}:commons-maven/uber-pom
> ${base.viewcvs.url}/commons-maven/uber-pom
> R-1_7
>
> Then after executing release:perform, the pom looks like this in CVS:
>
>
> scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom
>
> scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom
>
> http://behrcvs.masco-coatings.com/cgi-bin/viewcvs.cgi/commons-maven/uber-pom
>
> Notice that the properties that were there for the base URLs for CVS and
> ViewCVS have been replaced with literal values.
> No other properties in the POM are being replaced
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2787) JdbcHelper 0.3.1 Upload Request
JdbcHelper 0.3.1 Upload Request --- Key: MAVENUPLOAD-2787 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2787 Project: Maven Upload Requests Issue Type: Wish Reporter: Erdinc YILMAZEL Attachments: jdbc-helper-0.3.1-bundle.jar Inspired by Spring Jdbctemplate and Commons Dbutils projects, JdbcHelper? is a very small library for helping the developers code common jdbc operations. JdbcHelper? is very lightweight. It is only ~70K and it has no external dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-557) ERROR:gitosis.serve.main:Arguments to command look dangerous (apparently)
ERROR:gitosis.serve.main:Arguments to command look dangerous (apparently) - Key: SCM-557 URL: http://jira.codehaus.org/browse/SCM-557 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Affects Versions: 1.3 Reporter: Paul Hammant Trying to run the release plugin for a git project http://xircles.codehaus.org/projects/paranamer/repo/git/repo (branch real_asm). In the prepare phase it barfs like so : [INFO] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] [INFO] [INFO] Total time: 11 seconds [INFO] [INFO] Finished at: Thu Jun 10 05:21:23 CDT 2010 [INFO] [INFO] Final Memory: 39M/81M [INFO] [INFO] [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /scm/oss/paranamer-git/paranamer && git add -- pom.xml [INFO] Working directory: /scm/oss/paranamer-git/paranamer [INFO] Executing: /bin/sh -c cd /scm/oss/paranamer-git/paranamer && git status [INFO] Working directory: /scm/oss/paranamer-git/paranamer [DEBUG] # On branch real_asm [DEBUG] # Changes to be committed: [DEBUG] # (use "git reset HEAD ..." to unstage) [DEBUG] # [DEBUG] # modified: pom.xml [DEBUG] # [DEBUG] # Untracked files: [DEBUG] # (use "git add ..." to include in what will be committed) [DEBUG] # [DEBUG] # pom.xml.releaseBackup [DEBUG] # release.properties [INFO] Executing: /bin/sh -c cd /scm/oss/paranamer-git/paranamer && git commit --verbose -F /var/folders/qb/qbAjORvlEIKOmBNFQArSsTI/-Tmp-/maven-scm-964404670.commit pom.xml [INFO] Working directory: /scm/oss/paranamer-git/paranamer [INFO] Executing: /bin/sh -c cd /scm/oss/paranamer-git/paranamer && git symbolic-ref HEAD [INFO] Working directory: /scm/oss/paranamer-git/paranamer [INFO] Executing: /bin/sh -c cd /scm/oss/paranamer-git/paranamer && git push ssh://g...@git.codehaus.org/paranamer.git/ real_asm:real_asm [INFO] Working directory: /scm/oss/paranamer-git/paranamer [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: The git-push command failed. Command output: ## Unauthorized access to this system (codehaus01) is forbidden and will be prosecuted by law. By accessing this system, you agree that your actions may be monitored if unauthorized usage is suspected. ## ERROR:gitosis.serve.main:Arguments to command look dangerous fatal: The remote end hung up unexpectedly [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Unable to commit files Provider message: The git-push command failed. Command output: ## Unauthorized access to this system (codehaus01) is forbidden and will be prosecuted by law. By accessing this system, you agree that your actions may be monitored if unauthorized usage is suspected. ## ERROR:gitosis.serve.main:Arguments to command look dangerous fatal: The remote end hung up unexpectedly at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds
[jira] Created: (SCM-556) Vague error message from git-scm-plugin prevents release:prepare
Vague error message from git-scm-plugin prevents release:prepare Key: SCM-556 URL: http://jira.codehaus.org/browse/SCM-556 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Affects Versions: 1.3 Reporter: Paul Hammant "Unable to commit files" is vague I think. The only special thing I'm trying to do is commit from a branch that is not master. Yes, the branch has remote representation (fully pushed) as well as local. For the record the project is paranamer on codehaus, which was flipped from Subversion to Git. http://xircles.codehaus.org/projects/paranamer/repo/git/repo real_asm branch. -e -X console output : [DEBUG] # On branch real_asm [DEBUG] # Untracked files: [DEBUG] # (use "git add ..." to include in what will be committed) [DEBUG] # [DEBUG] # pom.xml.releaseBackup [DEBUG] # release.properties [DEBUG] nothing added to commit but untracked files present (use "git add" to track) [INFO] nothing added to commit but untracked files present (use "git add" to track) [INFO] Executing: /bin/sh -c cd /scm/oss/paranamer-git/paranamer && git commit --verbose -F /var/folders/qb/qbAjORvlEIKOmBNFQArSsTI/-Tmp-/maven-scm-890989155.commit pom.xml [INFO] Working directory: /scm/oss/paranamer-git/paranamer [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: The git-commit command failed. Command output: [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Unable to commit files Provider message: The git-commit command failed. Command output: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files Provider message: The git-commit command failed. Command output: at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:219) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to commit files Provider message: The git-commit command failed. Command output: at org.apache.maven.shared.release.phase.ScmCommitPhase.checkin(ScmCommitPhase.java:133) at org.apache.maven.shared.release.phase.ScmCommitPhase.execute(ScmCommitPhase.java:109) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103) at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211) ... 20 more [INFO] -
[jira] Commented: (MGPG-28) Should be able to use gpg2 that MacPorts will install
[ http://jira.codehaus.org/browse/MGPG-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224827#action_224827 ] Benjamin Bentmann commented on MGPG-28: --- Why can't you set https://maven.apache.org/plugins/maven-gpg-plugin/sign-mojo.html#executable to "gpg2"? > Should be able to use gpg2 that MacPorts will install > - > > Key: MGPG-28 > URL: http://jira.codehaus.org/browse/MGPG-28 > Project: Maven 2.x GPG Plugin > Issue Type: New Feature >Reporter: Paul Hammant > > On Mac, should be able to use gpg2 or gpg. > paul$ gpg --version > gpg (GnuPG) 1.4.10 > Copyright (C) 2008 Free Software Foundation, Inc. > paul$ gpg2 --version > gpg (GnuPG) 2.0.13 > libgcrypt 1.4.4 > Copyright (C) 2009 Free Software Foundation, Inc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MGPG-28) Should be able to use gpg2 that MacPorts will install
Should be able to use gpg2 that MacPorts will install - Key: MGPG-28 URL: http://jira.codehaus.org/browse/MGPG-28 Project: Maven 2.x GPG Plugin Issue Type: New Feature Reporter: Paul Hammant On Mac, should be able to use gpg2 or gpg. paul$ gpg --version gpg (GnuPG) 1.4.10 Copyright (C) 2008 Free Software Foundation, Inc. paul$ gpg2 --version gpg (GnuPG) 2.0.13 libgcrypt 1.4.4 Copyright (C) 2009 Free Software Foundation, Inc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-487) Introduce ${artifact.properties} counterpart for ${project.properties}
Introduce ${artifact.properties} counterpart for ${project.properties}
--
Key: MASSEMBLY-487
URL: http://jira.codehaus.org/browse/MASSEMBLY-487
Project: Maven 2.x Assembly Plugin
Issue Type: Improvement
Affects Versions: 2.2-beta-5
Reporter: Andreas Sewe
At the moment, interpolation in {{outputFileNameMapping}} allows access to the
POM properties of the artifact in a {{dependencySet}} by means of
{{${artifact.*}}}. Access to the (system) properties defined by the artifact's
POM, however, is impossible; there is no {{${artifact.properties}}} counterpart
for {{${project.properties}}}, even though it would solve some real-world
problems for which no easy workaround is possible:
http://www.mail-archive.com/us...@maven.apache.org/msg109792.html.
That being said, this inconsistency is at the very least confusing, in
particular as the documentation's distinction between POM properties and
(system) properties is quite subtle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4585) surefire-junit-2.4.3 artifact not available with Maven 3 Alpha-6
[
http://jira.codehaus.org/browse/MNG-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224822#action_224822
]
Jean-Sébastien Scrève commented on MNG-4585:
Adding this dependency will solve the issue :
org.apache.maven.surefire
surefire-junit4
2.4.3
test
It will download surefire-junit4 instead of surefire-junit
Kind of weird...
Regards,
Jean-Sébastien Scrève
> surefire-junit-2.4.3 artifact not available with Maven 3 Alpha-6
>
>
> Key: MNG-4585
> URL: http://jira.codehaus.org/browse/MNG-4585
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0-alpha-6
> Environment: windows XP.
> maven-3.0-alpha-6
> jdk 1.5.0.22
>Reporter: Pierre Devreux
>Assignee: Benjamin Bentmann
>Priority: Critical
>
> When building a project with in plugin management :
> {noformat}
>
>org.apache.maven.plugins
>maven-surefire-plugin
>2.4.3
>
> {noformat}
> _Maven 3 Alpha 6_ fails to download artifact :
> {noformat}
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.3/surefire-2.4.3.pom
> 8 KB downloaded at 18.4 KB/sec
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-booter/2.4.3/surefire-booter-2.4.3.pom
> 2 KB downloaded at 0.5 KB/sec
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-api/2.4.3/surefire-api-2.4.3.pom
> 3 KB downloaded at 4.6 KB/sec
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-booter/2.4.3/surefire-booter-2.4.3.jar
> 262 KB downloaded at 144.4 KB/sec
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-api/2.4.3/surefire-api-2.4.3.jar
> 504 KB downloaded at 166.2 KB/sec
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-junit/2.4.3/surefire-junit-2.4.3.pom
> [WARNING] Missing artifact metadata for
> org.apache.maven.surefire:surefire-junit:jar:2.4.3
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-junit/2.4.3/surefire-junit-2.4.3.jar
> {noformat}
> and finally
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test (default-test) on
> project xa-common: Error to resolving suref
> ire provider dependency: Error transferring file
> org.apache.maven.surefire:surefire-junit:jar:2.4.3
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
> Path to dependency:
> 1) dummy:dummy:jar:1.0
> 2) org.apache.maven.surefire:surefire-junit:jar:2.4.3: Connection
> timed out: connect
> -> [Help 1]
> {noformat}
> But building same project with _Maven 2.0.9_ works fine.
> {noformat}
> [INFO] Nothing to compile - all classes are up to date
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-booter/2.4.3/surefire-booter-2.4.3.pom
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-api/2.4.3/surefire-api-2.4.3.pom
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-booter/2.4.3/surefire-booter-2.4.3.jar
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-api/2.4.3/surefire-api-2.4.3.jar
> [INFO] [surefire:test]
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-junit/2.4.3/surefire-junit-2.4.3.pom
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-providers/2.4.3/surefire-providers-2.4.3.pom
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-junit/2.4.3/surefire-junit-2.4.3.jar
> [INFO] Surefire report directory:
> D:\workspaces\workspace_xa\xa-common-parent\xa-common-core\target\surefire-reports
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4704) Maven 3.0 beta 1 password decryption log verbosity with FileNotFoundException
[ http://jira.codehaus.org/browse/MNG-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4704. -- Resolution: Duplicate Assignee: Benjamin Bentmann See MNG-4626 instead. > Maven 3.0 beta 1 password decryption log verbosity with FileNotFoundException > - > > Key: MNG-4704 > URL: http://jira.codehaus.org/browse/MNG-4704 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Command Line, Logging >Affects Versions: 3.0-beta-1 >Reporter: Jochen Stiepel >Assignee: Benjamin Bentmann > > I'm using decrypted passwords like described here: > http://blogs.jfrog.org/2009/01/avoiding-clear-text-passwords-in-maven.html > It works fine no problem. The only problem I have now, is the log verbosity > while using mvn -X or Maven in DEBUG mode. > It prints out hundreds of stack traces and so becomes unusable. > Please change the logging of this kind of messages. Maybe log only the first > stack trace and then stop repeating this stack trace printing. > I don't have a settings-security.xml, because I don't need one and so I get > this FileNotFoundException stack trace: > [DEBUG] Failed to decrypt password for server central: > org.sonatype.plexus.components.sec.dispatcher > .SecDispatcherException: java.io.FileNotFoundException: C:\Dokumente und > Einstellungen\stijoc\.m2\ > settings-security.xml (Das System kann die angegebene Datei nicht finden) > org.sonatype.plexus.components.sec.dispatcher.SecDispatcherException: > org.sonatype.plexus.components > .sec.dispatcher.SecDispatcherException: java.io.FileNotFoundException: > C:\Dokumente und Einstellunge > n\stijoc\.m2\settings-security.xml (Das System kann die angegebene Datei > nicht finden) > at > org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher.decrypt(DefaultSecDisp > atcher.java:121) > at > org.apache.maven.settings.crypto.DefaultSettingsDecrypter.decrypt(DefaultSettingsDecrypte > r.java:106) > at > org.apache.maven.settings.crypto.DefaultSettingsDecrypter.decrypt(DefaultSettingsDecrypte > r.java:62) > at > org.apache.maven.repository.legacy.LegacyRepositorySystem.injectAuthentication(LegacyRepo > sitorySystem.java:477) > at > org.apache.maven.project.DefaultProjectBuildingHelper.createArtifactRepositories(DefaultP > rojectBuildingHelper.java:117) > at > org.apache.maven.project.DefaultModelBuildingListener.buildExtensionsAssembled(DefaultMod > elBuildingListener.java:127) > at > org.apache.maven.model.building.ModelBuildingEventCatapult$1.fire(ModelBuildingEventCatap > ult.java:43) > at > org.apache.maven.model.building.DefaultModelBuilder.fireEvent(DefaultModelBuilder.java:88 > 8) > at > org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:288) > at > org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:271) > at > org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:262) > at > org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:129) > at > org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:117) > at > org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:245) > at > org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:204) > at > org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetad > ataSource.java:576) > at > org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:1 > 89) > at > org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(Defaul > tLegacyArtifactCollector.java:533) > at > org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(Defaul > tLegacyArtifactCollector.java:594) > at > org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.collect(Defaul > tLegacyArtifactCollector.java:150) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolve > r.java:590) > at > org.apache.maven.repository.legacy.LegacyRepositorySystem.resolve(LegacyRepositorySystem. > java:325) > at > org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginD > ependenciesResolver.java:123) > at > org.apache.maven.plugin.internal.DefaultMavenPluginManager.createPluginRealm(DefaultMaven > PluginManager.java:324) > at > org.apache.maven.plugin.internal.DefaultMavenPluginManager.setupPluginRealm(DefaultMavenP > luginManager.java:272) > at > org.apache.maven.plugi
[jira] Commented: (MNG-2276) profile activation by property doesn't work with properties defined in settings.
[ http://jira.codehaus.org/browse/MNG-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224818#action_224818 ] Mark Michaelis commented on MNG-2276: - If my evaluation is correct it also means that profiles from parent POMs cannot activate profiles in child POMs. Is this correct? > profile activation by property doesn't work with properties defined in > settings. > > > Key: MNG-2276 > URL: http://jira.codehaus.org/browse/MNG-2276 > Project: Maven 2 & 3 > Issue Type: Bug > Components: POM, Profiles >Affects Versions: 2.0.4 >Reporter: Brian Fox >Assignee: Benjamin Bentmann > Fix For: 3.0-beta-1 > > Attachments: mng-2276.zip > > > Activating a profile like below doesn't get activated unless the property is > set on the CLI. I need to have the property defined in the settings.xml so > it's always set. > > > prod > > > deploy-ct > > > Further, I noticed that if I set it so that the activation is like: > > > deploy-cttrue > > > The profile is triggered just by setting the cli like "mvn -Ddeploy-ct" It > is not active if I use "-Ddeploy-ct=false" but the settings descriptor says > that the existence of the property is only used if value is not set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-197) ArrayIndexOutOfBoundsException on maven-2.2.1
[ http://jira.codehaus.org/browse/MPIR-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224817#action_224817 ] Xu Hui Sheng commented on MPIR-197: --- Thank you Dennis, I got it. > ArrayIndexOutOfBoundsException on maven-2.2.1 > - > > Key: MPIR-197 > URL: http://jira.codehaus.org/browse/MPIR-197 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: summary >Affects Versions: 2.2 > Environment: windows xp, jdk1.5.0_15, maven-2.2.1 >Reporter: Xu Hui Sheng >Priority: Blocker > Attachments: test.zip > > > after upgrade to 2.2 from 2.1.2. We got ArrayIndexOutOfBoundsException when > we try to generate the site of project. > Stacktrace > [INFO] Trace > java.lang.ArrayIndexOutOfBoundsException: 1 > at > org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.jav > a:791) > at > org.apache.maven.doxia.module.xhtml.XhtmlSink.tableHeaderCell(XhtmlSi > nk.java:777) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeaderCel > l(AbstractMavenReportRenderer.java:267) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeader(Ab > stractMavenReportRenderer.java:356) > at > org.apache.maven.report.projectinfo.ProjectSummaryReport$ProjectSumma > ryRenderer.renderBody(ProjectSummaryReport.java:107) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(Abstrac > tMavenReportRenderer.java:79) > at > org.apache.maven.report.projectinfo.ProjectSummaryReport.executeRepor > t(ProjectSummaryReport.java:49) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMaven > Report.java:190) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMaven > Report.java:144) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(R > eportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule( > DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(Defaul > tSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133 > ) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6 > 0) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4704) Maven 3.0 beta 1 password decryption log verbosity with FileNotFoundException
Maven 3.0 beta 1 password decryption log verbosity with FileNotFoundException - Key: MNG-4704 URL: http://jira.codehaus.org/browse/MNG-4704 Project: Maven 2 & 3 Issue Type: Bug Components: Command Line, Logging Affects Versions: 3.0-beta-1 Reporter: Jochen Stiepel I'm using decrypted passwords like described here: http://blogs.jfrog.org/2009/01/avoiding-clear-text-passwords-in-maven.html It works fine no problem. The only problem I have now, is the log verbosity while using mvn -X or Maven in DEBUG mode. It prints out hundreds of stack traces and so becomes unusable. Please change the logging of this kind of messages. Maybe log only the first stack trace and then stop repeating this stack trace printing. I don't have a settings-security.xml, because I don't need one and so I get this FileNotFoundException stack trace: [DEBUG] Failed to decrypt password for server central: org.sonatype.plexus.components.sec.dispatcher .SecDispatcherException: java.io.FileNotFoundException: C:\Dokumente und Einstellungen\stijoc\.m2\ settings-security.xml (Das System kann die angegebene Datei nicht finden) org.sonatype.plexus.components.sec.dispatcher.SecDispatcherException: org.sonatype.plexus.components .sec.dispatcher.SecDispatcherException: java.io.FileNotFoundException: C:\Dokumente und Einstellunge n\stijoc\.m2\settings-security.xml (Das System kann die angegebene Datei nicht finden) at org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher.decrypt(DefaultSecDisp atcher.java:121) at org.apache.maven.settings.crypto.DefaultSettingsDecrypter.decrypt(DefaultSettingsDecrypte r.java:106) at org.apache.maven.settings.crypto.DefaultSettingsDecrypter.decrypt(DefaultSettingsDecrypte r.java:62) at org.apache.maven.repository.legacy.LegacyRepositorySystem.injectAuthentication(LegacyRepo sitorySystem.java:477) at org.apache.maven.project.DefaultProjectBuildingHelper.createArtifactRepositories(DefaultP rojectBuildingHelper.java:117) at org.apache.maven.project.DefaultModelBuildingListener.buildExtensionsAssembled(DefaultMod elBuildingListener.java:127) at org.apache.maven.model.building.ModelBuildingEventCatapult$1.fire(ModelBuildingEventCatap ult.java:43) at org.apache.maven.model.building.DefaultModelBuilder.fireEvent(DefaultModelBuilder.java:88 8) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:288) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:271) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:262) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:129) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:117) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:245) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:204) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetad ataSource.java:576) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:1 89) at org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(Defaul tLegacyArtifactCollector.java:533) at org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(Defaul tLegacyArtifactCollector.java:594) at org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.collect(Defaul tLegacyArtifactCollector.java:150) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolve r.java:590) at org.apache.maven.repository.legacy.LegacyRepositorySystem.resolve(LegacyRepositorySystem. java:325) at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginD ependenciesResolver.java:123) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.createPluginRealm(DefaultMaven PluginManager.java:324) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.setupPluginRealm(DefaultMavenP luginManager.java:272) at org.apache.maven.plugin.DefaultBuildPluginManager.getPluginRealm(DefaultBuildPluginManage r.java:184) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.j ava:80) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69) at org.apache.maven.lifecycle.in
[jira] Commented: (MNG-2199) Version ranges not supported for parent artifacts
[
http://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224811#action_224811
]
Mark Michaelis commented on MNG-2199:
-
We also need this issue to be resolved - actually MNG-624 (no version = use
latest parent) is not enough from my point of view. We need this parent POM for
environmental settings (where are repositories and such) which always needs to
be up to date. But: We also need to build old projects with this parent POM -
and to allow to refactor the property names for example some day we need to
have a rule like: In each major version of the parent POM its "API" (i. e.: the
property names) stay the same.
Up to now we used settings.xml for this which we handed over through the
invoker-plugin. The settings.xml were downloaded and unpacked as dependency -
which of course supports version ranges. But the invoker-plugin poses other
problems so that it is not a solution for us anylonger.
> Version ranges not supported for parent artifacts
> -
>
> Key: MNG-2199
> URL: http://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation, POM, Reactor and workspace
>Affects Versions: 2.0.3
>Reporter: Christian Schulte
> Fix For: Issues to be reviewed for 3.x
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
>
> artifactId
> groupId
> [2.0, 2.0.1]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom
> Additionally it would be great if this
>
> artifactId
> groupId
> [2.0, ${pom.version}]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
