[jira] (MDEPLOY-131) use default repository when no url specified
[ https://jira.codehaus.org/browse/MDEPLOY-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354701#comment-354701 ] Arne Brix commented on MDEPLOY-131: --- I have a similar usecase. We use the replacer plugin to modify our pom file (using a jenkins env-variable) before it is being deployed. With the old deploy plugin we could simply set the pomFile property to specify the path of the changed pom for deploy:deploy but now we must use deploy:file and that's not really practical if one has different repositories for releases and snapshots. So please let deploy:deploy honor the pomFile property as before or add automatic repository selection to deploy:file. > use default repository when no url specified > > > Key: MDEPLOY-131 > URL: https://jira.codehaus.org/browse/MDEPLOY-131 > Project: Maven Deploy Plugin > Issue Type: Improvement > Components: deploy:deploy-file >Reporter: raymond domingo > Labels: contributers-welcome > Attachments: DeployFileMojo.java, patch_deploy_file_mojo.diff > > > When using the deploy goal there is no need to specify the url of the > repository. > When using deploy-file you DO need to specify the url. This is a problem, > because during development I like to deploy to snapshot repository and when > releasing i deploy to release repository and I can't add this logic to the > pom. > Thas is why I like the url paramter to become optional (backwards compatible) > and add default behaviour when it is null. It should just like the deploy > plugin use the default repository. Snapshot for snapshots and release for > none snapshot versions. > I added a patch file fixing this. > I also added complete source of patched Mojo -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation
[
https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Phillips updated SUREFIRE-654:
-
Attachment: surefire-fix-test-build-output.txt
surefire-fix-test.zip
> Surefire does not recognize successful tests using TestNG with the
> invocationCount and successPercentage parameters on the @Test annotation
> ---
>
> Key: SUREFIRE-654
> URL: https://jira.codehaus.org/browse/SUREFIRE-654
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.6
> Environment: Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0-18
> Java home: /usr/lib/jvm/java-6-openjdk/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix"
> Ubuntu 10.10
>Reporter: Steve Stodola
> Attachments: bugtest.tar.gz, surefire654.diff,
> surefire-fix-test-build-output.txt, surefire-fix-test.zip
>
>
> Surefire does not recognize successful tests using TestNG with the
> invocationCount and successPercentage parameters on the @Test annotation.
> BugTest.java in the attached file has an invocationCount = 100 with a
> successPercentage = 1. 1 test in 100 needs to pass for the test to be
> considered successful. However when running *{{mvn clean test}}* Surefire
> reports the tests as failed. The generated report shows the tests as passing.
> Surefire should be identifying this test as passing.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation
[
https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354700#comment-354700
]
Andrew Phillips commented on SUREFIRE-654:
--
Unfortunately, this patch doesn't seem to work for me :-( What I did:
1. Cloned the surefire project
2. Reverted to the 2.17 release commit and applied the patch
3. Built and installed the surefire plugin locally (version 2.17-SUREFIRE-654)
4. Ran the attached project with {{mvn clean test}}
The test should fail as all four invocations fail, but even with a success
percentage of 99% the build succeeds. See attached output.
My environment:
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T12:37:52-05:00)
Maven home: C:\Program Files (x86)\Apache\maven-3.2.1\bin\..
Java version: 1.7.0_40, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_40\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Surefire does not recognize successful tests using TestNG with the
> invocationCount and successPercentage parameters on the @Test annotation
> ---
>
> Key: SUREFIRE-654
> URL: https://jira.codehaus.org/browse/SUREFIRE-654
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.6
> Environment: Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0-18
> Java home: /usr/lib/jvm/java-6-openjdk/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix"
> Ubuntu 10.10
>Reporter: Steve Stodola
> Attachments: bugtest.tar.gz, surefire654.diff,
> surefire-fix-test-build-output.txt, surefire-fix-test.zip
>
>
> Surefire does not recognize successful tests using TestNG with the
> invocationCount and successPercentage parameters on the @Test annotation.
> BugTest.java in the attached file has an invocationCount = 100 with a
> successPercentage = 1. 1 test in 100 needs to pass for the test to be
> considered successful. However when running *{{mvn clean test}}* Surefire
> reports the tests as failed. The generated report shows the tests as passing.
> Surefire should be identifying this test as passing.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354697#comment-354697
]
Michael Heuer commented on MDEPLOY-177:
---
Hello Robert,
Unfortunately I am no longer able to reproduce the issue since we now release
to Maven Central via Sonatype OSS Nexus, which doesn't use scp for the deploy
step.
http://tinyurl.com/pjo52mp
(link to
http://search.maven.org/#search|gav|1|g%3A%22org.biojava%22%20AND%20a%3A%22biojava-legacy%22,
which Jira doesn't handle)
> Maven release:perform hangs when downloading maven-metadata.xml
> ---
>
> Key: MDEPLOY-177
> URL: https://jira.codehaus.org/browse/MDEPLOY-177
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.8.1
> Environment: $ mvn -v
> Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
> 2014-02-14T11:37:52-06:00)
> Maven home: /usr/local/Cellar/maven/3.2.1/libexec
> Java version: 1.7.0_51, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9.2", arch: "x86_64", family: "mac"
>Reporter: Michael Heuer
>Priority: Critical
> Attachments: deploy-debug.txt, release-perform-3.0.5.txt,
> release-perform-debug.txt
>
>
> When attempting to mvn release:perform
> {code:none}
> $ mvn release:perform
> ...
> [INFO] [INFO]
>
> [INFO] [INFO] Building biojava-legacy 1.8.5
> [INFO] [INFO]
>
> [INFO] [INFO]
> [INFO] [INFO] >>> maven-source-plugin:2.2.1:jar (attach-sources) @
> biojava-legacy >>>
> [INFO] [INFO]
> [INFO] [INFO] <<< maven-source-plugin:2.2.1:jar (attach-sources) @
> biojava-legacy <<<
> [INFO] [INFO]
> [INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
> biojava-legacy ---
> [INFO] [INFO]
> [INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
> biojava-legacy ---
> [INFO] [INFO] Not executing Javadoc as the project is not a Java
> classpath-capable package
> [INFO] [INFO]
> [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
> biojava-legacy ---
> [INFO] [INFO] Installing
> /Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
> /Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
> [INFO] [INFO]
> [INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
> biojava-legacy ---
> [INFO] Uploading:
> scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
> [INFO] 4/9 KB
> [INFO] 8/9 KB
> [INFO] 9/9 KB
> [INFO]
> [INFO] Uploaded:
> scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
> (9 KB at 3.0 KB/sec)
> [INFO] Downloading:
> scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
> [INFO] 750/750 B
> [INFO] 751/750 B
> {code}
> the build hangs at this point. It appears there might be a difference
> between the expected file size and the downloaded file size, but no
> warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-251) Upgrade to Checkstyle 5.8
[ https://jira.codehaus.org/browse/MCHECKSTYLE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen reassigned MCHECKSTYLE-251: -- Assignee: Mirko Friedenhagen > Upgrade to Checkstyle 5.8 > - > > Key: MCHECKSTYLE-251 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-251 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.13 >Reporter: Andrew Gaul >Assignee: Mirko Friedenhagen > Fix For: 2.14 > > Attachments: checkstyle_5.8.patch > > > This release includes many new violations. Release notes: > http://checkstyle.sourceforge.net/releasenotes.html > I tested this patch against jclouds without regressions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-251) Upgrade to Checkstyle 5.8
[ https://jira.codehaus.org/browse/MCHECKSTYLE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen closed MCHECKSTYLE-251. -- Resolution: Fixed Fix Version/s: 2.14 > Upgrade to Checkstyle 5.8 > - > > Key: MCHECKSTYLE-251 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-251 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.13 >Reporter: Andrew Gaul >Assignee: Mirko Friedenhagen > Fix For: 2.14 > > Attachments: checkstyle_5.8.patch > > > This release includes many new violations. Release notes: > http://checkstyle.sourceforge.net/releasenotes.html > I tested this patch against jclouds without regressions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-253) Upgrade to checkstyle 5.9 for Java 8 compatibility
[ https://jira.codehaus.org/browse/MCHECKSTYLE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen updated MCHECKSTYLE-253: --- Summary: Upgrade to checkstyle 5.9 for Java 8 compatibility (was: Upgrade to checkstyle 5.9 for Java 8 compatability) > Upgrade to checkstyle 5.9 for Java 8 compatibility > -- > > Key: MCHECKSTYLE-253 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-253 > Project: Maven Checkstyle Plugin > Issue Type: New Feature >Reporter: Zlika >Assignee: Mirko Friedenhagen > Fix For: 2.14 > > > Checkstyle 5.9 has just been released and adds support for Java 8. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5703) ClosedChannelException from DefaultUpdateCheckManager.read on Linux
[ https://jira.codehaus.org/browse/MNG-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354692#comment-354692 ] Tony Reix commented on MNG-5703: On RHEL7/PPC64BE, I'm now using a Falcon patch that enables me to compile Falcon (and the modified version of Oozie that Falcon uses) with IBM Java 1.7 . And I do not have the Maven issue in this environment. Is it related to Ubuntu ? $ mvn --version Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:52+01:00) Maven home: /opt/apache-maven-3.2.1 Java version: 1.7.0, vendor: IBM Corporation Java home: /usr/lib/jvm/ibm-java-ppc64-71/jre Default locale: en_US, platform encoding: ISO-8859-1 OS name: "linux", version: "3.10.0-123.6.3.el7.ppc64", arch: "ppc64", family: "unix" > ClosedChannelException from DefaultUpdateCheckManager.read on Linux > --- > > Key: MNG-5703 > URL: https://jira.codehaus.org/browse/MNG-5703 > Project: Maven > Issue Type: Bug >Affects Versions: 3.2.1 > Environment: Ubuntu 14.10 / PPC64 LE - IBM JVM 1.7 > Ubuntu 14.10 / x86_64 - IBM JVM 1.7 & 1.6 - Oracle JVM 1.7 >Reporter: Tony Reix >Priority: Blocker > > I already added a note in: http://jira.codehaus.org/browse/MNG-5629 . > But, since this JIRA deals with Windows, since my issues are on Linux, and > since I'm blocked, I'm opening a new JIRA. > I was working on the port of Falcon on PPC64 when it appeared. I'm now > blocked. > First, I was on RHEL7/PPC64BE: this Maven error was not there, and I've been > able to compile and run tests, with IBM JVM v1.6 . > Then, I moved to Ubuntu/PPC64LE, with IBM JVM 1.7, and the issue appeared. > I then tried on Ubuntu/x86_64, with IBM JVM and then Oracle JVM, v1.7, and > the issue was there too. Same with IBM JVM 1.6 . > Traces show the issue when using -X only. > Example of traces, on Ubuntu/x86_64 , with IBM JVM 1.6 : > export HADOOP_VERSION=2.4.1 > export HADOOP_PROFILE=hadoop-2 > export OOZIE_VERSION=4.0.1 > mvn -X compile -P $HADOOP_PROFILE -Dhadoop.version=$HADOOP_VERSION > -Doozie.version=$OOZIE_VERSION -Doozie.forcebuild=false -DskipTests > ... > [DEBUG] Determining update check for artifact asm:asm > (/home/reixt/.m2/repository/asm/asm/maven-metadata-central.xml) from central > (http://repo1.maven.org/maven2) > [DEBUG] Searching for central.maven-metadata-central.xml.lastUpdated in > resolution tracking file. > [DEBUG] Reading resolution-state from: > /home/reixt/.m2/repository/asm/asm/resolver-status.properties > [DEBUG] Error releasing shared lock for resolution tracking file: > /home/reixt/.m2/repository/asm/asm/resolver-status.properties > java.nio.channels.ClosedChannelException > at sun.nio.ch.FileLockImpl.release(FileLockImpl.java:47) > at > org.apache.maven.repository.legacy.DefaultUpdateCheckManager.read(DefaultUpdateCheckManager.java:396) > at > org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:323) > at > org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:159) > at > org.apache.maven.repository.legacy.DefaultUpdateCheckManager.isUpdateRequired(DefaultUpdateCheckManager.java:148) > ... > [INFO] Apache Falcon Oozie EL Extension .. FAILURE [ 26.935 s] > [INFO] Apache Falcon Embedded Hadoop - Test Cluster .. SKIPPED > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 17:52 min > [INFO] Finished at: 2014-10-20T10:18:30-05:00 > [INFO] Final Memory: 38M/181M > [INFO] > > [ERROR] Failed to execute goal on project falcon-oozie-el-extension: Could > not resolve dependencies for project > org.apache.falcon:falcon-oozie-el-extension:jar:0.5-incubating: Could not > find artifact org.apache.oozie:oozie-core:jar:4.0.1-falcon in central > (http://repo1.maven.org/maven2) -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal on project falcon-oozie-el-extension: Could not resolve dependencies for > project org.apache.falcon:falcon-oozie-el-extension:jar:0.5-incubating: Could > not find artifact org.apache.oozie:oozie-core:jar:4.0.1-falcon in central > Testcase: > - download Falcon v0.5 > - use above mvn options -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-455) Flexible Modulename
[
https://jira.codehaus.org/browse/ARCHETYPE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354690#comment-354690
]
Giulio Micali edited comment on ARCHETYPE-455 at 10/20/14 11:24 AM:
I need it too, this and more.
I'm working on a patch that:
1) allows to declare a list of classes (hooks)
{code:xml}
...
it.my.pkg.Hook1
it.my.pkg.Hook2
{code}
implementing the following interface:
{code:title=ArchetypeVelocityHook.java|borderStyle=solid}
public interface ArchetypeVelocityHook {
public void onStart(Context context);
public void onModuleStart(String moduleName, Context context);
}
{code}
on these method implementations, we can define(and resolve directly) new
variables.
2) allows to include in build classpath all dependencies declared in the
archetype pom, so hooks can access those libs and implement all the possible
logic we wish (Personal formatting classes, connection to DBs/WebServices to
retrieve configurations, etc...)
But I have a couples of questions:
1) the source code I'm starting from is on SVN (tag 2.2), but i found also a
project in GitHub: which is the real actual reference ?
2) my solution could be used, with very little effort, also to solve the other
issues regarding the variables processing and/or templates exclusion: should I
open a new Issue for my proposal patch ?
Thanks,
Giulio
was (Author: gmicali):
I need it too, this and more.
I'm working on a patch that:
1) allows to declare a list of classes (hooks) implementing the following
interface:
public interface ArchetypeVelocityHook {
public void onStart(Context context);
public void onModuleStart(String moduleName, Context context);
}
on these method implementations, we can define(and resolve directly) new
variables.
2) allows to include in build classpath all dependencies declared in the
archetype pom, so hooks can access those libs and implement all the possible
logic we wish (Personal formatting classes, connection to DBs/WebServices to
retrieve configurations, etc...)
But I have a couples of questions:
1) the source code I'm starting from is on SVN (tag 2.2), but i found also a
project in GitHub: which is the real actual reference ?
2) my solution could be used, with very little effort, also to solve the other
issues regarding the variables processing and/or templates exclusion: should I
open a new Issue for my proposal patch ?
Thanks,
Giulio
> Flexible Modulename
> ---
>
> Key: ARCHETYPE-455
> URL: https://jira.codehaus.org/browse/ARCHETYPE-455
> Project: Maven Archetype
> Issue Type: Wish
> Components: Generator
>Reporter: Michael Kopf
> Attachments: archetype-common-flex-module-name.patch,
> archetype-multi-module-project-1.1.jar
>
>
> I have to create a multi-module project from maven-archetype with free
> configurable modulenames. This should be possible with required properties in
> the archetype.
> Up to now this is only possible with artifactId or rootArtifactId and you
> have to use it in form of prefix__rootArtifactId__postfix for the module
> directory.
> What I want is to set a required property while setting up the new project
> with the archetype. Within the archetype you have to configure the module
> with directory __yourproperty__ and in the archetype-metadata.xml the module
> entry like as follows:
> {code}
>
> {code}
> I made a patch which works for me.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (ARCHETYPE-455) Flexible Modulename
[
https://jira.codehaus.org/browse/ARCHETYPE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354690#comment-354690
]
Giulio Micali commented on ARCHETYPE-455:
-
I need it too, this and more.
I'm working on a patch that:
1) allows to declare a list of classes (hooks) implementing the following
interface:
public interface ArchetypeVelocityHook {
public void onStart(Context context);
public void onModuleStart(String moduleName, Context context);
}
on these method implementations, we can define(and resolve directly) new
variables.
2) allows to include in build classpath all dependencies declared in the
archetype pom, so hooks can access those libs and implement all the possible
logic we wish (Personal formatting classes, connection to DBs/WebServices to
retrieve configurations, etc...)
But I have a couples of questions:
1) the source code I'm starting from is on SVN (tag 2.2), but i found also a
project in GitHub: which is the real actual reference ?
2) my solution could be used, with very little effort, also to solve the other
issues regarding the variables processing and/or templates exclusion: should I
open a new Issue for my proposal patch ?
Thanks,
Giulio
> Flexible Modulename
> ---
>
> Key: ARCHETYPE-455
> URL: https://jira.codehaus.org/browse/ARCHETYPE-455
> Project: Maven Archetype
> Issue Type: Wish
> Components: Generator
>Reporter: Michael Kopf
> Attachments: archetype-common-flex-module-name.patch,
> archetype-multi-module-project-1.1.jar
>
>
> I have to create a multi-module project from maven-archetype with free
> configurable modulenames. This should be possible with required properties in
> the archetype.
> Up to now this is only possible with artifactId or rootArtifactId and you
> have to use it in form of prefix__rootArtifactId__postfix for the module
> directory.
> What I want is to set a required property while setting up the new project
> with the archetype. Within the archetype you have to configure the module
> with directory __yourproperty__ and in the archetype-metadata.xml the module
> entry like as follows:
> {code}
>
> {code}
> I made a patch which works for me.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation
[
https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354688#comment-354688
]
Andreas Gudian commented on SUREFIRE-654:
-
I'll take a closer look on the PR soon-ish.
> Surefire does not recognize successful tests using TestNG with the
> invocationCount and successPercentage parameters on the @Test annotation
> ---
>
> Key: SUREFIRE-654
> URL: https://jira.codehaus.org/browse/SUREFIRE-654
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.6
> Environment: Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0-18
> Java home: /usr/lib/jvm/java-6-openjdk/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix"
> Ubuntu 10.10
>Reporter: Steve Stodola
> Attachments: bugtest.tar.gz, surefire654.diff
>
>
> Surefire does not recognize successful tests using TestNG with the
> invocationCount and successPercentage parameters on the @Test annotation.
> BugTest.java in the attached file has an invocationCount = 100 with a
> successPercentage = 1. 1 test in 100 needs to pass for the test to be
> considered successful. However when running *{{mvn clean test}}* Surefire
> reports the tests as failed. The generated report shows the tests as passing.
> Surefire should be identifying this test as passing.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5629) ClosedChannelException from DefaultUpdateCheckManager.read
[
https://jira.codehaus.org/browse/MNG-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354685#comment-354685
]
Tony Reix commented on MNG-5629:
I've opened a new JIRA: http://jira.codehaus.org/browse/MNG-5703 .
> ClosedChannelException from DefaultUpdateCheckManager.read
> --
>
> Key: MNG-5629
> URL: https://jira.codehaus.org/browse/MNG-5629
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.2.1
> Environment: Windows 7, Java 7 updated 25
>Reporter: Anthony Whitford
> Attachments: xy.tar.gz
>
>
> I ran a build in debug mode ({{mvn -X}}) and noticed the following bug
> (repeatedly):
> {noformat}
> [DEBUG] Error releasing shared lock for resolution tracking file:
> C:\Users\awhitford\.m2\repository\org\apache\maven\plugins\maven-war-plugin\resolver-status.properties
> java.nio.channels.ClosedChannelException
> at sun.nio.ch.FileLockImpl.release(FileLockImpl.java:58)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.read(DefaultUpdateCheckManager.java:396)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:323)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:159)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.isUpdateRequired(DefaultUpdateCheckManager.java:148)
> at
> org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:127)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:435)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:425)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupArtifactVersions(DefaultVersionsHelper.java:229)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupPluginUpdates(DefaultVersionsHelper.java:727)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupPluginsUpdates(DefaultVersionsHelper.java:706)
> at
> org.codehaus.mojo.versions.PluginUpdatesReport.doGenerateReport(PluginUpdatesReport.java:103)
> at
> org.codehaus.mojo.versions.AbstractVersionsReport.executeReport(AbstractVersionsReport.java:253)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:228)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 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:108)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.ja
[jira] (MNG-5703) ClosedChannelException from DefaultUpdateCheckManager.read on Linux
Tony Reix created MNG-5703: -- Summary: ClosedChannelException from DefaultUpdateCheckManager.read on Linux Key: MNG-5703 URL: https://jira.codehaus.org/browse/MNG-5703 Project: Maven Issue Type: Bug Affects Versions: 3.2.1 Environment: Ubuntu 14.10 / PPC64 LE - IBM JVM 1.7 Ubuntu 14.10 / x86_64 - IBM JVM 1.7 & 1.6 - Oracle JVM 1.7 Reporter: Tony Reix Priority: Blocker I already added a note in: http://jira.codehaus.org/browse/MNG-5629 . But, since this JIRA deals with Windows, since my issues are on Linux, and since I'm blocked, I'm opening a new JIRA. I was working on the port of Falcon on PPC64 when it appeared. I'm now blocked. First, I was on RHEL7/PPC64BE: this Maven error was not there, and I've been able to compile and run tests, with IBM JVM v1.6 . Then, I moved to Ubuntu/PPC64LE, with IBM JVM 1.7, and the issue appeared. I then tried on Ubuntu/x86_64, with IBM JVM and then Oracle JVM, v1.7, and the issue was there too. Same with IBM JVM 1.6 . Traces show the issue when using -X only. Example of traces, on Ubuntu/x86_64 , with IBM JVM 1.6 : export HADOOP_VERSION=2.4.1 export HADOOP_PROFILE=hadoop-2 export OOZIE_VERSION=4.0.1 mvn -X compile -P $HADOOP_PROFILE -Dhadoop.version=$HADOOP_VERSION -Doozie.version=$OOZIE_VERSION -Doozie.forcebuild=false -DskipTests ... [DEBUG] Determining update check for artifact asm:asm (/home/reixt/.m2/repository/asm/asm/maven-metadata-central.xml) from central (http://repo1.maven.org/maven2) [DEBUG] Searching for central.maven-metadata-central.xml.lastUpdated in resolution tracking file. [DEBUG] Reading resolution-state from: /home/reixt/.m2/repository/asm/asm/resolver-status.properties [DEBUG] Error releasing shared lock for resolution tracking file: /home/reixt/.m2/repository/asm/asm/resolver-status.properties java.nio.channels.ClosedChannelException at sun.nio.ch.FileLockImpl.release(FileLockImpl.java:47) at org.apache.maven.repository.legacy.DefaultUpdateCheckManager.read(DefaultUpdateCheckManager.java:396) at org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:323) at org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:159) at org.apache.maven.repository.legacy.DefaultUpdateCheckManager.isUpdateRequired(DefaultUpdateCheckManager.java:148) ... [INFO] Apache Falcon Oozie EL Extension .. FAILURE [ 26.935 s] [INFO] Apache Falcon Embedded Hadoop - Test Cluster .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 17:52 min [INFO] Finished at: 2014-10-20T10:18:30-05:00 [INFO] Final Memory: 38M/181M [INFO] [ERROR] Failed to execute goal on project falcon-oozie-el-extension: Could not resolve dependencies for project org.apache.falcon:falcon-oozie-el-extension:jar:0.5-incubating: Could not find artifact org.apache.oozie:oozie-core:jar:4.0.1-falcon in central (http://repo1.maven.org/maven2) -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project falcon-oozie-el-extension: Could not resolve dependencies for project org.apache.falcon:falcon-oozie-el-extension:jar:0.5-incubating: Could not find artifact org.apache.oozie:oozie-core:jar:4.0.1-falcon in central Testcase: - download Falcon v0.5 - use above mvn options -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5629) ClosedChannelException from DefaultUpdateCheckManager.read
[
https://jira.codehaus.org/browse/MNG-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354684#comment-354684
]
Tony Reix commented on MNG-5629:
For my projects, dealing with Hadoop, I always use Maven v3.2.1 .
$ mvn --version
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T12:37:52-05:00)
Maven home: /opt/apache-maven-3.2.1
> ClosedChannelException from DefaultUpdateCheckManager.read
> --
>
> Key: MNG-5629
> URL: https://jira.codehaus.org/browse/MNG-5629
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.2.1
> Environment: Windows 7, Java 7 updated 25
>Reporter: Anthony Whitford
> Attachments: xy.tar.gz
>
>
> I ran a build in debug mode ({{mvn -X}}) and noticed the following bug
> (repeatedly):
> {noformat}
> [DEBUG] Error releasing shared lock for resolution tracking file:
> C:\Users\awhitford\.m2\repository\org\apache\maven\plugins\maven-war-plugin\resolver-status.properties
> java.nio.channels.ClosedChannelException
> at sun.nio.ch.FileLockImpl.release(FileLockImpl.java:58)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.read(DefaultUpdateCheckManager.java:396)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:323)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:159)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.isUpdateRequired(DefaultUpdateCheckManager.java:148)
> at
> org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:127)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:435)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:425)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupArtifactVersions(DefaultVersionsHelper.java:229)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupPluginUpdates(DefaultVersionsHelper.java:727)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupPluginsUpdates(DefaultVersionsHelper.java:706)
> at
> org.codehaus.mojo.versions.PluginUpdatesReport.doGenerateReport(PluginUpdatesReport.java:103)
> at
> org.codehaus.mojo.versions.AbstractVersionsReport.executeReport(AbstractVersionsReport.java:253)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:228)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 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:108)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.class
[jira] (MNG-5629) ClosedChannelException from DefaultUpdateCheckManager.read
[
https://jira.codehaus.org/browse/MNG-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354683#comment-354683
]
Tony Reix commented on MNG-5629:
I've tried to use IBM JVM 1.6 for compiling Falcon on Ubuntu/x86_64.
I've got the same ClosedChannelException, several times (24 !).
Compilation ends with an error.
export HADOOP_VERSION=2.4.1
export HADOOP_PROFILE=hadoop-2
export OOZIE_VERSION=4.0.1
mvn -X compile -P $HADOOP_PROFILE -Dhadoop.version=$HADOOP_VERSION
-Doozie.version=$OOZIE_VERSION -Doozie.forcebuild=false -DskipTests
...
[DEBUG] Determining update check for artifact asm:asm
(/home/reixt/.m2/repository/asm/asm/maven-metadata-central.xml) from central
(http://repo1.maven.org/maven2)
[DEBUG] Searching for central.maven-metadata-central.xml.lastUpdated in
resolution tracking file.
[DEBUG] Reading resolution-state from:
/home/reixt/.m2/repository/asm/asm/resolver-status.properties
[DEBUG] Error releasing shared lock for resolution tracking file:
/home/reixt/.m2/repository/asm/asm/resolver-status.properties
java.nio.channels.ClosedChannelException
at sun.nio.ch.FileLockImpl.release(FileLockImpl.java:47)
at
org.apache.maven.repository.legacy.DefaultUpdateCheckManager.read(DefaultUpdateCheckManager.java:396)
at
org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:323)
at
org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:159)
at
org.apache.maven.repository.legacy.DefaultUpdateCheckManager.isUpdateRequired(DefaultUpdateCheckManager.java:148)
...
[INFO] Apache Falcon Oozie EL Extension .. FAILURE [ 26.935 s]
[INFO] Apache Falcon Embedded Hadoop - Test Cluster .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 17:52 min
[INFO] Finished at: 2014-10-20T10:18:30-05:00
[INFO] Final Memory: 38M/181M
[INFO]
[ERROR] Failed to execute goal on project falcon-oozie-el-extension: Could not
resolve dependencies for project
org.apache.falcon:falcon-oozie-el-extension:jar:0.5-incubating: Could not find
artifact org.apache.oozie:oozie-core:jar:4.0.1-falcon in central
(http://repo1.maven.org/maven2) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
on project falcon-oozie-el-extension: Could not resolve dependencies for
project org.apache.falcon:falcon-oozie-el-extension:jar:0.5-incubating: Could
not find artifact org.apache.oozie:oozie-core:jar:4.0.1-falcon in central
(http://repo1.maven.org/maven2)
> ClosedChannelException from DefaultUpdateCheckManager.read
> --
>
> Key: MNG-5629
> URL: https://jira.codehaus.org/browse/MNG-5629
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.2.1
> Environment: Windows 7, Java 7 updated 25
>Reporter: Anthony Whitford
> Attachments: xy.tar.gz
>
>
> I ran a build in debug mode ({{mvn -X}}) and noticed the following bug
> (repeatedly):
> {noformat}
> [DEBUG] Error releasing shared lock for resolution tracking file:
> C:\Users\awhitford\.m2\repository\org\apache\maven\plugins\maven-war-plugin\resolver-status.properties
> java.nio.channels.ClosedChannelException
> at sun.nio.ch.FileLockImpl.release(FileLockImpl.java:58)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.read(DefaultUpdateCheckManager.java:396)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:323)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:159)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.isUpdateRequired(DefaultUpdateCheckManager.java:148)
> at
> org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:127)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:435)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:425)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupArtifactVersions(DefaultVersionsHelper.java:229)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupPluginUpdates(DefaultVersionsHelper.java:727)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupPluginsUpdates(DefaultVersionsHelper.java:706)
> at
> org.codehaus.mojo.versions.Plug
[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation
[
https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354678#comment-354678
]
Andrew Phillips commented on SUREFIRE-654:
--
We're also running into this with Apache jclouds, so it would be great to see
some movement here.
I understand [~agudian]'s comment about trying to keep the change minimal, but
looking at the PR it's indeed a small change which seems to be (this coming
from someone without much knowledge of the Surefire internals) "in the right
place".
Is there some existing functionality that is working correctly that this PR is
breaking?
> Surefire does not recognize successful tests using TestNG with the
> invocationCount and successPercentage parameters on the @Test annotation
> ---
>
> Key: SUREFIRE-654
> URL: https://jira.codehaus.org/browse/SUREFIRE-654
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.6
> Environment: Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0-18
> Java home: /usr/lib/jvm/java-6-openjdk/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix"
> Ubuntu 10.10
>Reporter: Steve Stodola
> Attachments: bugtest.tar.gz, surefire654.diff
>
>
> Surefire does not recognize successful tests using TestNG with the
> invocationCount and successPercentage parameters on the @Test annotation.
> BugTest.java in the attached file has an invocationCount = 100 with a
> successPercentage = 1. 1 test in 100 needs to pass for the test to be
> considered successful. However when running *{{mvn clean test}}* Surefire
> reports the tests as failed. The generated report shows the tests as passing.
> Surefire should be identifying this test as passing.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5629) ClosedChannelException from DefaultUpdateCheckManager.read
[
https://jira.codehaus.org/browse/MNG-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354677#comment-354677
]
Tony Reix commented on MNG-5629:
Hi
What is the status of this issue today ?
I was working on the port of Falcon on PPC64 when it appeared. I'm now blocked.
First, I was on RHEL7/PPC64BE: this Maven error was not there, and I've been
able to compile and run tests, with IBM JVM v1.6 .
Then, I moved to Ubuntu/PPC64LE, with IBM JVM 1.7, and the issue appeared.
I then tried on Ubuntu/x86_64, with IBM JVM and then Oracle JVM, v1.7, and the
issue was there too.
I gonna try with Java v1.6 on Ubuntu/x86_64 asap.
Traces show the issue when using -X only.
Example of traces, on Ubuntu/x86_64:
[DEBUG] Determining update check for artifact asm:asm
(/home/reixt/.m2/repository/asm/asm/maven-metadata-DN_M2_Repo.xml) from
DN_M2_Repo (http://www.datanucleus.org/downloads/maven2/)
[DEBUG] Searching for DN_M2_Repo.maven-metadata-DN_M2_Repo.xml.lastUpdated in
resolution tracking file.
[DEBUG] Reading resolution-state from:
/home/reixt/.m2/repository/asm/asm/resolver-status.properties
[DEBUG] Error releasing shared lock for resolution tracking file:
/home/reixt/.m2/repository/asm/asm/resolver-status.properties
java.nio.channels.ClosedChannelException
at sun.nio.ch.FileLockImpl.release(FileLockImpl.java:70)
at
org.apache.maven.repository.legacy.DefaultUpdateCheckManager.read(DefaultUpdateCheckManager.java:396)
at
org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:323)
at
org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:159)
at
org.apache.maven.repository.legacy.DefaultUpdateCheckManager.isUpdateRequired(DefaultUpdateCheckManager.java:148)
> ClosedChannelException from DefaultUpdateCheckManager.read
> --
>
> Key: MNG-5629
> URL: https://jira.codehaus.org/browse/MNG-5629
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.2.1
> Environment: Windows 7, Java 7 updated 25
>Reporter: Anthony Whitford
> Attachments: xy.tar.gz
>
>
> I ran a build in debug mode ({{mvn -X}}) and noticed the following bug
> (repeatedly):
> {noformat}
> [DEBUG] Error releasing shared lock for resolution tracking file:
> C:\Users\awhitford\.m2\repository\org\apache\maven\plugins\maven-war-plugin\resolver-status.properties
> java.nio.channels.ClosedChannelException
> at sun.nio.ch.FileLockImpl.release(FileLockImpl.java:58)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.read(DefaultUpdateCheckManager.java:396)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:323)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.readLastUpdated(DefaultUpdateCheckManager.java:159)
> at
> org.apache.maven.repository.legacy.DefaultUpdateCheckManager.isUpdateRequired(DefaultUpdateCheckManager.java:148)
> at
> org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:127)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:435)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:425)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupArtifactVersions(DefaultVersionsHelper.java:229)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupPluginUpdates(DefaultVersionsHelper.java:727)
> at
> org.codehaus.mojo.versions.api.DefaultVersionsHelper.lookupPluginsUpdates(DefaultVersionsHelper.java:706)
> at
> org.codehaus.mojo.versions.PluginUpdatesReport.doGenerateReport(PluginUpdatesReport.java:103)
> at
> org.codehaus.mojo.versions.AbstractVersionsReport.executeReport(AbstractVersionsReport.java:253)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:228)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.jav
[jira] (MEAR-201) Exception during parallel execution (
[
https://jira.codehaus.org/browse/MEAR-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354673#comment-354673
]
Kristian Rosenvold commented on MEAR-201:
-
You may want to test the PLXCOMP-258 fix on this one ΓΈ
> Exception during parallel execution (
> -
>
> Key: MEAR-201
> URL: https://jira.codehaus.org/browse/MEAR-201
> Project: Maven Ear Plugin
> Issue Type: Bug
> Environment: Maven 3.1.1
> -T 4.0
> maven-ear-plugin:2.9.1
>Reporter: Karl-Heinz Marbaise
>
> {code}
> 00:15:15.602 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-ear-plugin:2.9.1:ear (default-ear) on project
> xyz-ear: Execution default-ear of goal
> org.apache.maven.plugins:maven-ear-plugin:2.9.1:ear failed: file mode must
> be 3 or 4 characters -> [Help 1]
> 00:15:15.602 org.apache.maven.lifecycle.LifecycleExecutionException: Failed
> to execute goal org.apache.maven.plugins:maven-ear-plugin:2.9.1:ear
> (default-ear) on project xyz-ear: Execution default-ear of goal
> org.apache.maven.plugins:maven-ear-plugin:2.9.1:ear failed: file mode must
> be 3 or 4 characters
> 00:15:15.602 at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 00:15:15.602 at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 00:15:15.602 at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 00:15:15.602 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> 00:15:15.602 at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:169)
> 00:15:15.602 at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:165)
> 00:15:15.602 at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
> 00:15:15.602 at java.util.concurrent.FutureTask.run(FutureTask.java:149)
> 00:15:15.602 at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452)
> 00:15:15.602 at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
> 00:15:15.602 at java.util.concurrent.FutureTask.run(FutureTask.java:149)
> 00:15:15.602 at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
> 00:15:15.602 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
> 00:15:15.602 at java.lang.Thread.run(Thread.java:770)
> 00:15:15.602 Caused by: org.apache.maven.plugin.PluginExecutionException:
> Execution default-ear of goal
> org.apache.maven.plugins:maven-ear-plugin:2.9.1:ear failed: file mode must
> be 3 or 4 characters
> 00:15:15.602 at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115)
> 00:15:15.602 at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 00:15:15.602 ... 13 more
> 00:15:15.602 Caused by: java.lang.IllegalArgumentException: file mode must
> be 3 or 4 characters
> 00:15:15.602 at
> org.codehaus.plexus.archiver.util.FilePermissionUtils.getFilePermissionFromMode(FilePermissionUtils.java:55)
> 00:15:15.602 at
> org.codehaus.plexus.archiver.util.ArchiveEntryUtils.applyPermissionsWithJvm(ArchiveEntryUtils.java:133)
> 00:15:15.602 at
> org.codehaus.plexus.archiver.util.ArchiveEntryUtils.chmod(ArchiveEntryUtils.java:61)
> 00:15:15.602 at
> org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFile(AbstractZipUnArchiver.java:238)
> 00:15:15.602 at
> org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFileIfIncluded(AbstractZipUnArchiver.java:185)
> 00:15:15.602 at
> org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.execute(AbstractZipUnArchiver.java:149)
> 00:15:15.602 at
> org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:120)
> 00:15:15.602 at
> org.apache.maven.plugin.ear.EarMojo.changeManifestClasspath(EarMojo.java:669)
> 00:15:15.602 at org.apache.maven.plugin.ear.EarMojo.execute(EarMojo.java:338)
> 00:15:15.602 at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> 00:15:15.602 ... 14 more
> 00:15:15.603 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-ear-plugin:2.9.1:ear (default-ear) on project
> abc-ear: Execution default-ear of goal
> org.apache.maven.plugins:maven-ear-plugin:2.9.1:ear failed: file mode must
> be 3 or 4 characters -> [Help 1]
> 00:15:15.603 org.apache.maven.lifecycle.LifecycleExecutionException: Failed
> to execute goal org.apache.maven.plugins:maven-ear-plugin:2.9.1:ear
> (default-ear) on project abc-ear: Execution default-ear of goal
> org.apache.maven.plugins:maven-ear-plugin:2.9.1:ear failed: file mode must
> be 3 or 4 characters
> 00:15:15.603 a
[jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management
[
https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354657#comment-354657
]
wesson commented on MSITE-604:
--
Same problem for me.
> Properties from settings.xml are not recognized in site distribution
> management
>
>
> Key: MSITE-604
> URL: https://jira.codehaus.org/browse/MSITE-604
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 3.0
> Environment: Apache Maven 2.2.1 and 3.0.3
>Reporter: Marcin Kuthan
> Fix For: backlog
>
> Attachments: MSITE-604-it.patch, MSITE-604-it.patch,
> MSITE-604-it.patch, MSITE-604-maven3-2.patch, MSITE-604-maven3.patch,
> MSITE-604.tgz
>
>
> My distribution management section looks like:
> {code}
>
>
>${acme-corporate-pom.siteRepositoryId}
>${acme-corporate-pom.siteRepositoryUrl}
>
>
> {code}
> Where the default property values are defined in the pom:
> {code}
>
>
> acme-site
>
> scp://sites.intranet.acme.com/var/www
>
> {code}
> I'm able redefine properties from command line, the provided repository is
> used instead default one:
> {code}
> mvn site:site site:deploy
> -Dacme-corporate-pom.siteRepositoryUrl=scp://somehost/var/www/sites
> -Dacme-corporate-pom.siteRepositoryId=somehost
> {code}
> But when I redefine properties in the profile in {{settings.xml}}, they are
> ignored. The profile is activated in {{ It looks, than only m-site-p ignores properties defined in the
> {{settings.xml}} file. m-deploy-p recognizes properties as I expected
> (distribution management section for articats deployment is configured in
> similar way to site deployment).
> --
> Marcin Kuthan
> Maven For Enterprise - http://code.google.com/p/m4enterprise/
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
