[jira] (WAGON-391) Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot connect. Reason: verify: false
[ https://jira.codehaus.org/browse/WAGON-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319801#comment-319801 ] Olivier Lamy commented on WAGON-391: can you provide a patch or a pull request here: https://github.com/apache/maven-wagon ? > Error installing artifact's metadata: Error while deploying metadata: > Authentication failed: Cannot connect. Reason: verify: false > --- > > Key: WAGON-391 > URL: https://jira.codehaus.org/browse/WAGON-391 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-ssh >Affects Versions: 2.3 >Reporter: Bryan Kelly > > When attempting to publish an artifact to an ssh server we get the following > exception intermittently: > Error installing artifact's metadata: Error while deploying metadata: > Authentication failed: Cannot connect. Reason: verify: false > Other consumers of the jsch library have had a similar issue [1], their fix > was to add retry logic while attempting to make the connection to the ssh > server. > [1] https://github.com/int128/gradle-ssh-plugin/issues/11 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-556) Vague error message from git-scm-plugin prevents release:prepare
[ https://jira.codehaus.org/browse/SCM-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319796#comment-319796 ] Daniel Serodio commented on SCM-556: I don't understand why this was closed as "Not a bug". The error message is completely misleading. > Vague error message from git-scm-plugin prevents release:prepare > > > Key: SCM-556 > URL: https://jira.codehaus.org/browse/SCM-556 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.3 >Reporter: Paul Hammant >Assignee: Olivier Lamy > > "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.j
[jira] (MPH-83) all-profiles should list profiles from settings.xml even if there is no project
[ https://jira.codehaus.org/browse/MPH-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MPH-83. - Resolution: Cannot Reproduce Assignee: Robert Scholte Tested with M2.2.1 and M3.0.4 and works fine. For previous M3 versions it did not work due to MNG-5224 IT improved with [r1446764|http://svn.apache.org/r1446764] > all-profiles should list profiles from settings.xml even if there is no > project > --- > > Key: MPH-83 > URL: https://jira.codehaus.org/browse/MPH-83 > Project: Maven 2.x Help Plugin > Issue Type: Bug > Components: all-profiles >Affects Versions: 2.1.1 >Reporter: Julien Nicoulaud >Assignee: Robert Scholte > > Running the goal all-profiles somewhere outside of a project answers "No > profile detected !". I have active and inactive profiles in my settings.xml, > they should appear. -- 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-963) Unable to set empty environment variables
[
https://jira.codehaus.org/browse/SUREFIRE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319793#comment-319793
]
Kristian Rosenvold commented on SUREFIRE-963:
-
Btw you can probably modify Surefire763EnvironmentForkModeIT and the
corresponding "environment-variables" project. Maybe even rename the IT to
"EnvironmentVariablesIT"
> Unable to set empty environment variables
> -
>
> Key: SUREFIRE-963
> URL: https://jira.codehaus.org/browse/SUREFIRE-963
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.13
> Environment: Linux Ubuntu 12.10,Maven 3.0.4
>Reporter: Christophe DENEUX
> Attachments: SUREFIRE-963.txt
>
>
> With the following configuration of the maven-surefire-plugin:
> {code}
>
>
>
>
>
> {code}
> I get the String "null" instead of "" as value of my env var in my unit test.
--
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] (WAGON-391) Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot connect. Reason: verify: false
[
https://jira.codehaus.org/browse/WAGON-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319792#comment-319792
]
Bryan Kelly commented on WAGON-391:
---
I think the retry logic could be added to AbstractJschWagon.java around line
200, it could look something like the following:
StringWriter stringWriter = new StringWriter();
for (int tries = 0; tries < 10; tries++) {
try {
session.connect();
if (getKnownHostsProvider() != null) {
PrintWriter w = new
PrintWriter(stringWriter);
HostKeyRepository hkr =
sch.getHostKeyRepository();
HostKey[] keys = hkr.getHostKey();
for (int i = 0; keys != null && i <
keys.length; i++) {
HostKey key = keys[i];
w.println(key.getHost() + " " +
key.getType() + " " + key.getKey());
}
}
break;
} catch (JSchException e) {
if (tries < 10) {
continue;
}
if
(e.getMessage().startsWith("UnknownHostKey:") ||
e.getMessage().startsWith("reject HostKey:")) {
throw new UnknownHostException(host, e);
} else if (e.getMessage().indexOf("HostKey has
been changed") >= 0) {
throw new
KnownHostChangedException(host, e);
} else {
throw new
AuthenticationException("Cannot connect. Reason: " + e.getMessage(), e);
}
}
}
> Error installing artifact's metadata: Error while deploying metadata:
> Authentication failed: Cannot connect. Reason: verify: false
> ---
>
> Key: WAGON-391
> URL: https://jira.codehaus.org/browse/WAGON-391
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
>Affects Versions: 2.3
>Reporter: Bryan Kelly
>
> When attempting to publish an artifact to an ssh server we get the following
> exception intermittently:
> Error installing artifact's metadata: Error while deploying metadata:
> Authentication failed: Cannot connect. Reason: verify: false
> Other consumers of the jsch library have had a similar issue [1], their fix
> was to add retry logic while attempting to make the connection to the ssh
> server.
> [1] https://github.com/int128/gradle-ssh-plugin/issues/11
--
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] (WAGON-391) Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot connect. Reason: verify: false
Bryan Kelly created WAGON-391: - Summary: Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot connect. Reason: verify: false Key: WAGON-391 URL: https://jira.codehaus.org/browse/WAGON-391 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Affects Versions: 2.3 Reporter: Bryan Kelly When attempting to publish an artifact to an ssh server we get the following exception intermittently: Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot connect. Reason: verify: false Other consumers of the jsch library have had a similar issue [1], their fix was to add retry logic while attempting to make the connection to the ssh server. [1] https://github.com/int128/gradle-ssh-plugin/issues/11 -- 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-953) Multi-module build succeeds even if tests time out
[
https://jira.codehaus.org/browse/SUREFIRE-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319787#comment-319787
]
Andreas Gudian commented on SUREFIRE-953:
-
See also SUREFIRE-920 (delivered with 2.13)
> Multi-module build succeeds even if tests time out
> --
>
> Key: SUREFIRE-953
> URL: https://jira.codehaus.org/browse/SUREFIRE-953
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support, Maven Surefire Plugin
>Affects Versions: 2.13
> Environment: Ubuntu 12.04. OpenJDK 7u9.
>Reporter: Diwaker Gupta
> Fix For: 2.14
>
>
> We have a multi-module Maven project. One of the modules has the following
> Surefire configuration:
> {noformat}
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
> classes
> random
> 1
> 300
>
>
> {noformat}
> Notice the 300s timeout. We've seen multiple instances where the build
> succeeds even if the tests time out. Here's an example:
> {noformat}
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Project 1 . SUCCESS [4.742s]
> [INFO] Project 2 . SUCCESS [5:15.220s]
> {noformat}
> Notice that Project 2 (which had the 300s timeout) above has run > 5 min.
> Earlier, in the log we see this:
> {noformat}
> mojoSucceeded
> org.apache.maven.plugins:maven-surefire-plugin:2.13(default-test)
> [ERROR] There was a timeout or other error in the fork
> [JENKINS] Recording test results
> projectSucceeded
> {noformat}
> So clearly Maven did hit a timeout and yet succeeded the build. I'm happy to
> provide any other information about our setup. I don't have an isolated,
> reproducible test case yet however.
--
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-953) Multi-module build succeeds even if tests time out
[
https://jira.codehaus.org/browse/SUREFIRE-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319783#comment-319783
]
Andreas Gudian commented on SUREFIRE-953:
-
Hi Diwaker,
only when I set {{-Dmaven.test.failure.ignore=true}} as VM argument (e.g.
through some option in Jenkins) or
{{true}} in the pom, I can observe the
behaviour you describe. As far as I can see it in the code, that is how it is
supposed to work
If that you don't have {{testFailureIgnore}} enabled, and still experience the
problem, than we clearly have a bug at hand - and we would need an isolated
test case for a deeper analysis.
If you have {{testFailureIgnore}} enabled and feel that Surefire should behave
differently, then let us know - good suggestions are always welcome around here.
> Multi-module build succeeds even if tests time out
> --
>
> Key: SUREFIRE-953
> URL: https://jira.codehaus.org/browse/SUREFIRE-953
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support, Maven Surefire Plugin
>Affects Versions: 2.13
> Environment: Ubuntu 12.04. OpenJDK 7u9.
>Reporter: Diwaker Gupta
> Fix For: 2.14
>
>
> We have a multi-module Maven project. One of the modules has the following
> Surefire configuration:
> {noformat}
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
> classes
> random
> 1
> 300
>
>
> {noformat}
> Notice the 300s timeout. We've seen multiple instances where the build
> succeeds even if the tests time out. Here's an example:
> {noformat}
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Project 1 . SUCCESS [4.742s]
> [INFO] Project 2 . SUCCESS [5:15.220s]
> {noformat}
> Notice that Project 2 (which had the 300s timeout) above has run > 5 min.
> Earlier, in the log we see this:
> {noformat}
> mojoSucceeded
> org.apache.maven.plugins:maven-surefire-plugin:2.13(default-test)
> [ERROR] There was a timeout or other error in the fork
> [JENKINS] Recording test results
> projectSucceeded
> {noformat}
> So clearly Maven did hit a timeout and yet succeeded the build. I'm happy to
> provide any other information about our setup. I don't have an isolated,
> reproducible test case yet however.
--
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] (MPH-53) mvn help:describe returns the version that is specified in metadata instead of the one in the parent pom
[
https://jira.codehaus.org/browse/MPH-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319779#comment-319779
]
Robert Scholte commented on MPH-53:
---
I've found a problem for M3.0.4:
{code:title=org.apache.maven.plugin.internal.DefaultPluginManager.verifyPlugin(Plugin,
MavenProject, Settings, ArtifactRepository)}
...
if ( plugin.getVersion() == null )
{
PluginVersionRequest versionRequest =
new DefaultPluginVersionRequest( plugin,
session.getRepositorySession(),
project.getRemotePluginRepositories() );
plugin.setVersion( pluginVersionResolver.resolve( versionRequest
).getVersion() );
}
...
{code}
The {{Model}} is not passed to the {{versionRequest}}, so the version is
resolved based on repositories.
There's no clear description of what the {{verifyPlugin()}} should do, so it's
hard to tell if we can just add the {{Model}}.
> mvn help:describe returns the version that is specified in metadata instead
> of the one in the parent pom
> -
>
> Key: MPH-53
> URL: https://jira.codehaus.org/browse/MPH-53
> Project: Maven 2.x Help Plugin
> Issue Type: Bug
> Components: describe
>Affects Versions: 2.0.1
> Environment: windows xp
> tested with mvn 2.0.8 & 2.0.9
>Reporter: Rintcius Blok
> Fix For: Backlog
>
>
> {{mvn help:describe}} returns a different version than {{mvn
> help:effective-pom}} returns:
> {noformat}
> > mvn help:describe -Dplugin=surefire
> ...
> [INFO] [help:describe]
> [INFO] Plugin: 'org.apache.maven.plugins:maven-surefire-plugin:2.2'
> ---
> Group Id: org.apache.maven.plugins
> Artifact Id: maven-surefire-plugin
> Version: 2.2
> Goal Prefix: surefire
> {noformat}
> However, when I run {{mvn help:effective-pom}}
> I get
> {code:xml}
> ...
>
>
>
> maven-surefire-plugin
> 2.4.3
>
> true
>
> **/*Test.java
>
> html
>
>
>
>
> ...
> {code}
> My pom structure is quite simple: just a parent {{pom.xml}} with the
> pluginmanagement section as above and a child pom using that. I have tested
> with both maven 2.0.8 and 2.0.9.
> See the discussion here:
> http://www.nabble.com/Wrong-output-of-mvn-help%3Adescribe--td19168212.html
--
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-963) Unable to set empty environment variables
[
https://jira.codehaus.org/browse/SUREFIRE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319778#comment-319778
]
Kristian Rosenvold commented on SUREFIRE-963:
-
Can you please create a small IT as described here
http://maven.apache.org/surefire/maven-surefire-plugin/developing.html
So we can avoid breaking this later ;)
> Unable to set empty environment variables
> -
>
> Key: SUREFIRE-963
> URL: https://jira.codehaus.org/browse/SUREFIRE-963
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.13
> Environment: Linux Ubuntu 12.10,Maven 3.0.4
>Reporter: Christophe DENEUX
> Attachments: SUREFIRE-963.txt
>
>
> With the following configuration of the maven-surefire-plugin:
> {code}
>
>
>
>
>
> {code}
> I get the String "null" instead of "" as value of my env var in my unit test.
--
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-4226) Better detection of JAVA_HOME on Apple Mac OS X
[
https://jira.codehaus.org/browse/MNG-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319774#comment-319774
]
Nikolaj Schumacher commented on MNG-4226:
-
This should probably be revisited soon. Apple recently removed the "Java
Preferences" and has everything in the system default to Java 7, if that is
installed. The pre-installed version of mvn 3.0.3 also uses Java 7, but any
upgrade to 3.0.4 will revert back to Java 6 due to this issue.
I assume this will surprise quite a few people and cost them time tracking it
down. And the current hard-coded /System/Library path will probably break as
soon as Apple drops their own JRE (which they deprecated in 2010.)
> Better detection of JAVA_HOME on Apple Mac OS X
> ---
>
> Key: MNG-4226
> URL: https://jira.codehaus.org/browse/MNG-4226
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Command Line
>Reporter: Alin Dreghiciu
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: MNG-4226-apache-maven.patch
>
>
> On mac JAVA_HOME is detected by using the following code:
> {code}
>if [ -z "$JAVA_VERSION" ] ; then
> JAVA_VERSION="CurrentJDK"
>else
> echo "Using Java version: $JAVA_VERSION"
>fi
>if [ -z "$JAVA_HOME" ] ; then
>
> JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/${JAVA_VERSION}/Home
>fi
> {code}
> But this does not work in collaboration with Using "Java preferences" to
> change the actual java version to use as "CurrentJDK" does not change once
> you update the "java applications" order.
> There is an alternative (at least on Leopard) for determining current java
> home that is based on Java Preferences by using an apple provided script. So,
> as a replacement fo rthe code above the following could be used.
> {code}
>if [ -z "$JAVA_HOME" ] ; then
> JAVA_HOME=`/usr/libexec/java_home | tail -1`
>fi
> {code}
> Could also be taht this is teh first attempt and if fails use the current way
> of determining home.
--
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] (MPH-67) Add a way to merge inherited profiles with same id
[
https://jira.codehaus.org/browse/MPH-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MPH-67:
--
Component/s: effective-pom
> Add a way to merge inherited profiles with same id
> --
>
> Key: MPH-67
> URL: https://jira.codehaus.org/browse/MPH-67
> Project: Maven 2.x Help Plugin
> Issue Type: Bug
> Components: effective-pom
>Affects Versions: 2.1
>Reporter: Vincent Siveton
> Fix For: Backlog
>
>
> Take the following project:
> {noformat}
> apache:6:pom with has a "apache-release" profileId
> |_ maven-parent:12
> |_ doxia:1.1.2-SNAPSHOT with has a "apache-release" profileId
> {noformat}
> Call /doxia/doxia/mvn help:effective-pom -N
> You will see only the apache-release from Doxia but Maven uses the
> apache-release from parent.
> Two way to see in the effective pom the inherited profiles with same id:
> * merge child and parent profiles
> * add parent profile with another id
--
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] (MECLIPSE-739) Goal eclipse:eclipse very slow
Romain N created MECLIPSE-739:
-
Summary: Goal eclipse:eclipse very slow
Key: MECLIPSE-739
URL: https://jira.codehaus.org/browse/MECLIPSE-739
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: WTP support
Affects Versions: 2.9
Environment: Windows XP, Maven 3
Reporter: Romain N
Priority: Critical
In a multiple project, when I run the goal eclipse:eclipse, the plugin spends a
lot of time to execute it (=~ 12min)
For each submodule, it blocs on this line:
{quote}[INFO] Adding support for WTP version 2.0.{quote}
And when I run the goal in debug mode (-X), I see it spends many time in
dependencies hierarchie, for exemple:
{quote}
[DEBUG] org.springframework:spring-context:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-aop:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] aopalliance:aopalliance:jar:1.0:compile (selected for compile)
[DEBUG] org.springframework:spring-asm:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-beans:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-core:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-core:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-beans:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-core:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-expression:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-asm:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] fr.generali.pdo.fondation.fwk:pdo-framework-logs:jar:1.0.14:compile
(selected for compile)
[DEBUG] ch.qos.logback:logback-classic:jar:0.9.28:compile (selected for
compile)
[DEBUG] ch.qos.logback:logback-core:jar:0.9.28:compile (selected for
compile)
{quote}
In this exemple, the plugin spends 30secondes on the last line.
My maven eclipse configuration is the next:
org.apache.maven.plugins
maven-eclipse-plugin
2.9
true
true
false
2.0
e:\workspace -->
org.eclipse.jdt.launching.JRE_CONTAINER
--
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-963) Unable to set empty environment variables
[
https://jira.codehaus.org/browse/SUREFIRE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christophe DENEUX updated SUREFIRE-963:
---
Attachment: SUREFIRE-963.txt
A patch solving the problem
> Unable to set empty environment variables
> -
>
> Key: SUREFIRE-963
> URL: https://jira.codehaus.org/browse/SUREFIRE-963
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.13
> Environment: Linux Ubuntu 12.10,Maven 3.0.4
>Reporter: Christophe DENEUX
> Attachments: SUREFIRE-963.txt
>
>
> With the following configuration of the maven-surefire-plugin:
> {code}
>
>
>
>
>
> {code}
> I get the String "null" instead of "" as value of my env var in my unit test.
--
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] (MRELEASE-823) Check for local modifications works incorrectly with Mercurial
[
https://jira.codehaus.org/browse/MRELEASE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319757#comment-319757
]
Stanilslav Spiridonov commented on MRELEASE-823:
plugin configuration:
maven-release-plugin
2.3.2
true
false
@{project.version}
true
> Check for local modifications works incorrectly with Mercurial
> --
>
> Key: MRELEASE-823
> URL: https://jira.codehaus.org/browse/MRELEASE-823
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: Mercurial
>Affects Versions: 2.3.2
>Reporter: Stanilslav Spiridonov
>
> It just ignore modified files. In the log above the "impl\pom.xml" is modified
> C:\Development\work\repo\JRS\open\base\manager\pom>mvn release:branch
> -DbranchName=my-branch -DupdateBranchVersions=true
> C:\Development\work\repo\JRS\open\base\manager\pom>set
> MAVEN_OPTS=-Dfile.encoding=UTF-8
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] JRESEARCH-COMMONS: POM for base domain managers
> [INFO] JRS-COMMONS: Base service API
> [INFO] JRS-COMMONS: Base service implementation
> [INFO]
> [INFO]
>
> [INFO] Building JRESEARCH-COMMONS: POM for base domain managers 1.0.2-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-release-plugin:2.3.2:branch (default-cli) @
> org.jresearch.commons.base.manager.pom ---
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: **\release.properties, **\pom.xml.next,
> **\pom.xml.releaseBackup, **\pom.xml.backup, **\pom.xml.branch, **\pom.xml.tag
> [INFO] EXECUTING: cmd.exe /X /C "hg status"
> [INFO] Not a file:
> C:\Development\work\repo\JRS\open\base\manager\pom\impl\pom.xml. Ignoring
> [INFO] Not a file:
> C:\Development\work\repo\JRS\open\base\manager\pom\api\pom.xml.releaseBackup.
> Ignoring
> [INFO] Not a file:
> C:\Development\work\repo\JRS\open\base\manager\pom\impl\pom.xml.releaseBackup.
> Ignoring
> [INFO] Not a file:
> C:\Development\work\repo\JRS\open\base\manager\pom\pom\pom.xml.releaseBackup.
> Ignoring
> What is the branch version for "JRESEARCH-COMMONS: POM for base domain
> managers"?
> (org.jresearch.commons.base.manager:org.jresearch.commons.base.manager.pom)
> 1.0.2-SNAPSHOT: : Terminate batch
> job (Y/N)? y
> C:\Development\work\repo\JRS\open\base\manager\impl>hg status
> M impl\pom.xml
> ? api\pom.xml.releaseBackup
> ? impl\pom.xml.releaseBackup
> ? pom\pom.xml.releaseBackup
--
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] (MRELEASE-823) Check for local modifications works incorrectly with Mercurial
Stanilslav Spiridonov created MRELEASE-823: -- Summary: Check for local modifications works incorrectly with Mercurial Key: MRELEASE-823 URL: https://jira.codehaus.org/browse/MRELEASE-823 Project: Maven 2.x Release Plugin Issue Type: Bug Components: Mercurial Affects Versions: 2.3.2 Reporter: Stanilslav Spiridonov It just ignore modified files. In the log above the "impl\pom.xml" is modified C:\Development\work\repo\JRS\open\base\manager\pom>mvn release:branch -DbranchName=my-branch -DupdateBranchVersions=true C:\Development\work\repo\JRS\open\base\manager\pom>set MAVEN_OPTS=-Dfile.encoding=UTF-8 [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] JRESEARCH-COMMONS: POM for base domain managers [INFO] JRS-COMMONS: Base service API [INFO] JRS-COMMONS: Base service implementation [INFO] [INFO] [INFO] Building JRESEARCH-COMMONS: POM for base domain managers 1.0.2-SNAPSHOT [INFO] [INFO] [INFO] --- maven-release-plugin:2.3.2:branch (default-cli) @ org.jresearch.commons.base.manager.pom --- [INFO] Verifying that there are no local modifications... [INFO] ignoring changes on: **\release.properties, **\pom.xml.next, **\pom.xml.releaseBackup, **\pom.xml.backup, **\pom.xml.branch, **\pom.xml.tag [INFO] EXECUTING: cmd.exe /X /C "hg status" [INFO] Not a file: C:\Development\work\repo\JRS\open\base\manager\pom\impl\pom.xml. Ignoring [INFO] Not a file: C:\Development\work\repo\JRS\open\base\manager\pom\api\pom.xml.releaseBackup. Ignoring [INFO] Not a file: C:\Development\work\repo\JRS\open\base\manager\pom\impl\pom.xml.releaseBackup. Ignoring [INFO] Not a file: C:\Development\work\repo\JRS\open\base\manager\pom\pom\pom.xml.releaseBackup. Ignoring What is the branch version for "JRESEARCH-COMMONS: POM for base domain managers"? (org.jresearch.commons.base.manager:org.jresearch.commons.base.manager.pom) 1.0.2-SNAPSHOT: : Terminate batch job (Y/N)? y C:\Development\work\repo\JRS\open\base\manager\impl>hg status M impl\pom.xml ? api\pom.xml.releaseBackup ? impl\pom.xml.releaseBackup ? pom\pom.xml.releaseBackup -- 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] (MCLEAN-53) directory (specified in the section) not removed if it's not empty
[
https://jira.codehaus.org/browse/MCLEAN-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319748#comment-319748
]
Peter B. commented on MCLEAN-53:
OK, my wrong, I'm supposed to use:
{code}
maven-clean-plugin
2.5
./
deleteme/**
{code}
> directory (specified in the section) not removed if it's not empty
> -
>
> Key: MCLEAN-53
> URL: https://jira.codehaus.org/browse/MCLEAN-53
> Project: Maven 2.x Clean Plugin
> Issue Type: Bug
>Affects Versions: 2.4, 2.4.1, 2.5
> Environment: fedora 17, 64bit
> java -version:
> java version "1.7.0_09"
> Java(TM) SE Runtime Environment (build 1.7.0_09-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode)
> mvn --version
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.7.0_09
> Java home: /usr/java/jdk1.7.0_09/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux" version: "3.6.8-2.fc17.x86_64" arch: "amd64" Family: "unix"
>Reporter: Peter B.
> Fix For: 2.5
>
> Attachments: sample.zip
>
>
> in case of following configuration:
> {code:xml}
>
> maven-clean-plugin
> 2.5
>
>
>
> ./
>
> deleteme
>
>
>
>
>
> {code}
> and having directory structure like this:
> {code}
> deleteme/i_prevent_deletion.txt
> pom.xml
> {code}
> directory deleteme won't be deleted. If the i_prevent_deletion.txt file is
> removed, all works.
> Problematic behavior doesn't seem to be working since 2.4 version.
> However for 2.3 version it works OK.
> Usage of the section is critical here, because in our real world
> application we don't have single directory, but rather multilevel directory
> structure and we use * in the includes (this could not be achieved by the
> only as far as I know).
--
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] (MCLEAN-53) directory (specified in the section) not removed if it's not empty
[
https://jira.codehaus.org/browse/MCLEAN-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter B. closed MCLEAN-53.
--
Resolution: Not A Bug
Fix Version/s: 2.5
> directory (specified in the section) not removed if it's not empty
> -
>
> Key: MCLEAN-53
> URL: https://jira.codehaus.org/browse/MCLEAN-53
> Project: Maven 2.x Clean Plugin
> Issue Type: Bug
>Affects Versions: 2.4, 2.4.1, 2.5
> Environment: fedora 17, 64bit
> java -version:
> java version "1.7.0_09"
> Java(TM) SE Runtime Environment (build 1.7.0_09-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode)
> mvn --version
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.7.0_09
> Java home: /usr/java/jdk1.7.0_09/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux" version: "3.6.8-2.fc17.x86_64" arch: "amd64" Family: "unix"
>Reporter: Peter B.
> Fix For: 2.5
>
> Attachments: sample.zip
>
>
> in case of following configuration:
> {code:xml}
>
> maven-clean-plugin
> 2.5
>
>
>
> ./
>
> deleteme
>
>
>
>
>
> {code}
> and having directory structure like this:
> {code}
> deleteme/i_prevent_deletion.txt
> pom.xml
> {code}
> directory deleteme won't be deleted. If the i_prevent_deletion.txt file is
> removed, all works.
> Problematic behavior doesn't seem to be working since 2.4 version.
> However for 2.3 version it works OK.
> Usage of the section is critical here, because in our real world
> application we don't have single directory, but rather multilevel directory
> structure and we use * in the includes (this could not be achieved by the
> only as far as I know).
--
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-963) Unable to set empty environment variables
[
https://jira.codehaus.org/browse/SUREFIRE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319745#comment-319745
]
Christophe DENEUX commented on SUREFIRE-963:
In debug mode, I get the following trace:
{code}
[DEBUG] Setting environment variable [PETALS_CLI_PREFS]=[null]
{code}
> Unable to set empty environment variables
> -
>
> Key: SUREFIRE-963
> URL: https://jira.codehaus.org/browse/SUREFIRE-963
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.13
> Environment: Linux Ubuntu 12.10,Maven 3.0.4
>Reporter: Christophe DENEUX
>
> With the following configuration of the maven-surefire-plugin:
> {code}
>
>
>
>
>
> {code}
> I get the String "null" instead of "" as value of my env var in my unit test.
--
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-963) Unable to set empty environment variables
Christophe DENEUX created SUREFIRE-963:
--
Summary: Unable to set empty environment variables
Key: SUREFIRE-963
URL: https://jira.codehaus.org/browse/SUREFIRE-963
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.13
Environment: Linux Ubuntu 12.10,Maven 3.0.4
Reporter: Christophe DENEUX
With the following configuration of the maven-surefire-plugin:
{code}
{code}
I get the String "null" instead of "" as value of my env var in my unit test.
--
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
