[jira] Created: (MRELEASE-666) release:prepare can fail during rewrite-poms-for-development phase if a property matches the version being released
release:prepare can fail during rewrite-poms-for-development phase if a
property matches the version being released
---
Key: MRELEASE-666
URL: http://jira.codehaus.org/browse/MRELEASE-666
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.1
Environment: Linux
Reporter: Marius Dumitru Florea
Attachments: maven-release-prepare-debug-log.txt
Executing
{noformat}
mvn release:prepare -DautoVersionSubmodules=true -Pci
{noformat}
against http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/ @r35313 in
order to create
http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-3.0-milestone-3/
fails with the attached log (I attached only the final part of the console
log) when using {{3.0-milestone-3}} as release version. Prepare succeeds if
release version is {{3.0-test-3}}. In other words release:prepare fails if the
version being released matches the {{commons.version}} property defined in the
parent pom. Note that after release:prepare fails all poms are ready to be
committed, i.e. I just had to commit them to finish the release:prepare , so it
looks like release:prepare manages to rewrite the poms for next development
iteration but fails just before committing them for some obscure reason.
I was able to reproduce this with both maven 2.2.1 and 3.0.3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-666) release:prepare can fail during rewrite-poms-for-development phase if a property matches the version being released
[
http://jira.codehaus.org/browse/MRELEASE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259586#action_259586
]
Vincent Massol commented on MRELEASE-666:
-
The parent POM has:
{noformat}
...
3.0-milestone-3
3.0-milestone-3
...
{noformat}
And the error we get is:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on
project xwiki-core-parent: The version could not be updated: ${commons.version}
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on
project xwiki-core-parent: The version could not be updated: ${commons.version}
{noformat}
> release:prepare can fail during rewrite-poms-for-development phase if a
> property matches the version being released
> ---
>
> Key: MRELEASE-666
> URL: http://jira.codehaus.org/browse/MRELEASE-666
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.1
> Environment: Linux
>Reporter: Marius Dumitru Florea
> Attachments: maven-release-prepare-debug-log.txt
>
>
> Executing
> {noformat}
> mvn release:prepare -DautoVersionSubmodules=true -Pci
> {noformat}
> against http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/ @r35313 in
> order to create
> http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-3.0-milestone-3/
> fails with the attached log (I attached only the final part of the console
> log) when using {{3.0-milestone-3}} as release version. Prepare succeeds if
> release version is {{3.0-test-3}}. In other words release:prepare fails if
> the version being released matches the {{commons.version}} property defined
> in the parent pom. Note that after release:prepare fails all poms are ready
> to be committed, i.e. I just had to commit them to finish the release:prepare
> , so it looks like release:prepare manages to rewrite the poms for next
> development iteration but fails just before committing them for some obscure
> reason.
> I was able to reproduce this with both maven 2.2.1 and 3.0.3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-666) release:prepare can fail during rewrite-poms-for-development phase if a property matches the version being released
[
http://jira.codehaus.org/browse/MRELEASE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259587#action_259587
]
Marius Dumitru Florea commented on MRELEASE-666:
An important detail is that release:prepare succeeds with {{3.0-milestone-3}}
if I use {{-DdryRun=true}} and maven 2.2.1. With maven 3.0.3 it fails both when
run for real and on simulation mode.
> release:prepare can fail during rewrite-poms-for-development phase if a
> property matches the version being released
> ---
>
> Key: MRELEASE-666
> URL: http://jira.codehaus.org/browse/MRELEASE-666
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.1
> Environment: Linux
>Reporter: Marius Dumitru Florea
> Attachments: maven-release-prepare-debug-log.txt
>
>
> Executing
> {noformat}
> mvn release:prepare -DautoVersionSubmodules=true -Pci
> {noformat}
> against http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/ @r35313 in
> order to create
> http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-3.0-milestone-3/
> fails with the attached log (I attached only the final part of the console
> log) when using {{3.0-milestone-3}} as release version. Prepare succeeds if
> release version is {{3.0-test-3}}. In other words release:prepare fails if
> the version being released matches the {{commons.version}} property defined
> in the parent pom. Note that after release:prepare fails all poms are ready
> to be committed, i.e. I just had to commit them to finish the release:prepare
> , so it looks like release:prepare manages to rewrite the poms for next
> development iteration but fails just before committing them for some obscure
> reason.
> I was able to reproduce this with both maven 2.2.1 and 3.0.3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MJAVADOC-311) Aggregated javadoc report not generated for multi-module project at sub-level if run from parent level.
[
http://jira.codehaus.org/browse/MJAVADOC-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl moved MSITE-518 to MJAVADOC-311:
--
Component/s: (was: multi module)
(was: inheritance)
Affects Version/s: (was: 3.0-beta-3)
2.7
Key: MJAVADOC-311 (was: MSITE-518)
Project: Maven 2.x Javadoc Plugin (was: Maven 2.x and 3.x Site
Plugin)
> Aggregated javadoc report not generated for multi-module project at sub-level
> if run from parent level.
> ---
>
> Key: MJAVADOC-311
> URL: http://jira.codehaus.org/browse/MJAVADOC-311
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.7
> Environment: Windows Vista x64, JDK 6u22, Maven 3.0
>Reporter: André Fügenschuh
> Attachments: maven3-site-javadoc-testcase.zip
>
>
> With a +multi-module project design+ (cf. attached testcase):
> {noformat}
> - parent(pom)
> + library (pom) // javadoc:aggregate
> + module-a (jar)
> + module-b (jar)
> + application (jar) // javadoc:javadoc
> {noformat}
> run
> {{mvn site}} | {{mvn -DstagingDirectory=\[dir\] site:stage}}
> at _parent_ level.
> +Result:+
> Aggregated javadocs for _library_ are *not* generated (but are properly done
> if {{mvn site}} is run at _library_ level itself), while javadocs at
> _application_ level are generated.
> OT: as appropriate {{}} sections are declared (cf. attached
> testcase), {{mvn compile}} runs as expected at _parent_ level.
> This is a follow-up to MJAVADOC-181, which, although marked as resolved, has
> never been working for me using the _old_ site/reports configuration for
> Maven 2.2.1 / Site plugin 2.1.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHECKSTYLE-155) Checkstyle plugin fails on ubuntu with maven 3
Checkstyle plugin fails on ubuntu with maven 3
--
Key: MCHECKSTYLE-155
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-155
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.6, 2.5
Environment: Ubuntu 10.10
$ mvn -version
Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
Default locale: en_DK, platform encoding: UTF-8
OS name: "linux", version: "2.6.35-27-generic", arch: "amd64", family: "unix"
Reporter: Paul Nyheim
Priority: Critical
Checkstyle plugin fails on Ubuntu with the following error message:
{noformat}
$ mvn checkstyle:checkstyle
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building myartifactid 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-checkstyle-plugin:2.5:checkstyle (default-cli) @ myartifactid
---
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.311s
[INFO] Finished at: Thu Mar 10 14:01:14 CET 2011
[INFO] Final Memory: 8M/105M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle (default-cli)
on project myartifactid: Execution
default-cli of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle failed: An API
incompatibility was encountered while
executing org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle:
java.lang.ClassFormatError: Method ""
in class com/google/common/collect/Sets$SetView has illegal signature "()b"
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.5
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/home/pauln/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.jar
[ERROR] urls[1] =
file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.6/maven-reporting-api-2.0.6.jar
[ERROR] urls[2] =
file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.0.4.3/maven-reporting-impl-2.0.4.3.jar
[ERROR] urls[3] =
file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar
[ERROR] urls[4] =
file:/home/pauln/.m2/repository/commons-validator/commons-validator/1.2.0/commons-validator-1.2.0.jar
[ERROR] urls[5] =
file:/home/pauln/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
[ERROR] urls[6] =
file:/home/pauln/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
[ERROR] urls[7] =
file:/home/pauln/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
[ERROR] urls[8] =
file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.0/doxia-sink-api-1.0.jar
[ERROR] urls[9] =
file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar
[ERROR] urls[10] =
file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar
[ERROR] urls[11] =
file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
[ERROR] urls[12] =
file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar
[ERROR] urls[13] =
file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar
[ERROR] urls[14] =
file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0/doxia-module-xdoc-1.0.jar
[ERROR] urls[15] =
file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0/doxia-module-xhtml-1.0.jar
[ERROR] urls[16] =
file:/home/pauln/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar
[ERROR] urls[17] =
file:/home/pauln/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
[ERROR] urls[18] =
file:/home/pauln/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[19] =
file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-resources/1.0-alpha-6/plexus-resources-1.0-alpha-6.jar
[ERROR] urls[20] =
file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar
[ERROR] urls[21] =
file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar
[ERROR] urls[22] =
file:/home/pauln/.m2/repository/checkstyle/checkstyle/5
[jira] Commented: (MCHECKSTYLE-155) Checkstyle plugin fails on ubuntu with maven 3
[
http://jira.codehaus.org/browse/MCHECKSTYLE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259620#action_259620
]
Paul Nyheim commented on MCHECKSTYLE-155:
-
Just realized that I attached output from running with version 2.5
This is the corresponding error message from 2.6:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.6:checkstyle (default-cli)
on project myartifactid: Execution default-cli of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.6:checkstyle failed: Unable
to load the mojo 'checkstyle' in the plugin
'org.apache.maven.plugins:maven-checkstyle-plugin:2.6'. A required class is
missing: org.apache.maven.plugin.checkstyle.CheckstyleReport
{noformat}
> Checkstyle plugin fails on ubuntu with maven 3
> --
>
> Key: MCHECKSTYLE-155
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-155
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5, 2.6
> Environment: Ubuntu 10.10
> $ mvn -version
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_DK, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35-27-generic", arch: "amd64", family: "unix"
>Reporter: Paul Nyheim
>Priority: Critical
>
> Checkstyle plugin fails on Ubuntu with the following error message:
> {noformat}
> $ mvn checkstyle:checkstyle
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building myartifactid 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (default-cli) @
> myartifactid ---
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.311s
> [INFO] Finished at: Thu Mar 10 14:01:14 CET 2011
> [INFO] Final Memory: 8M/105M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle (default-cli)
> on project myartifactid: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle failed: An
> API incompatibility was encountered while
> executing org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle:
> java.lang.ClassFormatError: Method ""
> in class com/google/common/collect/Sets$SetView has illegal signature "()b"
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.5
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/pauln/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.jar
> [ERROR] urls[1] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.6/maven-reporting-api-2.0.6.jar
> [ERROR] urls[2] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.0.4.3/maven-reporting-impl-2.0.4.3.jar
> [ERROR] urls[3] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar
> [ERROR] urls[4] =
> file:/home/pauln/.m2/repository/commons-validator/commons-validator/1.2.0/commons-validator-1.2.0.jar
> [ERROR] urls[5] =
> file:/home/pauln/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
> [ERROR] urls[6] =
> file:/home/pauln/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
> [ERROR] urls[7] =
> file:/home/pauln/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> [ERROR] urls[8] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.0/doxia-sink-api-1.0.jar
> [ERROR] urls[9] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar
> [ERROR] urls[10] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar
> [ERROR] urls[11] =
> file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
> [ERROR] urls[12] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar
> [ERROR] urls[13] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar
> [ERROR] urls[14] =
[jira] Commented: (MCHECKSTYLE-155) Checkstyle plugin fails on ubuntu with maven 3
[
http://jira.codehaus.org/browse/MCHECKSTYLE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259623#action_259623
]
Dennis Lundberg commented on MCHECKSTYLE-155:
-
Can you please run 'mvn clean' on your test project, then zip it up and attach
it to this issue?
> Checkstyle plugin fails on ubuntu with maven 3
> --
>
> Key: MCHECKSTYLE-155
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-155
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5, 2.6
> Environment: Ubuntu 10.10
> $ mvn -version
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_DK, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35-27-generic", arch: "amd64", family: "unix"
>Reporter: Paul Nyheim
>Priority: Critical
>
> Checkstyle plugin fails on Ubuntu with the following error message:
> {noformat}
> $ mvn checkstyle:checkstyle
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building myartifactid 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (default-cli) @
> myartifactid ---
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.311s
> [INFO] Finished at: Thu Mar 10 14:01:14 CET 2011
> [INFO] Final Memory: 8M/105M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle (default-cli)
> on project myartifactid: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle failed: An
> API incompatibility was encountered while
> executing org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle:
> java.lang.ClassFormatError: Method ""
> in class com/google/common/collect/Sets$SetView has illegal signature "()b"
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.5
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/pauln/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.jar
> [ERROR] urls[1] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.6/maven-reporting-api-2.0.6.jar
> [ERROR] urls[2] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.0.4.3/maven-reporting-impl-2.0.4.3.jar
> [ERROR] urls[3] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar
> [ERROR] urls[4] =
> file:/home/pauln/.m2/repository/commons-validator/commons-validator/1.2.0/commons-validator-1.2.0.jar
> [ERROR] urls[5] =
> file:/home/pauln/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
> [ERROR] urls[6] =
> file:/home/pauln/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
> [ERROR] urls[7] =
> file:/home/pauln/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> [ERROR] urls[8] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.0/doxia-sink-api-1.0.jar
> [ERROR] urls[9] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar
> [ERROR] urls[10] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar
> [ERROR] urls[11] =
> file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
> [ERROR] urls[12] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar
> [ERROR] urls[13] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar
> [ERROR] urls[14] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0/doxia-module-xdoc-1.0.jar
> [ERROR] urls[15] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0/doxia-module-xhtml-1.0.jar
> [ERROR] urls[16] =
> file:/home/pauln/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar
> [ERROR] urls[17] =
> file:/home/pauln/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4
[jira] Updated: (MCHECKSTYLE-155) Checkstyle plugin fails on ubuntu with maven 3
[
http://jira.codehaus.org/browse/MCHECKSTYLE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Nyheim updated MCHECKSTYLE-155:
Attachment: myartifactid.zip
zipped up copy of my test project used to reproduce the problem
unzip on ubuntu, run mvn checkstyle:checkstyle to reproduce
> Checkstyle plugin fails on ubuntu with maven 3
> --
>
> Key: MCHECKSTYLE-155
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-155
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5, 2.6
> Environment: Ubuntu 10.10
> $ mvn -version
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_DK, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35-27-generic", arch: "amd64", family: "unix"
>Reporter: Paul Nyheim
>Priority: Critical
> Attachments: myartifactid.zip
>
>
> Checkstyle plugin fails on Ubuntu with the following error message:
> {noformat}
> $ mvn checkstyle:checkstyle
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building myartifactid 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (default-cli) @
> myartifactid ---
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.311s
> [INFO] Finished at: Thu Mar 10 14:01:14 CET 2011
> [INFO] Final Memory: 8M/105M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle (default-cli)
> on project myartifactid: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle failed: An
> API incompatibility was encountered while
> executing org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle:
> java.lang.ClassFormatError: Method ""
> in class com/google/common/collect/Sets$SetView has illegal signature "()b"
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.5
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/pauln/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.jar
> [ERROR] urls[1] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.6/maven-reporting-api-2.0.6.jar
> [ERROR] urls[2] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.0.4.3/maven-reporting-impl-2.0.4.3.jar
> [ERROR] urls[3] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar
> [ERROR] urls[4] =
> file:/home/pauln/.m2/repository/commons-validator/commons-validator/1.2.0/commons-validator-1.2.0.jar
> [ERROR] urls[5] =
> file:/home/pauln/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
> [ERROR] urls[6] =
> file:/home/pauln/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
> [ERROR] urls[7] =
> file:/home/pauln/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> [ERROR] urls[8] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.0/doxia-sink-api-1.0.jar
> [ERROR] urls[9] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar
> [ERROR] urls[10] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar
> [ERROR] urls[11] =
> file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
> [ERROR] urls[12] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar
> [ERROR] urls[13] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar
> [ERROR] urls[14] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0/doxia-module-xdoc-1.0.jar
> [ERROR] urls[15] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0/doxia-module-xhtml-1.0.jar
> [ERROR] urls[16] =
> file:/home/pauln/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar
> [ERROR] urls[17] =
> file:/home/pauln/.m2/repositor
[jira] Created: (MNGSITE-134) Maven Guide to relocation does not work for Maven Central
Maven Guide to relocation does not work for Maven Central - Key: MNGSITE-134 URL: http://jira.codehaus.org/browse/MNGSITE-134 Project: Maven Project Web Site Issue Type: Bug Reporter: Dennis Lundberg The instructions at http://maven.apache.org/guides/mini/guide-relocation.html can not be used for artifacts in Maven Central repository, because the policy of the Central repository prevents making changes to already published POMs. You are simply not allowed to add relocation information to POMs for old versions. Add a prominent note explaining this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-155) Checkstyle plugin fails on ubuntu with maven 3
[
http://jira.codehaus.org/browse/MCHECKSTYLE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259625#action_259625
]
Benjamin Bentmann commented on MCHECKSTYLE-155:
---
I suggest to clean the local repo and retry, watching the log closely for
network/checksum errors. Those errors smell like corrupt JARs.
> Checkstyle plugin fails on ubuntu with maven 3
> --
>
> Key: MCHECKSTYLE-155
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-155
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5, 2.6
> Environment: Ubuntu 10.10
> $ mvn -version
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_DK, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35-27-generic", arch: "amd64", family: "unix"
>Reporter: Paul Nyheim
>Priority: Critical
> Attachments: myartifactid.zip
>
>
> Checkstyle plugin fails on Ubuntu with the following error message:
> {noformat}
> $ mvn checkstyle:checkstyle
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building myartifactid 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (default-cli) @
> myartifactid ---
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.311s
> [INFO] Finished at: Thu Mar 10 14:01:14 CET 2011
> [INFO] Final Memory: 8M/105M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle (default-cli)
> on project myartifactid: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle failed: An
> API incompatibility was encountered while
> executing org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle:
> java.lang.ClassFormatError: Method ""
> in class com/google/common/collect/Sets$SetView has illegal signature "()b"
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.5
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/pauln/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.jar
> [ERROR] urls[1] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.6/maven-reporting-api-2.0.6.jar
> [ERROR] urls[2] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.0.4.3/maven-reporting-impl-2.0.4.3.jar
> [ERROR] urls[3] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar
> [ERROR] urls[4] =
> file:/home/pauln/.m2/repository/commons-validator/commons-validator/1.2.0/commons-validator-1.2.0.jar
> [ERROR] urls[5] =
> file:/home/pauln/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
> [ERROR] urls[6] =
> file:/home/pauln/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
> [ERROR] urls[7] =
> file:/home/pauln/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> [ERROR] urls[8] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.0/doxia-sink-api-1.0.jar
> [ERROR] urls[9] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar
> [ERROR] urls[10] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar
> [ERROR] urls[11] =
> file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
> [ERROR] urls[12] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar
> [ERROR] urls[13] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar
> [ERROR] urls[14] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0/doxia-module-xdoc-1.0.jar
> [ERROR] urls[15] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0/doxia-module-xhtml-1.0.jar
> [ERROR] urls[16] =
> file:/home/pauln/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar
> [ERROR]
[jira] Commented: (MCHECKSTYLE-155) Checkstyle plugin fails on ubuntu with maven 3
[
http://jira.codehaus.org/browse/MCHECKSTYLE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259627#action_259627
]
Paul Nyheim commented on MCHECKSTYLE-155:
-
I had done that previously, but forgot to bypass our company repository server
(Artifactory). This time, when bypassing Artifactory, both 2.5 and 2.6 works
fine. Seems I have to investigate why Artifactory (or the proxy) corrupts those
files..
Thanks
> Checkstyle plugin fails on ubuntu with maven 3
> --
>
> Key: MCHECKSTYLE-155
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-155
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5, 2.6
> Environment: Ubuntu 10.10
> $ mvn -version
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_DK, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35-27-generic", arch: "amd64", family: "unix"
>Reporter: Paul Nyheim
>Priority: Critical
> Attachments: myartifactid.zip
>
>
> Checkstyle plugin fails on Ubuntu with the following error message:
> {noformat}
> $ mvn checkstyle:checkstyle
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building myartifactid 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (default-cli) @
> myartifactid ---
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.311s
> [INFO] Finished at: Thu Mar 10 14:01:14 CET 2011
> [INFO] Final Memory: 8M/105M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle (default-cli)
> on project myartifactid: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle failed: An
> API incompatibility was encountered while
> executing org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle:
> java.lang.ClassFormatError: Method ""
> in class com/google/common/collect/Sets$SetView has illegal signature "()b"
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.5
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/pauln/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.jar
> [ERROR] urls[1] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.6/maven-reporting-api-2.0.6.jar
> [ERROR] urls[2] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.0.4.3/maven-reporting-impl-2.0.4.3.jar
> [ERROR] urls[3] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar
> [ERROR] urls[4] =
> file:/home/pauln/.m2/repository/commons-validator/commons-validator/1.2.0/commons-validator-1.2.0.jar
> [ERROR] urls[5] =
> file:/home/pauln/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
> [ERROR] urls[6] =
> file:/home/pauln/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
> [ERROR] urls[7] =
> file:/home/pauln/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> [ERROR] urls[8] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.0/doxia-sink-api-1.0.jar
> [ERROR] urls[9] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar
> [ERROR] urls[10] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar
> [ERROR] urls[11] =
> file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
> [ERROR] urls[12] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar
> [ERROR] urls[13] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar
> [ERROR] urls[14] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0/doxia-module-xdoc-1.0.jar
> [ERROR] urls[15] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0/doxia-module-xhtml-1.0.jar
> [ERROR] urls[16] =
> file:/home/pa
[jira] Commented: (MCHECKSTYLE-155) Checkstyle plugin fails on ubuntu with maven 3
[
http://jira.codehaus.org/browse/MCHECKSTYLE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259628#action_259628
]
Dennis Lundberg commented on MCHECKSTYLE-155:
-
Hi Paul,
I was able to successfully run your project on my virtual Ubuntu 10.04 using
Java 5.
> Checkstyle plugin fails on ubuntu with maven 3
> --
>
> Key: MCHECKSTYLE-155
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-155
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5, 2.6
> Environment: Ubuntu 10.10
> $ mvn -version
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_DK, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35-27-generic", arch: "amd64", family: "unix"
>Reporter: Paul Nyheim
>Priority: Critical
> Attachments: myartifactid.zip
>
>
> Checkstyle plugin fails on Ubuntu with the following error message:
> {noformat}
> $ mvn checkstyle:checkstyle
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building myartifactid 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (default-cli) @
> myartifactid ---
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.311s
> [INFO] Finished at: Thu Mar 10 14:01:14 CET 2011
> [INFO] Final Memory: 8M/105M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle (default-cli)
> on project myartifactid: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle failed: An
> API incompatibility was encountered while
> executing org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle:
> java.lang.ClassFormatError: Method ""
> in class com/google/common/collect/Sets$SetView has illegal signature "()b"
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.5
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/pauln/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.jar
> [ERROR] urls[1] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.6/maven-reporting-api-2.0.6.jar
> [ERROR] urls[2] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.0.4.3/maven-reporting-impl-2.0.4.3.jar
> [ERROR] urls[3] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar
> [ERROR] urls[4] =
> file:/home/pauln/.m2/repository/commons-validator/commons-validator/1.2.0/commons-validator-1.2.0.jar
> [ERROR] urls[5] =
> file:/home/pauln/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
> [ERROR] urls[6] =
> file:/home/pauln/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
> [ERROR] urls[7] =
> file:/home/pauln/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> [ERROR] urls[8] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.0/doxia-sink-api-1.0.jar
> [ERROR] urls[9] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar
> [ERROR] urls[10] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar
> [ERROR] urls[11] =
> file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
> [ERROR] urls[12] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar
> [ERROR] urls[13] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar
> [ERROR] urls[14] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0/doxia-module-xdoc-1.0.jar
> [ERROR] urls[15] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0/doxia-module-xhtml-1.0.jar
> [ERROR] urls[16] =
> file:/home/pauln/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar
> [ERROR] urls[17] =
> file:/home/pauln/.m2/repository
[jira] Closed: (MCHECKSTYLE-155) Checkstyle plugin fails on ubuntu with maven 3
[
http://jira.codehaus.org/browse/MCHECKSTYLE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Nyheim closed MCHECKSTYLE-155.
---
Resolution: Not A Bug
Seems as this was an issue on our side with either Artifactory or the
http_proxy corrupting the jars downloaded. :-(
Thanks for your help on sorting out this issue.
> Checkstyle plugin fails on ubuntu with maven 3
> --
>
> Key: MCHECKSTYLE-155
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-155
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5, 2.6
> Environment: Ubuntu 10.10
> $ mvn -version
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_DK, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35-27-generic", arch: "amd64", family: "unix"
>Reporter: Paul Nyheim
>Priority: Critical
> Attachments: myartifactid.zip
>
>
> Checkstyle plugin fails on Ubuntu with the following error message:
> {noformat}
> $ mvn checkstyle:checkstyle
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building myartifactid 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (default-cli) @
> myartifactid ---
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.311s
> [INFO] Finished at: Thu Mar 10 14:01:14 CET 2011
> [INFO] Final Memory: 8M/105M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle (default-cli)
> on project myartifactid: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle failed: An
> API incompatibility was encountered while
> executing org.apache.maven.plugins:maven-checkstyle-plugin:2.5:checkstyle:
> java.lang.ClassFormatError: Method ""
> in class com/google/common/collect/Sets$SetView has illegal signature "()b"
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.5
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/pauln/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.jar
> [ERROR] urls[1] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.6/maven-reporting-api-2.0.6.jar
> [ERROR] urls[2] =
> file:/home/pauln/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.0.4.3/maven-reporting-impl-2.0.4.3.jar
> [ERROR] urls[3] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar
> [ERROR] urls[4] =
> file:/home/pauln/.m2/repository/commons-validator/commons-validator/1.2.0/commons-validator-1.2.0.jar
> [ERROR] urls[5] =
> file:/home/pauln/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
> [ERROR] urls[6] =
> file:/home/pauln/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
> [ERROR] urls[7] =
> file:/home/pauln/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> [ERROR] urls[8] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.0/doxia-sink-api-1.0.jar
> [ERROR] urls[9] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar
> [ERROR] urls[10] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar
> [ERROR] urls[11] =
> file:/home/pauln/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
> [ERROR] urls[12] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar
> [ERROR] urls[13] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar
> [ERROR] urls[14] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0/doxia-module-xdoc-1.0.jar
> [ERROR] urls[15] =
> file:/home/pauln/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0/doxia-module-xhtml-1.0.jar
> [ERROR] urls[16] =
> file:/home/pauln/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar
> [ERROR] urls[17] =
[jira] Updated: (MSITE-312) Interpolation not working in inherited elements
[ http://jira.codehaus.org/browse/MSITE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-312: Attachment: MSITE-312.zip > Interpolation not working in inherited elements > --- > > Key: MSITE-312 > URL: http://jira.codehaus.org/browse/MSITE-312 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: inheritance, site descriptor >Affects Versions: 2.0-beta-7 > Environment: JDK 1.5.0_13 on OS/X 10.5.2 >Reporter: Brian Hanafee > Attachments: example.zip, MSITE-312.zip > > > Properties defined in the local POM are not interpolated into elements of the > site that are inherited. > In the attached example, the property "parentprop" is defined in the parent > POM and "childprop" is defined in the child POM. The parent project has a > site.xml that defines an inherited menu with items that reference both > properties. Only parentprop is interpolated. The child project has an > identical menu and the properties are interpolated correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-312) Interpolation not working in inherited elements
[ http://jira.codehaus.org/browse/MSITE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259636#action_259636 ] Lukas Theussl commented on MSITE-312: - Your use case is not valid. Inherited menus are supposed to be the same for all child projects. If you have module-specific stuff to add you should add a separate menu in the child. In your example project, the parent site will always have an un-resolved link in the menu. I attach a slightly modified version of your example project where I added references to $project.url in the menu. As you see, in the inherited parent menu, this links back to the parent, as expected. If we would implement what you ask for, it would point to the child. MSITE-135 is a completely different issue, it concerns inherited site.xml files, ie where the child project has no site descriptor at all. Here we are talking about inherited menus. As you see from my attached project, the $project.* references are working correctly in inherited menus (tested also with current site-plugin-2.2 and 2.3-SNAPSHOT). > Interpolation not working in inherited elements > --- > > Key: MSITE-312 > URL: http://jira.codehaus.org/browse/MSITE-312 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: inheritance, site descriptor >Affects Versions: 2.0-beta-7 > Environment: JDK 1.5.0_13 on OS/X 10.5.2 >Reporter: Brian Hanafee > Attachments: example.zip, MSITE-312.zip > > > Properties defined in the local POM are not interpolated into elements of the > site that are inherited. > In the attached example, the property "parentprop" is defined in the parent > POM and "childprop" is defined in the child POM. The parent project has a > site.xml that defines an inherited menu with items that reference both > properties. Only parentprop is interpolated. The child project has an > identical menu and the properties are interpolated correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-312) Interpolation not working in inherited elements
[ http://jira.codehaus.org/browse/MSITE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-312. --- Resolution: Won't Fix Assignee: Lukas Theussl > Interpolation not working in inherited elements > --- > > Key: MSITE-312 > URL: http://jira.codehaus.org/browse/MSITE-312 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: inheritance, site descriptor >Affects Versions: 2.0-beta-7 > Environment: JDK 1.5.0_13 on OS/X 10.5.2 >Reporter: Brian Hanafee >Assignee: Lukas Theussl > Attachments: example.zip, MSITE-312.zip > > > Properties defined in the local POM are not interpolated into elements of the > site that are inherited. > In the attached example, the property "parentprop" is defined in the parent > POM and "childprop" is defined in the child POM. The parent project has a > site.xml that defines an inherited menu with items that reference both > properties. Only parentprop is interpolated. The child project has an > identical menu and the properties are interpolated correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-666) release:prepare can fail during rewrite-poms-for-development phase if a property matches the version being released
[
http://jira.codehaus.org/browse/MRELEASE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259643#action_259643
]
Marius Dumitru Florea commented on MRELEASE-666:
{quote}
Note that after release:prepare fails all poms are ready to be committed, i.e.
I just had to commit them to finish the release:prepare, so it looks like
release:prepare manages to rewrite the poms for next development iteration but
fails just before committing them for some obscure reason.
{quote}
Actually I was wrong about this. Most of the POMs were updated but there were a
few that still had {{3.0-milestone-3}} as parent version. So release:prepare
failed in the middle of the rewrite-poms-for-development phase.
> release:prepare can fail during rewrite-poms-for-development phase if a
> property matches the version being released
> ---
>
> Key: MRELEASE-666
> URL: http://jira.codehaus.org/browse/MRELEASE-666
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.1
> Environment: Linux
>Reporter: Marius Dumitru Florea
> Attachments: maven-release-prepare-debug-log.txt
>
>
> Executing
> {noformat}
> mvn release:prepare -DautoVersionSubmodules=true -Pci
> {noformat}
> against http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/ @r35313 in
> order to create
> http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-3.0-milestone-3/
> fails with the attached log (I attached only the final part of the console
> log) when using {{3.0-milestone-3}} as release version. Prepare succeeds if
> release version is {{3.0-test-3}}. In other words release:prepare fails if
> the version being released matches the {{commons.version}} property defined
> in the parent pom. Note that after release:prepare fails all poms are ready
> to be committed, i.e. I just had to commit them to finish the release:prepare
> , so it looks like release:prepare manages to rewrite the poms for next
> development iteration but fails just before committing them for some obscure
> reason.
> I was able to reproduce this with both maven 2.2.1 and 3.0.3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSHADE-95) test-scoped artifact excluded, even if it is also a transitive dep
test-scoped artifact excluded, even if it is also a transitive dep
--
Key: MSHADE-95
URL: http://jira.codehaus.org/browse/MSHADE-95
Project: Maven 2.x Shade Plugin
Issue Type: Bug
Affects Versions: 1.4, 1.3.2
Environment: (cygwin)
Apache Maven 3.0.1 (r1038046; 2010-11-23 05:58:32-0500)
Java version: 1.6.0_23
Java home: C:\Program Files\Java\jdk1.6.0_23\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
Reporter: Alan D. Salewski
A test-scoped artifact is excluded from the final jar, even if that artifact is
also a transitive dependency of some other (non-test-scoped) dep.
{noformat}
MY_POM
|
|
+-- dep A (scope: test)
|
|
+-- dep B (scope: compile)
|
|
+-- dep A (scope: compile)
{noformat}
In the above scenario, I would expect '{{dep A}}' to be included in the final
jar, even though it's in the '{{test}}' scope in my POM. The rationale is that
it is required for '{{dep B}}' to run; its absence will result in a
{{java.lang.ClassNotFoundException}} at runtime.
Behavior observed with maven-shade-plugin versions 1.3.2 and 1.4; other
versions not tested.
I'll put together a test case later tonight when I have more time and attach it
here.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPDF-46) Remove [WARNING] Deprecated API called
[ http://jira.codehaus.org/browse/MPDF-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259685#action_259685 ] Herve Boutemy commented on MPDF-46: --- reports are not run under Maven 3, they cannot emit anything even a warning :) > Remove [WARNING] Deprecated API called > -- > > Key: MPDF-46 > URL: http://jira.codehaus.org/browse/MPDF-46 > Project: Maven 2.x PDF Plugin > Issue Type: Task >Affects Versions: 1.1 >Reporter: Lukas Theussl >Assignee: Herve Boutemy > Fix For: 1.2 > > > Happens when including reports in the pdf. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-577) running only some method of a unit class (with -Dtest=MyClass#myMethod)
[ http://jira.codehaus.org/browse/SUREFIRE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259687#action_259687 ] Jesse Glick commented on SUREFIRE-577: -- Seems to be working well in 2.8 from the staging repo. I have prepared a patch for NetBeans to use this to enable the action Run Focused Test from the editor context menu for a project using Surefire 2.8+. (It already worked if you bypass Maven for running individual tests, which is the default behavior; but there is the option to use Maven + Surefire even for single test suites - useful for people with unusual build setups - which will now work also with single test cases.) I will plan to incorporate in NB 7.1. Thanks! By the way I am the integrator (not original author) of the corresponding feature in Ant 1.8.2. > running only some method of a unit class (with -Dtest=MyClass#myMethod) > --- > > Key: SUREFIRE-577 > URL: http://jira.codehaus.org/browse/SUREFIRE-577 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.8 > > > I definitely don't know if it's possible with junit. > But it's an idea, I have now :-). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANTTASKS-214) maven antlib artifact:dependencies target should support arbitrary setting.xml file location
maven antlib artifact:dependencies target should support arbitrary setting.xml
file location
Key: MANTTASKS-214
URL: http://jira.codehaus.org/browse/MANTTASKS-214
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: dependencies task
Affects Versions: 2.1.1
Environment: Mac OSX, Ant 1.8.1
Reporter: Ed Burns
My use case is that I have a set of common dependencies that I use across many
projects.
In order to save me some typing I created a pom whose sole purpose is to depend
on all
the common dependencies, so that each of my projects can depend on only this
one pom.
The problem is that the pom file gets included in the classpath, an the junit
task shows
an annoying error because it can't make sense of it as a directory or jar file.
A relatively simple testcase to show the issue is this pom.xml:
{code:xml}http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";
xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
4.0.0
foo
bar
1.0
asm
asm-parent
3.1
pom
{code}
An the following build.xml in the same directory:
{code:xml}
${toString:maven2.test.classpath}
{code}
When I run this I expect the output from to list the classpath
consisting of the jars dependencies from {{asm-parent}}. That pom happens to
have no jar dependencies, so I expect the output to be empty. Instead I get
the path of the pom file.
In a more realistic example I will use this as a classpath argument to
and get an error like:
{noformat}
Unable to obtain resource from
/Users/knut/.m2/repository/asm/asm-parent/3.1/asm-parent-3.1.pom:
java.util.zip.ZipException: error in opening zip file
[junit] Unable to obtain resource from
/Users/knut/.m2/repository/asm/asm-parent/3.1/asm-parent-3.1.pom:
[junit] java.util.zip.ZipException: error in opening zip file
[junit] at java.util.zip.ZipFile.open(Native Method)
[junit] at java.util.zip.ZipFile.(ZipFile.java:114)
[junit] at java.util.jar.JarFile.(JarFile.java:135)
[junit] at java.util.jar.JarFile.(JarFile.java:99)
[junit] at
org.apache.tools.ant.AntClassLoader.getResourceURL(AntClassLoader.java:1002)
[junit] at
org.apache.tools.ant.AntClassLoader$ResourceEnumeration.findNextResource(AntClassLoader.java:145)
[junit] at
org.apache.tools.ant.AntClassLoader$ResourceEnumeration.(AntClassLoader.java:109)
[junit] at
org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:949)
[junit] at
org.apache.tools.ant.AntClassLoader.getNamedResources(AntClassLoader.java:918)
[junit] at
org.apache.tools.ant.loader.AntClassLoader5.getResources(AntClassLoader5.java:54)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.checkForkedPath(JUnitTask.java:1135)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeAsForked(JUnitTask.java:1011)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:811)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1808)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:760)
[junit] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
[junit] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
[junit] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:597)
[junit] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[junit] at org.apache.tools.ant.Task.perform(Task.java:348)
[junit] at org.apache.tools.ant.Target.execute(Target.java:390)
[junit] at org.apache.tools.ant.Target.performTasks(Target.java:411)
[junit] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
[junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1366)
[junit] at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[junit] at
org.apache.tools.ant.Project.executeTargets(Project.java:1249)
[junit] at org.apache.tools.ant.Main.runBuild(Main.java:801)
[junit] at org.apache.tools.ant.Main.startAnt(Main.java:218)
[junit] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
[junit] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
{noformat}
When I read MANTTASKS-41 I can't help but think it revolves around the
[jira] Closed: (MANTTASKS-214) maven antlib artifact:dependencies target should support arbitrary setting.xml file location
[
http://jira.codehaus.org/browse/MANTTASKS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ed Burns closed MANTTASKS-214.
--
Resolution: Fixed
I was hoping to clone and customize, but I cannot do that.
> maven antlib artifact:dependencies target should support arbitrary
> setting.xml file location
>
>
> Key: MANTTASKS-214
> URL: http://jira.codehaus.org/browse/MANTTASKS-214
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: dependencies task
>Affects Versions: 2.1.1
> Environment: Mac OSX, Ant 1.8.1
>Reporter: Ed Burns
>
> My use case is that I have a set of common dependencies that I use across
> many projects.
> In order to save me some typing I created a pom whose sole purpose is to
> depend on all
> the common dependencies, so that each of my projects can depend on only this
> one pom.
> The problem is that the pom file gets included in the classpath, an the junit
> task shows
> an annoying error because it can't make sense of it as a directory or jar
> file.
> A relatively simple testcase to show the issue is this pom.xml:
> {code:xml}http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";
> xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> 4.0.0
> foo
> bar
> 1.0
>
>
> asm
> asm-parent
> 3.1
> pom
>
>
>
> {code}
> An the following build.xml in the same directory:
> {code:xml}
>
> xmlns:artifact="antlib:org.apache.maven.artifact.ant">
>
>
> filesetId="test.fileset">
>
>
> ${toString:maven2.test.classpath}
>
>
> {code}
> When I run this I expect the output from to list the classpath
> consisting of the jars dependencies from {{asm-parent}}. That pom happens to
> have no jar dependencies, so I expect the output to be empty. Instead I get
> the path of the pom file.
> In a more realistic example I will use this as a classpath argument to
> and get an error like:
> {noformat}
> Unable to obtain resource from
> /Users/knut/.m2/repository/asm/asm-parent/3.1/asm-parent-3.1.pom:
> java.util.zip.ZipException: error in opening zip file
> [junit] Unable to obtain resource from
> /Users/knut/.m2/repository/asm/asm-parent/3.1/asm-parent-3.1.pom:
> [junit] java.util.zip.ZipException: error in opening zip file
> [junit] at java.util.zip.ZipFile.open(Native Method)
> [junit] at java.util.zip.ZipFile.(ZipFile.java:114)
> [junit] at java.util.jar.JarFile.(JarFile.java:135)
> [junit] at java.util.jar.JarFile.(JarFile.java:99)
> [junit] at
> org.apache.tools.ant.AntClassLoader.getResourceURL(AntClassLoader.java:1002)
> [junit] at
> org.apache.tools.ant.AntClassLoader$ResourceEnumeration.findNextResource(AntClassLoader.java:145)
> [junit] at
> org.apache.tools.ant.AntClassLoader$ResourceEnumeration.(AntClassLoader.java:109)
> [junit] at
> org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:949)
> [junit] at
> org.apache.tools.ant.AntClassLoader.getNamedResources(AntClassLoader.java:918)
> [junit] at
> org.apache.tools.ant.loader.AntClassLoader5.getResources(AntClassLoader5.java:54)
> [junit] at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.checkForkedPath(JUnitTask.java:1135)
> [junit] at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeAsForked(JUnitTask.java:1011)
> [junit] at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:811)
> [junit] at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1808)
> [junit] at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:760)
> [junit] at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [junit] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> [junit] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> [junit] at java.lang.reflect.Method.invoke(Method.java:597)
> [junit] at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [junit] at org.apache.tools.ant.Task.perform(Task.java:348)
> [junit] at org.apache.tools.ant.Target.execute(Target.java:390)
> [junit] at org.apache.tools.ant.Target.performTasks(Target.java:411)
> [junit] at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> [junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1366)
> [junit] at
> org.apache.tools.ant.helper.DefaultExecutor.execut
[jira] Created: (MANTTASKS-215) Need a way to specify settings.xml file
Need a way to specify settings.xml file
---
Key: MANTTASKS-215
URL: http://jira.codehaus.org/browse/MANTTASKS-215
Project: Maven 2.x Ant Tasks
Issue Type: Improvement
Components: dependencies task
Reporter: Ed Burns
Priority: Minor
The docs for this task say:
"The file is first looked for in ${user.home}/.ant/settings.xml, then in
${user.home}/.m2/settings.xml so that the settings can be shared with Maven 2.0
itself."
Their does not appear to be a way to indicate the task should use an arbitrary
settings file, as you have with the --settings command line argument.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-546) "container" field of SiteDeployMojo not populated correctly -> NPE with servers containing configuration
[ http://jira.codehaus.org/browse/MSITE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MSITE-546. -- Resolution: Fixed Fix Version/s: 3.0-beta-4 fixed rev [1080389|http://svn.apache.org/viewvc?rev=1080389&view=rev] > "container" field of SiteDeployMojo not populated correctly -> NPE with > servers containing configuration > > > Key: MSITE-546 > URL: http://jira.codehaus.org/browse/MSITE-546 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3, site:deploy >Affects Versions: 3.0-beta-3 >Reporter: Carl Wilund >Assignee: Olivier Lamy > Fix For: 3.0-beta-4 > > > In SiteDeployMojo, the field "container" is not populated correctly (version > skew with @Requirement?). When configureWagon is subsequently called, IFF the > site deploy server has an entry in settings.xml AND contains a > "configuration" subelement, there will be a NullPointerException thrown (line > 474) when container.lookup is called. > Simple repro: > settings.xml: > ... > > bogus > bogus > bogus > > > > ... > pom.xml: > ... > > > > org.apache.maven.plugins > maven-site-plugin > 3.0-beta-3 > > > > > > bogus > Bogus > sftp://bogus.bogus.org/bogus > > > ... > While this should obviously not work, it should not NPE at line 474. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4565) Multiple profile activation conditions does not work
[
http://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259703#action_259703
]
Peter Goodwine commented on MNG-4565:
-
[Settings Reference|http://maven.apache.org/settings.html#Activation]:
{quote}Activation occurs when all specified criteria have been met, though not
all are required at once.{quote}
Contradicts the POM reference, worse than "not really useful"
> Multiple profile activation conditions does not work
>
>
> Key: MNG-4565
> URL: http://jira.codehaus.org/browse/MNG-4565
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.2.1
> Environment: All platforms.
>Reporter: Nicholas Allen
> Fix For: Issues to be reviewed for 3.x
>
>
> According to the documentation at
> http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html
> a profile is activated when all activation conditions are met (which makes
> sense of course). But when I try to use this it does not work. It seems maven
> does an OR instead of an AND (which is not rearly as useful and is the
> opposite of what the documentation says at the previous link).
> For example, if I have one profile that is activated like this:
>
> false
>
>linux
>
>
> and another profile that is activated like this:
>
> false
>
>linux
>
>
> release
> true
>
>
> Then I would expect the second profile to only be activated if the OS is
> linux and the release property is defined.
> When I run 'mvn help:active-profiles' however, maven shows that both profiles
> are active even though the release property is not defined.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
