[jira] [Updated] (MNG-6072) Cannot build archetypes on Windows
[
https://issues.apache.org/jira/browse/MNG-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated MNG-6072:
Description:
{code}
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
2015-03-13T21:10:27+01:00)
Maven home: C:\Program Files\Java\apache-maven-3.3.1
Java version: 1.8.0_101, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_101\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows server 2012 r2", version: "6.3", arch: "amd64", family: "dos"
[INFO] --- maven-archetype-plugin:2.2:integration-test
(default-integration-test) @ wildfly-camel-archetype-cdi ---
[INFO] Processing Archetype IT project: test-archetype-cdi
[INFO]
[INFO] Using following parameters for creating project from Archetype:
wildfly-camel-archetype-cdi:4.2.0-SNAPSHOT
[INFO]
[INFO] Parameter: groupId, Value: org.wildfly.camel.archetype.test
[INFO] Parameter: artifactId, Value: wildfly-camel-archetype-cdi-test
[INFO] Parameter: version, Value: 1.0
[INFO] Parameter: package, Value: org.wildfly.camel.archetype.test
[INFO] Parameter: packageInPathFormat, Value: org/wildfly/camel/archetype/test
[INFO] Parameter: version-wildfly-arquillian, Value: 1.0.2.Final
[INFO] Parameter: version-jboss-arquillian, Value: 1.1.10.Final
[INFO] Parameter: version-wildfly, Value: 10.0.0.Final
[INFO] Parameter: groupId, Value: org.wildfly.camel.archetype.test
[INFO] Parameter: version-junit, Value: 4.11
[INFO] Parameter: version, Value: 1.0
[INFO] Parameter: version-maven-war-plugin, Value: 2.5
[INFO] Parameter: version-apache-camel, Value: 2.17.2
[INFO] Parameter: package, Value: org.wildfly.camel.archetype.test
[INFO] Parameter: version-wildfly-maven-plugin, Value: 1.1.0.Alpha7
[INFO] Parameter: version-maven-compiler-plugin, Value: 3.1
[INFO] Parameter: artifactId, Value: wildfly-camel-archetype-cdi-test
[INFO] Parameter: version-wildfly-camel, Value: 4.2.0-SNAPSHOT
[INFO] Parameter: version-maven-surefire-plugin, Value: 2.18.1
[INFO] project created from Archetype in dir:
C:\Users\Administrator\git\wildfly-camel\archetypes\archetype-cdi\target\t
est-classes\projects\test-archetype-cdi\project\wildfly-camel-archetype-cdi-test
[INFO] Invoking post-archetype-generation goals: verify -Parq-managed
-Djboss.home=C:\\Users\\Administrator\\git\\wildfl
y-camel\\archetypes\\archetype-cdi\\target\\wildfly-10.0.0.Final
-Dserver.config=standalone.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 10.142 s
[INFO] Finished at: 2016-07-29T11:30:52+02:00
[INFO] Final Memory: 65M/762M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test
(default-integration
-test) on project wildfly-camel-archetype-cdi:
[ERROR] Archetype IT 'test-archetype-cdi' failed: Cannot run additions goals.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-archetype-
plugin:2.2:integration-test (default-integration-test) on project
wildfly-camel-archetype-cdi:
Archetype IT 'test-archetype-cdi' failed: Cannot run additions goals.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
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:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.
java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect
[jira] [Updated] (MNG-6072) Cannot build archetypes on Windows
[
https://issues.apache.org/jira/browse/MNG-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated MNG-6072:
Environment:
{code}
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
2015-03-13T21:10:27+01:00)
Maven home: C:\Program Files\Java\apache-maven-3.3.1
Java version: 1.8.0_101, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_101\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows server 2012 r2", version: "6.3", arch: "amd64", family: "dos"
{code}
was:
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
2015-03-13T21:10:27+01:00)
Maven home: C:\Program Files\Java\apache-maven-3.3.1
Java version: 1.8.0_101, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_101\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows server 2012 r2", version: "6.3", arch: "amd64", family: "dos"
> Cannot build archetypes on Windows
> --
>
> Key: MNG-6072
> URL: https://issues.apache.org/jira/browse/MNG-6072
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.1, 3.3.3, 3.3.9
> Environment: {code}
> Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
> 2015-03-13T21:10:27+01:00)
> Maven home: C:\Program Files\Java\apache-maven-3.3.1
> Java version: 1.8.0_101, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_101\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows server 2012 r2", version: "6.3", arch: "amd64", family:
> "dos"
> {code}
>Reporter: Thomas Diesler
>
> {code}
> [INFO] --- maven-archetype-plugin:2.2:integration-test
> (default-integration-test) @ wildfly-camel-archetype-cdi ---
> [INFO] Processing Archetype IT project: test-archetype-cdi
> [INFO]
>
> [INFO] Using following parameters for creating project from Archetype:
> wildfly-camel-archetype-cdi:4.2.0-SNAPSHOT
> [INFO]
>
> [INFO] Parameter: groupId, Value: org.wildfly.camel.archetype.test
> [INFO] Parameter: artifactId, Value: wildfly-camel-archetype-cdi-test
> [INFO] Parameter: version, Value: 1.0
> [INFO] Parameter: package, Value: org.wildfly.camel.archetype.test
> [INFO] Parameter: packageInPathFormat, Value: org/wildfly/camel/archetype/test
> [INFO] Parameter: version-wildfly-arquillian, Value: 1.0.2.Final
> [INFO] Parameter: version-jboss-arquillian, Value: 1.1.10.Final
> [INFO] Parameter: version-wildfly, Value: 10.0.0.Final
> [INFO] Parameter: groupId, Value: org.wildfly.camel.archetype.test
> [INFO] Parameter: version-junit, Value: 4.11
> [INFO] Parameter: version, Value: 1.0
> [INFO] Parameter: version-maven-war-plugin, Value: 2.5
> [INFO] Parameter: version-apache-camel, Value: 2.17.2
> [INFO] Parameter: package, Value: org.wildfly.camel.archetype.test
> [INFO] Parameter: version-wildfly-maven-plugin, Value: 1.1.0.Alpha7
> [INFO] Parameter: version-maven-compiler-plugin, Value: 3.1
> [INFO] Parameter: artifactId, Value: wildfly-camel-archetype-cdi-test
> [INFO] Parameter: version-wildfly-camel, Value: 4.2.0-SNAPSHOT
> [INFO] Parameter: version-maven-surefire-plugin, Value: 2.18.1
> [INFO] project created from Archetype in dir:
> C:\Users\Administrator\git\wildfly-camel\archetypes\archetype-cdi\target\t
> est-classes\projects\test-archetype-cdi\project\wildfly-camel-archetype-cdi-test
> [INFO] Invoking post-archetype-generation goals: verify -Parq-managed
> -Djboss.home=C:\\Users\\Administrator\\git\\wildfl
> y-camel\\archetypes\\archetype-cdi\\target\\wildfly-10.0.0.Final
> -Dserver.config=standalone.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 10.142 s
> [INFO] Finished at: 2016-07-29T11:30:52+02:00
> [INFO] Final Memory: 65M/762M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test
> (default-integration
> -test) on project wildfly-camel-archetype-cdi:
> [ERROR] Archetype IT 'test-archetype-cdi' failed: Cannot run additions goals.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-archetype-
> plugin:2.2:integration-test (default-integration-test) on project
> wildfly-camel-archetype-cdi:
> Archetype IT 'test-archetype-cdi' failed: Cannot run additions goals.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecuto
[jira] [Updated] (MNG-6072) Cannot build archetypes on Windows
[
https://issues.apache.org/jira/browse/MNG-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated MNG-6072:
Environment: Windows (was: {code}
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
2015-03-13T21:10:27+01:00)
Maven home: C:\Program Files\Java\apache-maven-3.3.1
Java version: 1.8.0_101, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_101\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows server 2012 r2", version: "6.3", arch: "amd64", family: "dos"
{code})
> Cannot build archetypes on Windows
> --
>
> Key: MNG-6072
> URL: https://issues.apache.org/jira/browse/MNG-6072
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.1, 3.3.3, 3.3.9
> Environment: Windows
>Reporter: Thomas Diesler
>
> {code}
> [INFO] --- maven-archetype-plugin:2.2:integration-test
> (default-integration-test) @ wildfly-camel-archetype-cdi ---
> [INFO] Processing Archetype IT project: test-archetype-cdi
> [INFO]
>
> [INFO] Using following parameters for creating project from Archetype:
> wildfly-camel-archetype-cdi:4.2.0-SNAPSHOT
> [INFO]
>
> [INFO] Parameter: groupId, Value: org.wildfly.camel.archetype.test
> [INFO] Parameter: artifactId, Value: wildfly-camel-archetype-cdi-test
> [INFO] Parameter: version, Value: 1.0
> [INFO] Parameter: package, Value: org.wildfly.camel.archetype.test
> [INFO] Parameter: packageInPathFormat, Value: org/wildfly/camel/archetype/test
> [INFO] Parameter: version-wildfly-arquillian, Value: 1.0.2.Final
> [INFO] Parameter: version-jboss-arquillian, Value: 1.1.10.Final
> [INFO] Parameter: version-wildfly, Value: 10.0.0.Final
> [INFO] Parameter: groupId, Value: org.wildfly.camel.archetype.test
> [INFO] Parameter: version-junit, Value: 4.11
> [INFO] Parameter: version, Value: 1.0
> [INFO] Parameter: version-maven-war-plugin, Value: 2.5
> [INFO] Parameter: version-apache-camel, Value: 2.17.2
> [INFO] Parameter: package, Value: org.wildfly.camel.archetype.test
> [INFO] Parameter: version-wildfly-maven-plugin, Value: 1.1.0.Alpha7
> [INFO] Parameter: version-maven-compiler-plugin, Value: 3.1
> [INFO] Parameter: artifactId, Value: wildfly-camel-archetype-cdi-test
> [INFO] Parameter: version-wildfly-camel, Value: 4.2.0-SNAPSHOT
> [INFO] Parameter: version-maven-surefire-plugin, Value: 2.18.1
> [INFO] project created from Archetype in dir:
> C:\Users\Administrator\git\wildfly-camel\archetypes\archetype-cdi\target\t
> est-classes\projects\test-archetype-cdi\project\wildfly-camel-archetype-cdi-test
> [INFO] Invoking post-archetype-generation goals: verify -Parq-managed
> -Djboss.home=C:\\Users\\Administrator\\git\\wildfl
> y-camel\\archetypes\\archetype-cdi\\target\\wildfly-10.0.0.Final
> -Dserver.config=standalone.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 10.142 s
> [INFO] Finished at: 2016-07-29T11:30:52+02:00
> [INFO] Final Memory: 65M/762M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test
> (default-integration
> -test) on project wildfly-camel-archetype-cdi:
> [ERROR] Archetype IT 'test-archetype-cdi' failed: Cannot run additions goals.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-archetype-
> plugin:2.2:integration-test (default-integration-test) on project
> wildfly-camel-archetype-cdi:
> Archetype IT 'test-archetype-cdi' failed: Cannot run additions goals.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> 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:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.
> java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
[jira] [Created] (MNG-6072) Cannot build archetypes on Windows
Thomas Diesler created MNG-6072:
---
Summary: Cannot build archetypes on Windows
Key: MNG-6072
URL: https://issues.apache.org/jira/browse/MNG-6072
Project: Maven
Issue Type: Bug
Components: core
Affects Versions: 3.3.9, 3.3.3, 3.3.1
Environment: Apache Maven 3.3.1
(cab6659f9874fa96462afef40fcf6bc033d58c1c; 2015-03-13T21:10:27+01:00)
Maven home: C:\Program Files\Java\apache-maven-3.3.1
Java version: 1.8.0_101, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_101\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows server 2012 r2", version: "6.3", arch: "amd64", family: "dos"
Reporter: Thomas Diesler
{code}
[INFO] --- maven-archetype-plugin:2.2:integration-test
(default-integration-test) @ wildfly-camel-archetype-cdi ---
[INFO] Processing Archetype IT project: test-archetype-cdi
[INFO]
[INFO] Using following parameters for creating project from Archetype:
wildfly-camel-archetype-cdi:4.2.0-SNAPSHOT
[INFO]
[INFO] Parameter: groupId, Value: org.wildfly.camel.archetype.test
[INFO] Parameter: artifactId, Value: wildfly-camel-archetype-cdi-test
[INFO] Parameter: version, Value: 1.0
[INFO] Parameter: package, Value: org.wildfly.camel.archetype.test
[INFO] Parameter: packageInPathFormat, Value: org/wildfly/camel/archetype/test
[INFO] Parameter: version-wildfly-arquillian, Value: 1.0.2.Final
[INFO] Parameter: version-jboss-arquillian, Value: 1.1.10.Final
[INFO] Parameter: version-wildfly, Value: 10.0.0.Final
[INFO] Parameter: groupId, Value: org.wildfly.camel.archetype.test
[INFO] Parameter: version-junit, Value: 4.11
[INFO] Parameter: version, Value: 1.0
[INFO] Parameter: version-maven-war-plugin, Value: 2.5
[INFO] Parameter: version-apache-camel, Value: 2.17.2
[INFO] Parameter: package, Value: org.wildfly.camel.archetype.test
[INFO] Parameter: version-wildfly-maven-plugin, Value: 1.1.0.Alpha7
[INFO] Parameter: version-maven-compiler-plugin, Value: 3.1
[INFO] Parameter: artifactId, Value: wildfly-camel-archetype-cdi-test
[INFO] Parameter: version-wildfly-camel, Value: 4.2.0-SNAPSHOT
[INFO] Parameter: version-maven-surefire-plugin, Value: 2.18.1
[INFO] project created from Archetype in dir:
C:\Users\Administrator\git\wildfly-camel\archetypes\archetype-cdi\target\t
est-classes\projects\test-archetype-cdi\project\wildfly-camel-archetype-cdi-test
[INFO] Invoking post-archetype-generation goals: verify -Parq-managed
-Djboss.home=C:\\Users\\Administrator\\git\\wildfl
y-camel\\archetypes\\archetype-cdi\\target\\wildfly-10.0.0.Final
-Dserver.config=standalone.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 10.142 s
[INFO] Finished at: 2016-07-29T11:30:52+02:00
[INFO] Final Memory: 65M/762M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test
(default-integration
-test) on project wildfly-camel-archetype-cdi:
[ERROR] Archetype IT 'test-archetype-cdi' failed: Cannot run additions goals.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-archetype-
plugin:2.2:integration-test (default-integration-test) on project
wildfly-camel-archetype-cdi:
Archetype IT 'test-archetype-cdi' failed: Cannot run additions goals.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
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:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.
java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.
[jira] (MENFORCER-185) Require Release Dependencies ignorant about aggregator build
[ https://jira.codehaus.org/browse/MENFORCER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342051#comment-342051 ] Thomas Diesler commented on MENFORCER-185: -- Cross reference: https://issues.jboss.org/browse/FABRIC-884 > Require Release Dependencies ignorant about aggregator build > > > Key: MENFORCER-185 > URL: https://jira.codehaus.org/browse/MENFORCER-185 > Project: Maven Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Affects Versions: 1.3.1 >Reporter: Thomas Diesler > > If A depends on B it is ok for A-1.0.0-SNAPSHOT to have snapshot dependency > on B-1.0.0-SNAPSHOT if B was build before A during the same reactor build. > Using the requireReleaseDeps rule it seems that SNAPSHOTS are generally not > allowed even when they belong to the same project and were built during the > same reactor build. > We have a complex project with 100+ modules. I want to enforce that no module > has dependencies on project SNAPSHOTS that were not included in the build. In > such case A would use a stale version of B that happened to be available in > the local/remote maven repository. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MENFORCER-185) Require Release Dependencies ignorant about aggregator build
Thomas Diesler created MENFORCER-185: Summary: Require Release Dependencies ignorant about aggregator build Key: MENFORCER-185 URL: https://jira.codehaus.org/browse/MENFORCER-185 Project: Maven Enforcer Plugin Issue Type: Bug Components: Standard Rules Affects Versions: 1.3.1 Reporter: Thomas Diesler If A depends on B it is ok for A-1.0.0-SNAPSHOT to have snapshot dependency on B-1.0.0-SNAPSHOT if B was build before A during the same reactor build. Using the requireReleaseDeps rule it seems that SNAPSHOTS are generally not allowed even when they belong to the same project and were built during the same reactor build. We have a complex project with 100+ modules. I want to enforce that no module has dependencies on project SNAPSHOTS that were not included in the build. In such case A would use a stale version of B that happened to be available in the local/remote maven repository. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1014) Unparsable test report XML when sysout contains invalid XML
[
https://jira.codehaus.org/browse/SUREFIRE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328480#comment-328480
]
Thomas Diesler commented on SUREFIRE-1014:
--
sysout (and possibly other user provided content) should use a CDATA section.
> Unparsable test report XML when sysout contains invalid XML
> ---
>
> Key: SUREFIRE-1014
> URL: https://jira.codehaus.org/browse/SUREFIRE-1014
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.15
>Reporter: Thomas Diesler
>
> Jenkins cannot generate test reports from this
> {code}
>classname="org.jboss.test.osgi.example.jpa.PersistenceTestCase" time="0">
>
> &#;[0m04:25:37,808 INFO [org.jboss.osgi.framework] (MSC
> service thread 1-7) JBOSGI011003: Bundle stopped: startlevel-testcase:0.0.0
> &#;[0m&#;[0m04:25:37,811 INFO [org.jboss.osgi.framework] (MSC
> service thread 1-7) JBOSGI011005: Bundle uninstalled:
> startlevel-testcase:0.0.0
> &#;[0m&#;[0m04:25:37,813 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-7) JBAS015877: Stopped deployment startlevel-testcase
> (runtime-name: startlevel-testcase) in 5ms
> &#;[0m&#;[0m04:25:37,947 INFO [org.jboss.as.repository]
> (management-handler-thread - 3) JBAS014901: Content removed from location
> /mnt/hudson_workspace/workspace/jbosgi-remote-wildfly/jbosgi/testsuite/example/target/wildfly-8.0.0.Alpha3-SNAPSHOT/standalone/data/content/05/a1644a3f4393604a469058be52a8ff22a7ddf9/content
> &#;[0m&#;[0m04:25:37,947 INFO [org.jboss.as.server]
> (management-handler-thread - 3) JBAS018558: Undeployed "startlevel-testcase"
> (runtime-name: "startlevel-testcase")
> &#;[0m&#;[0m04:25:37,947 INFO [org.jboss.as.controller]
> (management-handler-thread - 3) JBAS014774: Service status report
> JBAS014776:Newly corrected services:
> service jboss.module.service."deployment.osgi-startlevel-a".main (no
> longer required)
> &#;[0m&#;[0m04:25:38,065 INFO [org.jboss.as.repository]
> (management-handler-thread - 4) JBAS014900: Content added at location
> /mnt/hudson_workspace/workspace/jbosgi-remote-wildfly/jbosgi/testsuite/example/target/wildfly-8.0.0.Alpha3-SNAPSHOT/standalone/data/content/98/b7aa8f04dae4a922300c8fe4b522d7ed231555/content
> &#;[0m&#;[0m04:25:38,066 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-3) JBAS015876: Starting deployment of "osgi-jpa-test"
> (runtime-name: "osgi-jpa-test")
> &#;[0m&#;[0m04:25:38,078 INFO [org.jboss.osgi.framework] (MSC
> service thread 1-1) JBOSGI011001: Bundle installed: osgi-jpa-test:0.0.0
> &#;[0m&#;[0m04:25:38,090 INFO [org.jboss.as.arquillian] (MSC service
> thread 1-3) Arquillian deployment detected:
> ArquillianConfig[service=jboss.arquillian.config.osgi-jpa-test,unit=osgi-jpa-test,tests=[org.jboss.test.osgi.example.jpa.PersistenceTestCase]]
> &#;[0m&#;[0m04:25:38,093 INFO [org.jboss.osgi.framework] (MSC
> service thread 1-3) JBOSGI011002: Bundle started: osgi-jpa-test:0.0.0
> &#;[0m&#;[0m04:25:38,226 INFO [org.jboss.as.server]
> (management-handler-thread - 4) JBAS018559: Deployed "osgi-jpa-test"
> (runtime-name : "osgi-jpa-test")
> &#;[0m
>
> {code}
> we get
> {code}
> Caused by: org.xml.sax.SAXParseException: The reference to entity "amp" must
> end with the ';' delimiter.
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
> at
> com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1427)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1849)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3033)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
>
[jira] (SUREFIRE-1014) Unparsable test report XML when sysout contains invalid XML
Thomas Diesler created SUREFIRE-1014:
Summary: Unparsable test report XML when sysout contains invalid
XML
Key: SUREFIRE-1014
URL: https://jira.codehaus.org/browse/SUREFIRE-1014
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.15
Reporter: Thomas Diesler
Jenkins cannot generate test reports from this
{code}
&#;[0m04:25:37,808 INFO [org.jboss.osgi.framework] (MSC
service thread 1-7) JBOSGI011003: Bundle stopped: startlevel-testcase:0.0.0
&#;[0m&#;[0m04:25:37,811 INFO [org.jboss.osgi.framework] (MSC service
thread 1-7) JBOSGI011005: Bundle uninstalled: startlevel-testcase:0.0.0
&#;[0m&#;[0m04:25:37,813 INFO [org.jboss.as.server.deployment] (MSC
service thread 1-7) JBAS015877: Stopped deployment startlevel-testcase
(runtime-name: startlevel-testcase) in 5ms
&#;[0m&#;[0m04:25:37,947 INFO [org.jboss.as.repository]
(management-handler-thread - 3) JBAS014901: Content removed from location
/mnt/hudson_workspace/workspace/jbosgi-remote-wildfly/jbosgi/testsuite/example/target/wildfly-8.0.0.Alpha3-SNAPSHOT/standalone/data/content/05/a1644a3f4393604a469058be52a8ff22a7ddf9/content
&#;[0m&#;[0m04:25:37,947 INFO [org.jboss.as.server]
(management-handler-thread - 3) JBAS018558: Undeployed "startlevel-testcase"
(runtime-name: "startlevel-testcase")
&#;[0m&#;[0m04:25:37,947 INFO [org.jboss.as.controller]
(management-handler-thread - 3) JBAS014774: Service status report
JBAS014776:Newly corrected services:
service jboss.module.service."deployment.osgi-startlevel-a".main (no
longer required)
&#;[0m&#;[0m04:25:38,065 INFO [org.jboss.as.repository]
(management-handler-thread - 4) JBAS014900: Content added at location
/mnt/hudson_workspace/workspace/jbosgi-remote-wildfly/jbosgi/testsuite/example/target/wildfly-8.0.0.Alpha3-SNAPSHOT/standalone/data/content/98/b7aa8f04dae4a922300c8fe4b522d7ed231555/content
&#;[0m&#;[0m04:25:38,066 INFO [org.jboss.as.server.deployment] (MSC
service thread 1-3) JBAS015876: Starting deployment of "osgi-jpa-test"
(runtime-name: "osgi-jpa-test")
&#;[0m&#;[0m04:25:38,078 INFO [org.jboss.osgi.framework] (MSC service
thread 1-1) JBOSGI011001: Bundle installed: osgi-jpa-test:0.0.0
&#;[0m&#;[0m04:25:38,090 INFO [org.jboss.as.arquillian] (MSC service
thread 1-3) Arquillian deployment detected:
ArquillianConfig[service=jboss.arquillian.config.osgi-jpa-test,unit=osgi-jpa-test,tests=[org.jboss.test.osgi.example.jpa.PersistenceTestCase]]
&#;[0m&#;[0m04:25:38,093 INFO [org.jboss.osgi.framework] (MSC service
thread 1-3) JBOSGI011002: Bundle started: osgi-jpa-test:0.0.0
&#;[0m&#;[0m04:25:38,226 INFO [org.jboss.as.server]
(management-handler-thread - 4) JBAS018559: Deployed "osgi-jpa-test"
(runtime-name : "osgi-jpa-test")
&#;[0m
{code}
we get
{code}
Caused by: org.xml.sax.SAXParseException: The reference to entity "amp" must
end with the ';' delimiter.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1427)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1849)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3033)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at org.dom4j.io.SAXReader.read(SAXReader.java:465)
... 18 more
Build step 'Publish JUnit test result report' changed build result to FAILURE
Notifying upstream projects of job completion
Finished: FAILURE
{code}
--
This message is automatically generated by JIRA.
If you think
[jira] (MRELEASE-730) release:prepare cannot find dependent artefact
[
https://jira.codehaus.org/browse/MRELEASE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289253#comment-289253
]
Thomas Diesler edited comment on MRELEASE-730 at 1/24/12 4:57 AM:
--
The parent pom defines
{code}
jboss-releases-repository
JBoss Releases Repository
${jboss.releases.repo.url}
jboss-snapshots-repository
JBoss Snapshots Repository
${jboss.snapshots.repo.url}
{code}
You can test with
https://github.com/jbosgi/jbosgi-resolver/commit/713618aeaabdb71dd3f98191a0c642f108a786ae
was (Author: tdiesler):
The parent pom defines
{code}
jboss-releases-repository
JBoss Releases Repository
${jboss.releases.repo.url}
jboss-snapshots-repository
JBoss Snapshots Repository
${jboss.snapshots.repo.url}
{code}
> release:prepare cannot find dependent artefact
> --
>
> Key: MRELEASE-730
> URL: https://jira.codehaus.org/browse/MRELEASE-730
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.2.2
>Reporter: Thomas Diesler
>
> It seems that release:prepare assumes dependencies to come from central
> {code}
> [tdiesler@tdvaio jbosgi-resolver]$ mvn release:prepare
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] JBossOSGi Resolver
> [INFO] JBossOSGi Resolver API
> [INFO] JBossOSGi Resolver Felix
> [INFO]
>
> [INFO]
>
> [INFO] Building JBossOSGi Resolver 2.0.0.Alpha5-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @
> jbosgi-resolver-parent ---
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: pom.xml.next, release.properties,
> pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag
> [INFO] Executing: /bin/sh -c cd /home/tdiesler/git/jbosgi-resolver && git
> status
> [INFO] Working directory: /home/tdiesler/git/jbosgi-resolver
> [INFO] Checking dependencies and plugins for snapshots ...
> What is the release version for "JBossOSGi Resolver"?
> (org.jboss.osgi.resolver:jbosgi-resolver-parent) 2.0.0.Alpha5: :
> What is the release version for "JBossOSGi Resolver API"?
> (org.jboss.osgi.resolver:jbosgi-resolver-apiv2) 2.0.0.Alpha5: :
> What is the release version for "JBossOSGi Resolver Felix"?
> (org.jboss.osgi.resolver:jbosgi-resolver-felix) 2.0.0.Alpha5: :
> What is SCM release tag or label for "JBossOSGi Resolver"?
> (org.jboss.osgi.resolver:jbosgi-resolver-parent)
> jbosgi-resolver-parent-2.0.0.Alpha5: :
> What is the new development version for "JBossOSGi Resolver"?
> (org.jboss.osgi.resolver:jbosgi-resolver-parent) 2.0.1.Alpha5-SNAPSHOT: :
> What is the new development version for "JBossOSGi Resolver API"?
> (org.jboss.osgi.resolver:jbosgi-resolver-apiv2) 2.0.1.Alpha5-SNAPSHOT: :
> What is the new development version for "JBossOSGi Resolver Felix"?
> (org.jboss.osgi.resolver:jbosgi-resolver-felix) 2.0.1.Alpha5-SNAPSHOT: :
> [INFO] Transforming 'JBossOSGi Resolver'...
> [INFO] Transforming 'JBossOSGi Resolver API'...
> [INFO] Transforming 'JBossOSGi Resolver Felix'...
> [INFO] Ignoring artifact version update for expression ${project.version}
> [INFO] Not generating release POMs
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has
> been configured for this MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO]
>
> [INFO] [INFO] Reactor Build Order:
> [INFO] [INFO]
> [INFO] [INFO] JBossOSGi Resolver
> [INFO] [INFO] JBossOSGi Resolver API
> [INFO] [INFO] JBossOSGi Resolver Felix
> [INFO] [INFO]
>
> [INFO] [INFO]
>
> [INFO] [INFO] Building JBossOSGi Resolver 2.0.0.Alpha5
> [INFO] [INFO]
>
> [INFO] [INFO]
> [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> jbosgi-resolver-parent ---
> [INFO] [INFO] Deleting /home/tdiesler/git/jbosgi-resolver/target
> [INFO] [INFO]
> [INFO] [INFO] >>> maven-sourc
[jira] (MRELEASE-730) release:prepare cannot find dependent artefact
[
https://jira.codehaus.org/browse/MRELEASE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289253#comment-289253
]
Thomas Diesler commented on MRELEASE-730:
-
The parent pom defines
{code}
jboss-releases-repository
JBoss Releases Repository
${jboss.releases.repo.url}
jboss-snapshots-repository
JBoss Snapshots Repository
${jboss.snapshots.repo.url}
{code}
> release:prepare cannot find dependent artefact
> --
>
> Key: MRELEASE-730
> URL: https://jira.codehaus.org/browse/MRELEASE-730
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.2.2
>Reporter: Thomas Diesler
>
> It seems that release:prepare assumes dependencies to come from central
> {code}
> [tdiesler@tdvaio jbosgi-resolver]$ mvn release:prepare
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] JBossOSGi Resolver
> [INFO] JBossOSGi Resolver API
> [INFO] JBossOSGi Resolver Felix
> [INFO]
>
> [INFO]
>
> [INFO] Building JBossOSGi Resolver 2.0.0.Alpha5-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @
> jbosgi-resolver-parent ---
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: pom.xml.next, release.properties,
> pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag
> [INFO] Executing: /bin/sh -c cd /home/tdiesler/git/jbosgi-resolver && git
> status
> [INFO] Working directory: /home/tdiesler/git/jbosgi-resolver
> [INFO] Checking dependencies and plugins for snapshots ...
> What is the release version for "JBossOSGi Resolver"?
> (org.jboss.osgi.resolver:jbosgi-resolver-parent) 2.0.0.Alpha5: :
> What is the release version for "JBossOSGi Resolver API"?
> (org.jboss.osgi.resolver:jbosgi-resolver-apiv2) 2.0.0.Alpha5: :
> What is the release version for "JBossOSGi Resolver Felix"?
> (org.jboss.osgi.resolver:jbosgi-resolver-felix) 2.0.0.Alpha5: :
> What is SCM release tag or label for "JBossOSGi Resolver"?
> (org.jboss.osgi.resolver:jbosgi-resolver-parent)
> jbosgi-resolver-parent-2.0.0.Alpha5: :
> What is the new development version for "JBossOSGi Resolver"?
> (org.jboss.osgi.resolver:jbosgi-resolver-parent) 2.0.1.Alpha5-SNAPSHOT: :
> What is the new development version for "JBossOSGi Resolver API"?
> (org.jboss.osgi.resolver:jbosgi-resolver-apiv2) 2.0.1.Alpha5-SNAPSHOT: :
> What is the new development version for "JBossOSGi Resolver Felix"?
> (org.jboss.osgi.resolver:jbosgi-resolver-felix) 2.0.1.Alpha5-SNAPSHOT: :
> [INFO] Transforming 'JBossOSGi Resolver'...
> [INFO] Transforming 'JBossOSGi Resolver API'...
> [INFO] Transforming 'JBossOSGi Resolver Felix'...
> [INFO] Ignoring artifact version update for expression ${project.version}
> [INFO] Not generating release POMs
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has
> been configured for this MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO]
>
> [INFO] [INFO] Reactor Build Order:
> [INFO] [INFO]
> [INFO] [INFO] JBossOSGi Resolver
> [INFO] [INFO] JBossOSGi Resolver API
> [INFO] [INFO] JBossOSGi Resolver Felix
> [INFO] [INFO]
>
> [INFO] [INFO]
>
> [INFO] [INFO] Building JBossOSGi Resolver 2.0.0.Alpha5
> [INFO] [INFO]
>
> [INFO] [INFO]
> [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> jbosgi-resolver-parent ---
> [INFO] [INFO] Deleting /home/tdiesler/git/jbosgi-resolver/target
> [INFO] [INFO]
> [INFO] [INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @
> jbosgi-resolver-parent >>>
> [INFO] [INFO]
> [INFO] [INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @
> jbosgi-resolver-parent <<<
> [INFO] [INFO]
> [INFO] [INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @
> jbosgi-resolver-parent ---
> [INFO] [INFO]
>
> [INFO] [INFO]
>
> [INFO] [INFO] Building JBossOSGi Resolver API 2.
[jira] (MRELEASE-730) release:prepare cannot find dependent artefact
Thomas Diesler created MRELEASE-730:
---
Summary: release:prepare cannot find dependent artefact
Key: MRELEASE-730
URL: https://jira.codehaus.org/browse/MRELEASE-730
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.2.2
Reporter: Thomas Diesler
It seems that release:prepare assumes dependencies to come from central
{code}
[tdiesler@tdvaio jbosgi-resolver]$ mvn release:prepare
[INFO] Scanning for projects...
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] JBossOSGi Resolver
[INFO] JBossOSGi Resolver API
[INFO] JBossOSGi Resolver Felix
[INFO]
[INFO]
[INFO] Building JBossOSGi Resolver 2.0.0.Alpha5-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @
jbosgi-resolver-parent ---
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: pom.xml.next, release.properties,
pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag
[INFO] Executing: /bin/sh -c cd /home/tdiesler/git/jbosgi-resolver && git status
[INFO] Working directory: /home/tdiesler/git/jbosgi-resolver
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for "JBossOSGi Resolver"?
(org.jboss.osgi.resolver:jbosgi-resolver-parent) 2.0.0.Alpha5: :
What is the release version for "JBossOSGi Resolver API"?
(org.jboss.osgi.resolver:jbosgi-resolver-apiv2) 2.0.0.Alpha5: :
What is the release version for "JBossOSGi Resolver Felix"?
(org.jboss.osgi.resolver:jbosgi-resolver-felix) 2.0.0.Alpha5: :
What is SCM release tag or label for "JBossOSGi Resolver"?
(org.jboss.osgi.resolver:jbosgi-resolver-parent)
jbosgi-resolver-parent-2.0.0.Alpha5: :
What is the new development version for "JBossOSGi Resolver"?
(org.jboss.osgi.resolver:jbosgi-resolver-parent) 2.0.1.Alpha5-SNAPSHOT: :
What is the new development version for "JBossOSGi Resolver API"?
(org.jboss.osgi.resolver:jbosgi-resolver-apiv2) 2.0.1.Alpha5-SNAPSHOT: :
What is the new development version for "JBossOSGi Resolver Felix"?
(org.jboss.osgi.resolver:jbosgi-resolver-felix) 2.0.1.Alpha5-SNAPSHOT: :
[INFO] Transforming 'JBossOSGi Resolver'...
[INFO] Transforming 'JBossOSGi Resolver API'...
[INFO] Transforming 'JBossOSGi Resolver Felix'...
[INFO] Ignoring artifact version update for expression ${project.version}
[INFO] Not generating release POMs
[INFO] Executing goals 'clean verify'...
[WARNING] Maven will be executed in interactive mode, but no input stream has
been configured for this MavenInvoker instance.
[INFO] [INFO] Scanning for projects...
[INFO] [INFO]
[INFO] [INFO] Reactor Build Order:
[INFO] [INFO]
[INFO] [INFO] JBossOSGi Resolver
[INFO] [INFO] JBossOSGi Resolver API
[INFO] [INFO] JBossOSGi Resolver Felix
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] Building JBossOSGi Resolver 2.0.0.Alpha5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
jbosgi-resolver-parent ---
[INFO] [INFO] Deleting /home/tdiesler/git/jbosgi-resolver/target
[INFO] [INFO]
[INFO] [INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @
jbosgi-resolver-parent >>>
[INFO] [INFO]
[INFO] [INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @
jbosgi-resolver-parent <<<
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @
jbosgi-resolver-parent ---
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] Building JBossOSGi Resolver API 2.0.0.Alpha5
[INFO] [INFO]
[INFO] Downloading:
http://repo1.maven.org/maven2/org/jboss/osgi/vfs/jbosgi-vfs30/1.0.6/jbosgi-vfs30-1.0.6.pom
[INFO]
[INFO] [WARNING] The POM for org.jboss.osgi.vfs:jbosgi-vfs30:jar:1.0.6 is
missing, no dependency information available
[INFO] Downloading:
http://repo1.maven.org/maven2/org/jboss/osgi/vfs/jbosgi-vfs30/1.0.6/jbosgi-vfs30-1.0.6.jar
[INFO]
[INFO] [INFO]
[INFO] [INFO] Reactor Summary:
[INFO] [INFO]
[INFO] [INFO] JBossOSGi Resolver SUCCESS
[1.276s]
[INFO] [INFO] JBossOSGi Resolver API ..
[jira] Commented: (MAVENUPLOAD-2789) OSGi 4.2.0 Enterprise API
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229970#action_229970 ] Thomas Diesler commented on MAVENUPLOAD-2789: - Here is the link to the osgi download page http://www.osgi.org/Download/File?url=/download/r4v42/osgi.enterprise.jar > OSGi 4.2.0 Enterprise API > - > > Key: MAVENUPLOAD-2789 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2789 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Thomas Diesler > Attachments: org.osgi.enterprise-4.2.0.jar > > > This is the recently released OSGi 4.2.0 Enterprise API in bundle form. I > have manually created sha1 checksums for all artifacts; the pom is > maven-generated. -- 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] Issue Comment Edited: (MAVENUPLOAD-2789) OSGi 4.2.0 Enterprise API
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226544#action_226544 ] Thomas Diesler edited comment on MAVENUPLOAD-2789 at 6/28/10 6:55 AM: -- The duplicate issue was closed 27-Apr-2010 without action since Related EEG Thread: https://mail.osgi.org/pipermail/eeg/2010-June/006701.html was (Author: tdiesler): The duplicate issue was closed 27-Apr-2010 without action since > OSGi 4.2.0 Enterprise API > - > > Key: MAVENUPLOAD-2789 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2789 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Thomas Diesler > Attachments: org.osgi.enterprise-4.2.0.jar > > > This is the recently released OSGi 4.2.0 Enterprise API in bundle form. I > have manually created sha1 checksums for all artifacts; the pom is > maven-generated. -- 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] Issue Comment Edited: (MAVENUPLOAD-2789) OSGi 4.2.0 Enterprise API
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226544#action_226544 ] Thomas Diesler edited comment on MAVENUPLOAD-2789 at 6/28/10 6:08 AM: -- The duplicate issue was closed 27-Apr-2010 without action since was (Author: tdiesler): The duplicate issue was closed without action since > OSGi 4.2.0 Enterprise API > - > > Key: MAVENUPLOAD-2789 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2789 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Thomas Diesler > Attachments: org.osgi.enterprise-4.2.0.jar > > > This is the recently released OSGi 4.2.0 Enterprise API in bundle form. I > have manually created sha1 checksums for all artifacts; the pom is > maven-generated. -- 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: (MAVENUPLOAD-2789) OSGi 4.2.0 Enterprise API
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226544#action_226544 ] Thomas Diesler commented on MAVENUPLOAD-2789: - The duplicate issue was closed without action since > OSGi 4.2.0 Enterprise API > - > > Key: MAVENUPLOAD-2789 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2789 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Thomas Diesler > Attachments: org.osgi.enterprise-4.2.0.jar > > > This is the recently released OSGi 4.2.0 Enterprise API in bundle form. I > have manually created sha1 checksums for all artifacts; the pom is > maven-generated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2789) OSGi 4.2.0 Enterprise API
OSGi 4.2.0 Enterprise API - Key: MAVENUPLOAD-2789 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2789 Project: Maven Upload Requests Issue Type: Wish Reporter: Thomas Diesler Attachments: org.osgi.enterprise-4.2.0.jar This is the recently released OSGi 4.2.0 Enterprise API in bundle form. I have manually created sha1 checksums for all artifacts; the pom is maven-generated. -- 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: (SUREFIRE-601) Wildcards on -Dtest property
Wildcards on -Dtest property - Key: SUREFIRE-601 URL: http://jira.codehaus.org/browse/SUREFIRE-601 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.4.3 Reporter: Thomas Diesler I'd like to run all enterprise tests like this mvn -Dtest=enterprise/** test This should run all tests in subpackages of 'enterprise' org.jboss.test.osgi.example.enterprise.jmx.JMXEnterpriseTestCase Currently, I need to use a pattern like this mvn -Dtest=enterprise/*/* test -- 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: (SUREFIRE-548) System properties not inherited
System properties not inherited --- Key: SUREFIRE-548 URL: http://jira.codehaus.org/browse/SUREFIRE-548 Project: Maven Surefire Issue Type: Bug Components: plugin Affects Versions: 2.4.2 Reporter: Thomas Diesler Surefire system properties from the parent pom are not inherited. Instead the complete set of properties is replaced. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNGSITE-72) Maven 2 property reference guide
[ http://jira.codehaus.org/browse/MNGSITE-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173064#action_173064 ] Thomas Diesler commented on MNGSITE-72: --- http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide > Maven 2 property reference guide > > > Key: MNGSITE-72 > URL: http://jira.codehaus.org/browse/MNGSITE-72 > Project: Maven 2 Project Web Site > Issue Type: Bug > Environment: All >Reporter: Robert Bracewell > > The main Maven website needs to include documentation or a reference guide > that explains all Maven 2.x properties. > I havent been able to find any such link on the 2.x website if such does exist -- 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] Issue Comment Edited: (MNG-3546) command line cannot overwrite pom properties
[
http://jira.codehaus.org/browse/MNG-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146949#action_146949
]
tdiesler edited comment on MNG-3546 at 9/4/08 1:29 AM:
-
Also, a property defined in profiles.xml is not seen in module profile
activation
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/profiles-1.0.0.xsd";>
jboss-home-profile
user.name
/home/tdiesler/svn/jbossas/tags/JBoss_4_2_2_GA/build/output/jboss-4.2.2.GA
foo
{code}
{code}
no-jboss-bind-address
!jboss.bind.address
localhost
{code}
The effective pom should show foo for all modules, but does not
{code}
[EMAIL PROTECTED] trunk]$ mvn help:effective-pom | grep jboss.bind.address
foo
foo
foo
foo
foo
foo
foo
foo
foo
foo
no-jboss-bind-address
!jboss.bind.address
localhost
localhost
{code}
was (Author: tdiesler):
Also, a property defined in profiles.xml does not override a property
defined in a module profile
> command line cannot overwrite pom properties
>
>
> Key: MNG-3546
> URL: http://jira.codehaus.org/browse/MNG-3546
> Project: Maven 2
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 2.0.9
>Reporter: Thomas Diesler
> Fix For: 2.0.x
>
>
> With a pom like this
>
> localhost
>
> and a command line like this
> mvn -Pjboss422 -Djboss.bind.address=foo clean test-compilecxf.xml
> I get a filtered resource like this
>address='http://localhost:8080/jaxws-cxf-descriptor'
>
> implementor='org.jboss.test.ws.jaxws.cxf.descriptor.DescriptorEndpointImpl'>
>
>
>
>
>
>
> Note, the bind address is localhost
--
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-3546) command line cannot overwrite pom properties
[ http://jira.codehaus.org/browse/MNG-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146949#action_146949 ] Thomas Diesler commented on MNG-3546: - Also, a property defined in profiles.xml does not override a property defined in a module profile > command line cannot overwrite pom properties > > > Key: MNG-3546 > URL: http://jira.codehaus.org/browse/MNG-3546 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.9 >Reporter: Thomas Diesler > Fix For: 2.0.x > > > With a pom like this > > localhost > > and a command line like this > mvn -Pjboss422 -Djboss.bind.address=foo clean test-compilecxf.xml > I get a filtered resource like this >address='http://localhost:8080/jaxws-cxf-descriptor' > > implementor='org.jboss.test.ws.jaxws.cxf.descriptor.DescriptorEndpointImpl'> > > > > > > > Note, the bind address is localhost -- 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-515) Executes nested classes that are not tests
[ http://jira.codehaus.org/browse/SUREFIRE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145239#action_145239 ] Thomas Diesler commented on SUREFIRE-515: - BTW, why is it necessary to add the .java extension ? > Executes nested classes that are not tests > -- > > Key: SUREFIRE-515 > URL: http://jira.codehaus.org/browse/SUREFIRE-515 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.4.3 >Reporter: Thomas Diesler > > When using excludes like this > > maven-surefire-plugin > > > org/jboss/bpm/pattern/**/*APITest.java > > > org/jboss/bpm/pattern/** > > > > surefire executes the nested classes > Running > org.jboss.bpm.pattern.control.synchronization.SynchronizationTest$TaskB > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec > Running > org.jboss.bpm.pattern.control.synchronization.SynchronizationTest$TaskC > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec -- 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-515) Executes nested classes that are not tests
[ http://jira.codehaus.org/browse/SUREFIRE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145238#action_145238 ] Thomas Diesler commented on SUREFIRE-515: - Workarround org/jboss/bpm/pattern/**/*Task?.java > Executes nested classes that are not tests > -- > > Key: SUREFIRE-515 > URL: http://jira.codehaus.org/browse/SUREFIRE-515 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.4.3 >Reporter: Thomas Diesler > > When using excludes like this > > maven-surefire-plugin > > > org/jboss/bpm/pattern/**/*APITest.java > > > org/jboss/bpm/pattern/** > > > > surefire executes the nested classes > Running > org.jboss.bpm.pattern.control.synchronization.SynchronizationTest$TaskB > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec > Running > org.jboss.bpm.pattern.control.synchronization.SynchronizationTest$TaskC > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec -- 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-515) Executes nested classes that are not tests
[
http://jira.codehaus.org/browse/SUREFIRE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145237#action_145237
]
Thomas Diesler commented on SUREFIRE-515:
-
/*
* JBoss, Home of Professional Open Source
* Copyright 2005, JBoss Inc., and individual contributors as indicated
* by the @authors tag. See the copyright.txt in the distribution for a
* full listing of individual contributors.
*
* This is free software; you can redistribute it and/or modify it
* under the terms of the GNU Lesser General Public License as
* published by the Free Software Foundation; either version 2.1 of
* the License, or (at your option) any later version.
*
* This software is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this software; if not, write to the Free
* Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
* 02110-1301 USA, or see the FSF site: http://www.fsf.org.
*/
package org.jboss.bpm.pattern.control.synchronization;
// $Id: SynchronizationTest.java 1897 2008-08-15 08:46:48Z [EMAIL PROTECTED] $
import java.io.IOException;
import org.jboss.bpm.client.SignalListener;
import org.jboss.bpm.client.SignalManager;
import org.jboss.bpm.model.EventBuilder;
import org.jboss.bpm.model.Process;
import org.jboss.bpm.model.ProcessBuilder;
import org.jboss.bpm.model.ProcessBuilderFactory;
import org.jboss.bpm.model.Signal;
import org.jboss.bpm.model.Gateway.GatewayType;
import org.jboss.bpm.model.Signal.SignalType;
import org.jboss.bpm.runtime.ExecutionContext;
import org.jboss.bpm.runtime.ExecutionHandler;
import org.jboss.bpm.runtime.Token;
import org.jboss.bpm.test.DefaultEngineTestCase;
/**
* Parallel gateway that that has multiple incoming sequence flows. Each token
arriving from an incoming sequence flow
* is stored in the gateway until a token has arrived from each incoming
sequence flow. The tokens are merged together
* and leave the gateway as a one.
*
* @author [EMAIL PROTECTED]
* @since 06-Aug-2008
*/
public class SynchronizationTest extends DefaultEngineTestCase
{
public void testSynchronization() throws Exception
{
Process proc = getProcess();
proc.startProcess();
// Add a signal listener that sends the other start trigger signal
SignalManager signalManager = SignalManager.locateSignalManager();
Signal startTrigger = new Signal(getName(),
SignalType.SYSTEM_START_TRIGGER, "B");
signalManager.addSignalListener(null, new MergeListener(proc.getName(),
startTrigger));
// Send start trigger signal
signalManager.throwSignal(proc.getName(), new Signal(getName(),
SignalType.SYSTEM_START_TRIGGER, "A"));
// Wait for the process to end
proc.waitForEnd();
// Verify the result
assertEquals("TaskA:TaskB", TaskC.taskValue);
}
public void testSynchronizationTimeout() throws Exception
{
Process proc = getProcess();
proc.startProcess();
// Send start trigger signal
SignalManager signalManager = SignalManager.locateSignalManager();
signalManager.throwSignal(proc.getName(), new Signal(getName(),
SignalType.SYSTEM_START_TRIGGER, "A"));
// Wait for the process to end
try
{
proc.waitForEnd(1000);
fail("timeout expected");
}
catch (RuntimeException rte)
{
// expected
}
}
public void testSynchronizationInvalidToken() throws Exception
{
Process proc = getProcess();
proc.startProcess();
// Add a signal listener that sends the other start trigger signal
SignalManager signalManager = SignalManager.locateSignalManager();
Signal startTrigger = new Signal(getName(),
SignalType.SYSTEM_START_TRIGGER, "A");
signalManager.addSignalListener(null, new MergeListener(proc.getName(),
startTrigger));
// Send start trigger signal
signalManager.throwSignal(proc.getName(), new Signal(getName(),
SignalType.SYSTEM_START_TRIGGER, "A"));
try
{
proc.waitForEnd();
fail("Expected: Unexpected token from: SequenceFlow[TaskA->Merge]");
}
catch (RuntimeException rte)
{
// expected
}
// Restart the process
proc.startProcess();
// Add a signal listener that sends the other start trigger signal
startTrigger = new Signal(getName(), SignalType.SYSTEM_START_TRIGGER, "B");
signalManager.addSignalListener(null, new MergeListener(proc.getName(),
startTrigger));
// Send start trigger signal
signalManager.throwSignal(proc.getName(), new Signal(getName(),
SignalType.SYSTEM_START_TRIGGER, "A"));
// Wait for the process to end
proc.waitForEnd();
// Verify the result
assertEquals("TaskA:TaskB", TaskC.taskValue);
[jira] Created: (SUREFIRE-515) Executes nested classes that are not tests
Executes nested classes that are not tests -- Key: SUREFIRE-515 URL: http://jira.codehaus.org/browse/SUREFIRE-515 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.4.3 Reporter: Thomas Diesler When using excludes like this maven-surefire-plugin org/jboss/bpm/pattern/**/*APITest.java org/jboss/bpm/pattern/** surefire executes the nested classes Running org.jboss.bpm.pattern.control.synchronization.SynchronizationTest$TaskB Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.jboss.bpm.pattern.control.synchronization.SynchronizationTest$TaskC Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3711) NPE in ChecksumObserver
NPE in ChecksumObserver --- Key: MNG-3711 URL: http://jira.codehaus.org/browse/MNG-3711 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Reporter: Thomas Diesler After Ctrl+C during 'mvn deploy' I seem to have a corrupt snapshot repository. Subsequent deploy attempts fail with Uploading: https://snapshots.jboss.org/maven2/org/jboss/bpm/bpm-dialect-xpdl21/1.0.0-SNAPSHOT/bpm-dialect-xpdl21-1.0.0-20080814.162232-1.jar [INFO] Uploading project information for bpm-dialect-xpdl21 1.0.0-20080814.162232-1 [INFO] Retrieving previous metadata from snapshots.jboss.org [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.wagon.observers.ChecksumObserver.transferStarted(ChecksumObserver.java:65) at org.apache.maven.wagon.events.TransferEventSupport.fireTransferStarted(TransferEventSupport.java:100) at org.apache.maven.wagon.AbstractWagon.fireGetStarted(AbstractWagon.java:378) at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:193) at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:182) at org.apache.maven.wagon.providers.webdav.WebDavWagon.get(WebDavWagon.java:426) at org.apache.maven.wagon.providers.webdav.WebDavWagon.get(WebDavWagon.java:377) -- 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: (MANTRUN-91) Cannot run javac from tasks
[ http://jira.codehaus.org/browse/MANTRUN-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134128#action_134128 ] Thomas Diesler commented on MANTRUN-91: --- As a workaround you can use an external compiler > Cannot run javac from tasks > --- > > Key: MANTRUN-91 > URL: http://jira.codehaus.org/browse/MANTRUN-91 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Reporter: Thomas Diesler > > Embedded error: The following error occurred while executing this line: > /home/tdiesler/svn/jbossws/stack/native/trunk/modules/testsuite/native-tests/scripts/antrun-wstools.xml:65: > Unable to find a javac compiler; > com.sun.tools.javac.Main is not on the classpath. > Perhaps JAVA_HOME does not point to the JDK -- 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: (MANTRUN-91) Cannot run javac from tasks
Cannot run javac from tasks --- Key: MANTRUN-91 URL: http://jira.codehaus.org/browse/MANTRUN-91 Project: Maven 2.x Antrun Plugin Issue Type: Bug Reporter: Thomas Diesler Embedded error: The following error occurred while executing this line: /home/tdiesler/svn/jbossws/stack/native/trunk/modules/testsuite/native-tests/scripts/antrun-wstools.xml:65: Unable to find a javac compiler; com.sun.tools.javac.Main is not on the classpath. Perhaps JAVA_HOME does not point to the JDK -- 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: (MCOMPILER-72) Add support for specifying includes/excludes in an external file
[ http://jira.codehaus.org/browse/MCOMPILER-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133645#action_133645 ] Thomas Diesler commented on MCOMPILER-72: - Folks have been reporting [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:compile': Una ble to find the mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:compile' in the plugin 'org.apache.maven.plugins:ma ven-compiler-plugin' org/codehaus/plexus/compiler/util/scan/InclusionScanException [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plug ins:maven-compiler-plugin:2.0.2.SP1:compile': Unable to find the mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:co mpile' in the plugin 'org.apache.maven.plugins:maven-compiler-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:maven-compiler-plugin :2.0.2.SP1:compile' in the plugin 'org.apache.maven.plugins:maven-compiler-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:575) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:425) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.mav en.plugin.Mojoorg.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:compile', it could not be created at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:566) ... 18 more Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanciate component: role: 'null', i mplementation: 'org.apache.maven.plugin.CompilerMojo' at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93 ) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331) ... 20 more Caused by: java.lang.NoClassDefFoundError: org/codehaus/plexus/compiler/util/scan/InclusionScanException at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357) at java.lang.Class.getConstructor0(Class.java:2671) at java.lang.Class.newInstance0(Class.java:321) at java.lang.Class.newI
[jira] Commented: (MCOMPILER-72) Add support for specifying includes/excludes in an external file
[
http://jira.codehaus.org/browse/MCOMPILER-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133198#action_133198
]
Thomas Diesler commented on MCOMPILER-72:
-
The binary is here
http://repository.jboss.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.2.SP1/
> Add support for specifying includes/excludes in an external file
>
>
> Key: MCOMPILER-72
> URL: http://jira.codehaus.org/browse/MCOMPILER-72
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
>Affects Versions: 2.0.2
>Reporter: Thomas Diesler
> Attachments: svndiff.txt
>
>
> Similar to Ant, the compiler plugin should support excludes defined in an
> external file like this
> {code:xml}
>
> maven-compiler-plugin
> 2.0.2.SP1
>
> ../test-excludes-jboss422.txt
>
>
> {code}
> The exclude file would look like this
> {code}
> # [JBWS-2135] WebServiceException: Undefined port type
> org/jboss/test/ws/jaxws/jbws1822/**
> # [JBWS-2136] ClassCastException:
> com.sun.xml.ws.server.EndpointMessageContextImpl
> org/jboss/test/ws/jaxws/namespace/**
> # [JBAS-5359] mapped-name is required for context of deployment
> org/jboss/test/ws/jaxws/jbws1611/**
> {code}
--
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-486) Exlude tests via an external exlude file
[ http://jira.codehaus.org/browse/SUREFIRE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133197#action_133197 ] Thomas Diesler commented on SUREFIRE-486: - Well, we need this feature nevertheless. Folks that also do, please have a look at MCOMPILER-72 > Exlude tests via an external exlude file > > > Key: SUREFIRE-486 > URL: http://jira.codehaus.org/browse/SUREFIRE-486 > Project: Maven Surefire > Issue Type: New Feature >Reporter: Thomas Diesler > > Similar to Ant, Surefire should support excludes defined in an external file > like this > >test-excludes-jboss501.txt > > The exclude file would look like this > # [JBWS-2135] WebServiceException: Undefined port type > org/jboss/test/ws/jaxws/jbws1822/** > # [JBWS-2136] ClassCastException: > com.sun.xml.ws.server.EndpointMessageContextImpl > org/jboss/test/ws/jaxws/namespace/** > # [JBAS-5359] mapped-name is required for context of deployment > org/jboss/test/ws/jaxws/jbws1611/** -- 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] Updated: (MCOMPILER-72) Add support for specifying includes/excludes in an external file
[
http://jira.codehaus.org/browse/MCOMPILER-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated MCOMPILER-72:
Attachment: svndiff.txt
The diff is attached
> Add support for specifying includes/excludes in an external file
>
>
> Key: MCOMPILER-72
> URL: http://jira.codehaus.org/browse/MCOMPILER-72
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
>Affects Versions: 2.0.2
>Reporter: Thomas Diesler
> Attachments: svndiff.txt
>
>
> Similar to Ant, the compiler plugin should support excludes defined in an
> external file like this
> {code:xml}
>
> maven-compiler-plugin
> 2.0.2.SP1
>
> ../test-excludes-jboss422.txt
>
>
> {code}
> The exclude file would look like this
> {code}
> # [JBWS-2135] WebServiceException: Undefined port type
> org/jboss/test/ws/jaxws/jbws1822/**
> # [JBWS-2136] ClassCastException:
> com.sun.xml.ws.server.EndpointMessageContextImpl
> org/jboss/test/ws/jaxws/namespace/**
> # [JBAS-5359] mapped-name is required for context of deployment
> org/jboss/test/ws/jaxws/jbws1611/**
> {code}
--
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: (MCOMPILER-72) Add support for include/exclude files
[
http://jira.codehaus.org/browse/MCOMPILER-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133194#action_133194
]
Thomas Diesler commented on MCOMPILER-72:
-
For an implementation please see
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/maven/plugins/maven-compiler-plugin/tags/maven-compiler-plugin-2.0.2.SP1/src/main/java/org/apache/maven/plugin/TestCompilerMojo.java?revision=72917&view=markup
> Add support for include/exclude files
> -
>
> Key: MCOMPILER-72
> URL: http://jira.codehaus.org/browse/MCOMPILER-72
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
>Affects Versions: 2.0.2
>Reporter: Thomas Diesler
>
> Similar to Ant, the compiler plugin should support excludes defined in an
> external file like this
> {code:xml}
>
> maven-compiler-plugin
> 2.0.2.SP1
>
> ../test-excludes-jboss422.txt
>
>
> {code}
> The exclude file would look like this
> {code}
> # [JBWS-2135] WebServiceException: Undefined port type
> org/jboss/test/ws/jaxws/jbws1822/**
> # [JBWS-2136] ClassCastException:
> com.sun.xml.ws.server.EndpointMessageContextImpl
> org/jboss/test/ws/jaxws/namespace/**
> # [JBAS-5359] mapped-name is required for context of deployment
> org/jboss/test/ws/jaxws/jbws1611/**
> {code}
--
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: (MCOMPILER-72) Add support for include/exclude files
Add support for include/exclude files
-
Key: MCOMPILER-72
URL: http://jira.codehaus.org/browse/MCOMPILER-72
Project: Maven 2.x Compiler Plugin
Issue Type: New Feature
Affects Versions: 2.0.2
Reporter: Thomas Diesler
Similar to Ant, the compiler plugin should support excludes defined in an
external file like this
{code:xml}
maven-compiler-plugin
2.0.2.SP1
../test-excludes-jboss422.txt
{code}
The exclude file would look like this
{code}
# [JBWS-2135] WebServiceException: Undefined port type
org/jboss/test/ws/jaxws/jbws1822/**
# [JBWS-2136] ClassCastException:
com.sun.xml.ws.server.EndpointMessageContextImpl
org/jboss/test/ws/jaxws/namespace/**
# [JBAS-5359] mapped-name is required for context of deployment
org/jboss/test/ws/jaxws/jbws1611/**
{code}
--
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] Reopened: (SUREFIRE-486) Exlude tests via an external exlude file
[ http://jira.codehaus.org/browse/SUREFIRE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler reopened SUREFIRE-486: - Binding the execution of a test to the test source code is not a good idea. Also your suggested solution would introduce a dependency to a particular testing framework/version Suppose you have a test suite that runs against various environments. In environment A the test is expected to pass in environment B the test should be excluded. Switching the exclude file depending on environment is common practice in various TCKs (Test Compatibility Kit) Please have a look at http://jbws.dyndns.org/mediawiki/index.php?title=WSF for more background on this. > Exlude tests via an external exlude file > > > Key: SUREFIRE-486 > URL: http://jira.codehaus.org/browse/SUREFIRE-486 > Project: Maven Surefire > Issue Type: New Feature >Reporter: Thomas Diesler > > Similar to Ant, Surefire should support excludes defined in an external file > like this > >test-excludes-jboss501.txt > > The exclude file would look like this > # [JBWS-2135] WebServiceException: Undefined port type > org/jboss/test/ws/jaxws/jbws1822/** > # [JBWS-2136] ClassCastException: > com.sun.xml.ws.server.EndpointMessageContextImpl > org/jboss/test/ws/jaxws/namespace/** > # [JBAS-5359] mapped-name is required for context of deployment > org/jboss/test/ws/jaxws/jbws1611/** -- 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-3553) cannot resolve dependency with scope import
[
http://jira.codehaus.org/browse/MNG-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132836#action_132836
]
Thomas Diesler commented on MNG-3553:
-
In a more general way, it seem that project A cannot have a dependency on B if
B defines a dependency with scope import that is deployed on a non-central
snapshot repository.
> cannot resolve dependency with scope import
> ---
>
> Key: MNG-3553
> URL: http://jira.codehaus.org/browse/MNG-3553
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
>Reporter: Thomas Diesler
>
> This pom when added as a dependency of another project does not see
> repository http://snapshots.jboss.org/maven2
>
>
>
>
> org.jboss.jbossas
> jboss-as-component-matrix
> ${jboss.version}
> pom
> import
>
>
>
> with effective settings
> [EMAIL PROTECTED] trunk]$ mvn help:effective-settings
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] JBoss Web Services - Stack CXF
> [INFO] JBoss Web Services - Stack CXF Management
> [INFO] JBoss Web Services - Stack CXF Runtime Server
> [INFO] JBoss Web Services - Stack CXF Runtime Client
> [INFO] Searching repository for plugin with prefix: 'help'.
> [INFO]
>
> [INFO] Building JBoss Web Services - Stack CXF
> [INFO]task-segment: [help:effective-settings] (aggregator-style)
> [INFO]
>
> [INFO] [help:effective-settings]
> [INFO]
> Effective settings:
>
> /home/tdiesler/.m2/repository
>
>
>
>
> !jboss.repository.off
>
>
>
>
>
> snapshots.jboss.org
> http://snapshots.jboss.org/maven2
>
>
>
> false
>
> repository.jboss.org
> http://repository.jboss.org/maven2
>
>
> jboss.repository
>
>
>
> user-profile
>
>
> org.jboss.maven.plugins
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3553) cannot resolve dependency with scope import
cannot resolve dependency with scope import
---
Key: MNG-3553
URL: http://jira.codehaus.org/browse/MNG-3553
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Reporter: Thomas Diesler
This pom when added as a dependency of another project does not see repository
http://snapshots.jboss.org/maven2
org.jboss.jbossas
jboss-as-component-matrix
${jboss.version}
pom
import
with effective settings
[EMAIL PROTECTED] trunk]$ mvn help:effective-settings
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] JBoss Web Services - Stack CXF
[INFO] JBoss Web Services - Stack CXF Management
[INFO] JBoss Web Services - Stack CXF Runtime Server
[INFO] JBoss Web Services - Stack CXF Runtime Client
[INFO] Searching repository for plugin with prefix: 'help'.
[INFO]
[INFO] Building JBoss Web Services - Stack CXF
[INFO]task-segment: [help:effective-settings] (aggregator-style)
[INFO]
[INFO] [help:effective-settings]
[INFO]
Effective settings:
/home/tdiesler/.m2/repository
!jboss.repository.off
snapshots.jboss.org
http://snapshots.jboss.org/maven2
false
repository.jboss.org
http://repository.jboss.org/maven2
jboss.repository
user-profile
org.jboss.maven.plugins
--
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-3553) cannot resolve dependency with scope import
[
http://jira.codehaus.org/browse/MNG-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132835#action_132835
]
Thomas Diesler commented on MNG-3553:
-
When I build the project that contains the dependency with scope 'import' it
works. However when I use that project as a dependency of another project, the
import cannot be resolved
> cannot resolve dependency with scope import
> ---
>
> Key: MNG-3553
> URL: http://jira.codehaus.org/browse/MNG-3553
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
>Reporter: Thomas Diesler
>
> This pom when added as a dependency of another project does not see
> repository http://snapshots.jboss.org/maven2
>
>
>
>
> org.jboss.jbossas
> jboss-as-component-matrix
> ${jboss.version}
> pom
> import
>
>
>
> with effective settings
> [EMAIL PROTECTED] trunk]$ mvn help:effective-settings
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] JBoss Web Services - Stack CXF
> [INFO] JBoss Web Services - Stack CXF Management
> [INFO] JBoss Web Services - Stack CXF Runtime Server
> [INFO] JBoss Web Services - Stack CXF Runtime Client
> [INFO] Searching repository for plugin with prefix: 'help'.
> [INFO]
>
> [INFO] Building JBoss Web Services - Stack CXF
> [INFO]task-segment: [help:effective-settings] (aggregator-style)
> [INFO]
>
> [INFO] [help:effective-settings]
> [INFO]
> Effective settings:
>
> /home/tdiesler/.m2/repository
>
>
>
>
> !jboss.repository.off
>
>
>
>
>
> snapshots.jboss.org
> http://snapshots.jboss.org/maven2
>
>
>
> false
>
> repository.jboss.org
> http://repository.jboss.org/maven2
>
>
> jboss.repository
>
>
>
> user-profile
>
>
> org.jboss.maven.plugins
>
>
--
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: (SUREFIRE-486) Exlude tests via an external exlude file
Exlude tests via an external exlude file Key: SUREFIRE-486 URL: http://jira.codehaus.org/browse/SUREFIRE-486 Project: Maven Surefire Issue Type: New Feature Reporter: Thomas Diesler Similar to Ant, Surefire should support excludes defined in an external file like this test-excludes-jboss501.txt The exclude file would look like this # [JBWS-2135] WebServiceException: Undefined port type org/jboss/test/ws/jaxws/jbws1822/** # [JBWS-2136] ClassCastException: com.sun.xml.ws.server.EndpointMessageContextImpl org/jboss/test/ws/jaxws/namespace/** # [JBAS-5359] mapped-name is required for context of deployment org/jboss/test/ws/jaxws/jbws1611/** -- 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-3546) command line cannot overwrite pom properties
[ http://jira.codehaus.org/browse/MNG-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132465#action_132465 ] Thomas Diesler commented on MNG-3546: - Why is it not ok for system properties to take preference over pom ones? > command line cannot overwrite pom properties > > > Key: MNG-3546 > URL: http://jira.codehaus.org/browse/MNG-3546 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.9 >Reporter: Thomas Diesler > > With a pom like this > > localhost > > and a command line like this > mvn -Pjboss422 -Djboss.bind.address=foo clean test-compilecxf.xml > I get a filtered resource like this >address='http://localhost:8080/jaxws-cxf-descriptor' > > implementor='org.jboss.test.ws.jaxws.cxf.descriptor.DescriptorEndpointImpl'> > > > > > > > Note, the bind address is localhost -- 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-3546) command line cannot overwrite pom properties
[ http://jira.codehaus.org/browse/MNG-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132141#action_132141 ] Thomas Diesler commented on MNG-3546: - As a workaround, I can define the property in a profile no-jboss-bind-address !jboss.bind.address localhost > command line cannot overwrite pom properties > > > Key: MNG-3546 > URL: http://jira.codehaus.org/browse/MNG-3546 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.9 >Reporter: Thomas Diesler > > With a pom like this > > localhost > > and a command line like this > mvn -Pjboss422 -Djboss.bind.address=foo clean test-compilecxf.xml > I get a filtered resource like this >address='http://localhost:8080/jaxws-cxf-descriptor' > > implementor='org.jboss.test.ws.jaxws.cxf.descriptor.DescriptorEndpointImpl'> > > > > > > > Note, the bind address is localhost -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3546) command line cannot overwrite pom properties
command line cannot overwrite pom properties Key: MNG-3546 URL: http://jira.codehaus.org/browse/MNG-3546 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.0.9 Reporter: Thomas Diesler With a pom like this localhost and a command line like this mvn -Pjboss422 -Djboss.bind.address=foo clean test-compilecxf.xml I get a filtered resource like this Note, the bind address is localhost -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-319) Cannot bind to lifecycle with multiple modules
Cannot bind to lifecycle with multiple modules
--
Key: MASSEMBLY-319
URL: http://jira.codehaus.org/browse/MASSEMBLY-319
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Reporter: Thomas Diesler
Executing
> mvn package
using this plugin config
maven-assembly-plugin
deploy-artifacts
true
false
src/main/scripts/assembly-deploy-artifacts.xml
build-deploy-artifacts
package
directory-inline
with a descriptor using module sets
org.jboss.ws:jbossws-cxf-client
org.jboss.ws:jbossws-cxf-server
lib
${module.artifactId}.${module.extension}
false
${module.artifactId}.${module.extension}
true
*:cxf-*
*:geronimo-javamail*
*:geronimo-ws-metadata*
*:jaxb-api:jar
*:jaxb-impl:jar
*:jaxb-xjc:jar
*:jaxrpc-api:jar
*:jaxws-api:jar
*:jbossws-common:jar
*:jbossws-framework:jar
*:jbossws-spi:jar
*:jbossws-jboss42:jar
*:neethi:jar
*:saaj-api:jar
*:saaj-impl:jar
*:spring-beans:jar
*:spring-context:jar
*:spring-core:jar
*:stax-api:jar
*:wsdl4j:jar
*:xml-resolver:jar
*:XmlSchema:jar
wstx.jar
true
*:wstx-asl:jar
org.jboss.ws:jbossws-cxf-management
lib
${module.artifactId}.${module.extension}
false
false
I get
[INFO] Executed tasks
[INFO] [source:jar {execution: attach-sources}]
[INFO] [assembly:directory-inline {execution: build-deploy-artifacts}]
[INFO] Reading assembly descriptor:
src/main/scripts/assembly-deploy-artifacts.xml
[INFO] Processing DependencySet (output=bin)
[WARNING] Cannot include project artifact:
org.jboss.ws:jbossws-cxf:pom:3.0.2-SNAPSHOT; it doesn't have an associated file
or directory.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error creating assembly: Artifact:
org.jboss.ws:jbossws-cxf-server:jar:3.0.2-SNAPSHOT (included by module) does
not have an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
It seems that package was not executed in module
'org.jboss.ws:jbossws-cxf-server'
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-317) useStrictFiltering requires dependency in all included modules
useStrictFiltering requires dependency in all included modules
--
Key: MASSEMBLY-317
URL: http://jira.codehaus.org/browse/MASSEMBLY-317
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Reporter: Thomas Diesler
With this moduleSet all dependency artifacts must be defined in all included
modules
org.jboss.ws:jbossws-cxf-server
org.jboss.ws:jbossws-cxf-client
server/default/deploy/jbossws.sar
${module.artifactId}.${module.extension}
false
${module.artifactId}.${module.extension}
true
*:cxf-*
*:geronimo-javamail*
*:geronimo-ws-metadata*
*:jaxrpc-api*
*:jaxws-api*
*:neethi*
*:saaj-api*
*:saaj-impl*
*:spring-beans*
*:spring-context*
*:spring-core*
*:wsdl4j*
*:xml-resolver*
*:XmlSchema*
I believe this should be changed such that the dependency is satisfied by at
least one module.
--
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: (MASSEMBLY-316) useProjectArtifact is documented but not in schema
[ http://jira.codehaus.org/browse/MASSEMBLY-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131739#action_131739 ] Thomas Diesler commented on MASSEMBLY-316: -- [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:directory' --> [DEBUG] (s) appendAssemblyId = false [DEBUG] (f) attach = true [DEBUG] (s) basedir = /home/tdiesler/svn/jbossws/stack/cxf/branches/tdiesler/trunk [DEBUG] (s) descriptors = [Ljava.lang.String;@10e8647 [DEBUG] (f) dryRun = false [DEBUG] (f) executedProject = MavenProject: org.jboss.ws:jbossws-cxf:3.0.2-SNAPSHOT @ /home/tdiesler/svn/jbossws/stack/cxf/branches/tdiesler/trunk/pom.xml [DEBUG] (s) finalName = deploy-structure-jboss422 [DEBUG] (f) ignoreDirFormatExtensions = true [DEBUG] (s) ignoreMissingDescriptor = false [DEBUG] (s) includeSite = false [DEBUG] (s) localRepository = [local] -> file:///home/tdiesler/.m2/repository [DEBUG] (s) outputDirectory = /home/tdiesler/svn/jbossws/stack/cxf/branches/tdiesler/trunk/target [DEBUG] (s) reactorProjects = [MavenProject: org.jboss.ws:jbossws-cxf:3.0.2-SNAPSHOT @ /home/tdiesler/svn/jbossws/stack/cxf/branches/tdiesler/trunk/pom.xml, MavenProject: org.jboss.ws:jbossws-cxf-client:3.0.2-SNAPSHOT @ /home/tdiesler/svn/jbossws/stack/cxf/branches/tdiesler/trunk/modules/client/pom.xml] [DEBUG] (f) remoteRepositories = [[snapshots.jboss.org] -> http://snapshots.jboss.org/maven2, [repository.jboss.org] -> http://repository.jboss.org/maven2, [apache.incubating.repository] -> http://people.apache.org/repo/m2-incubating-repository, [java.net] -> http://download.java.net/maven/1/, [central] -> http://repo1.maven.org/maven2] [DEBUG] (s) siteDirectory = /home/tdiesler/svn/jbossws/stack/cxf/branches/tdiesler/trunk/target/site [DEBUG] (f) skipAssembly = false [DEBUG] (s) tarLongFileMode = warn [DEBUG] (s) tempRoot = /home/tdiesler/svn/jbossws/stack/cxf/branches/tdiesler/trunk/target/archive-tmp [DEBUG] (s) workDirectory = /home/tdiesler/svn/jbossws/stack/cxf/branches/tdiesler/trunk/target/assembly/work > useProjectArtifact is documented but not in schema > -- > > Key: MASSEMBLY-316 > URL: http://jira.codehaus.org/browse/MASSEMBLY-316 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Reporter: Thomas Diesler > > I like to include a module's dependencies, but not the projectArtifact > itself. This functionality seem to be provided by 'useProjectArtifact' > http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html > which is not defined in > http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd > and does not seem to work anymore. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-316) useProjectArtifact is documented but not in schema
useProjectArtifact is documented but not in schema -- Key: MASSEMBLY-316 URL: http://jira.codehaus.org/browse/MASSEMBLY-316 Project: Maven 2.x Assembly Plugin Issue Type: Bug Reporter: Thomas Diesler I like to include a module's dependencies, but not the projectArtifact itself. This functionality seem to be provided by 'useProjectArtifact' http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html which is not defined in http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd and does not seem to work anymore. -- 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: (MASSEMBLY-315) outputFileNameMapping in dependencySet uses pom's artifactid
[
http://jira.codehaus.org/browse/MASSEMBLY-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131738#action_131738
]
Thomas Diesler commented on MASSEMBLY-315:
--
With this config
server/default/lib
true
false
*:jaxws-api:jar
*:jbossws-common:jar
*:jbossws-framework:jar
*:jbossws-spi:jar
*:saaj-api:jar
I get
[EMAIL PROTECTED] trunk]$ ls
target/deploy-structure-jboss422/server/default/lib/
jaxws-api-2.0.jar
jbossws-framework-3.0.2-20080418.213730-13.jar saaj-api-1.3.jar
jbossws-common-3.0.0-20080419.202718-10.jar
jbossws-spi-3.0.0-20080418.213543-7.jar
as expected, but I don't want the version extensions.
> outputFileNameMapping in dependencySet uses pom's artifactid
>
>
> Key: MASSEMBLY-315
> URL: http://jira.codehaus.org/browse/MASSEMBLY-315
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Reporter: Thomas Diesler
>
> The descriptor below incorrectly produces a single output file in
> server/default/lib
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd";>
>
> deploy-structure-jboss422
>
> dir
>
> false
>
>
>
>
>
> bin
> true
> true
>
> *:jbossws-framework:zip:scripts
>
>
>
>
>
> server/default/lib
>
> ${artifactId}.${extension}
> true
> false
>
> *:jaxws-api:jar
> *:jbossws-common:jar
> *:jbossws-framework:jar
> *:jbossws-spi:jar
> *:saaj-api:jar
>
>
>
>
>
>
>
>
> org.jboss.ws:jbossws-cxf-client
>
>
> client
>
> ${module.artifactId}.${module.extension}
> false
>
>
>
> ${module.artifactId}.${module.extension}
> true
>
> *:cxf-*
> *:geronimo-javamail*
> *:geronimo-ws-metadata*
> *:jaxb-api:jar
> *:jaxb-impl:jar
> *:jaxb-xjc:jar
> *:jaxws-api:jar
> *:jbossws-common:jar
> *:jbossws-framework:jar
> *:jbossws-spi:jar
> *:neethi:jar
> *:saaj-api:jar
> *:saaj-impl:jar
> *:spring-beans:jar
> *:spring-context:jar
> *:spring-core:jar
> *:stax-api:jar
> *:wsdl4j:jar
> *:xml-resolver:jar
> *:XmlSchema:jar
>
>
>
> wstx.jar
> true
>
> *:wstx-asl:jar
>
>
>
>
>
>
>
>
> [EMAIL PROTECTED] trunk]$ ls
> target/deploy-structure-jboss422/server/default/lib/
> jbossws-cxf.${extension}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-315) outputFileNameMapping in dependencySet uses pom's artifactid
outputFileNameMapping in dependencySet uses pom's artifactid
Key: MASSEMBLY-315
URL: http://jira.codehaus.org/browse/MASSEMBLY-315
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Reporter: Thomas Diesler
The descriptor below incorrectly produces a single output file in
server/default/lib
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd";>
deploy-structure-jboss422
dir
false
bin
true
true
*:jbossws-framework:zip:scripts
server/default/lib
${artifactId}.${extension}
true
false
*:jaxws-api:jar
*:jbossws-common:jar
*:jbossws-framework:jar
*:jbossws-spi:jar
*:saaj-api:jar
org.jboss.ws:jbossws-cxf-client
client
${module.artifactId}.${module.extension}
false
${module.artifactId}.${module.extension}
true
*:cxf-*
*:geronimo-javamail*
*:geronimo-ws-metadata*
*:jaxb-api:jar
*:jaxb-impl:jar
*:jaxb-xjc:jar
*:jaxws-api:jar
*:jbossws-common:jar
*:jbossws-framework:jar
*:jbossws-spi:jar
*:neethi:jar
*:saaj-api:jar
*:saaj-impl:jar
*:spring-beans:jar
*:spring-context:jar
*:spring-core:jar
*:stax-api:jar
*:wsdl4j:jar
*:xml-resolver:jar
*:XmlSchema:jar
wstx.jar
true
*:wstx-asl:jar
[EMAIL PROTECTED] trunk]$ ls
target/deploy-structure-jboss422/server/default/lib/
jbossws-cxf.${extension}
--
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: (MANTRUN-86) Cannot handle multiple tasks elements
[
http://jira.codehaus.org/browse/MANTRUN-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131538#action_131538
]
Thomas Diesler commented on MANTRUN-86:
---
Ok, in that case we might want to rename the issue to "Improve configuration
error reporting"
> Cannot handle multiple tasks elements
> -
>
> Key: MANTRUN-86
> URL: http://jira.codehaus.org/browse/MANTRUN-86
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.1
>Reporter: Thomas Diesler
>
> {code:xml}
>
> maven-antrun-plugin
>
>
> install
>
> run
>
>
>
>
>value="${jboss.local.repository}"/>
>
>
>
>
>
>
>
>
>
> {code}
> Always executes the last tasks element although 'jboss.local.repository' is
> set
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [echo] Cannot install to
> jboss.local.repository=/home/tdiesler/svn/jboss.local.repository
> [INFO] Executed tasks
--
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: (MANTRUN-89) Cannot define execution order explicitly
[
http://jira.codehaus.org/browse/MANTRUN-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130732#action_130732
]
Thomas Diesler commented on MANTRUN-89:
---
This issue probably applies to plugin execution in general, not just antrun
> Cannot define execution order explicitly
>
>
> Key: MANTRUN-89
> URL: http://jira.codehaus.org/browse/MANTRUN-89
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
>Reporter: Thomas Diesler
>
> In this example antrun:run is excuted after dependency:copy-dependencies by
> virtue of plugin order. Preferable would be an explicit order definition. For
> example, a plugin could export a 'phase-id' that another uses in its 'phase'
> element.
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> copy-dependencies
> package
>
> copy-dependencies
>
>
>
> ${project.build.directory}/thirdparty
> true
>
>
>
>
>
> maven-antrun-plugin
>
>
> package
>
> run
>
>
>
>
>
>
>
>
>
>
--
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: (MANTRUN-89) Cannot define execution order explicitly
Cannot define execution order explicitly
Key: MANTRUN-89
URL: http://jira.codehaus.org/browse/MANTRUN-89
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Reporter: Thomas Diesler
In this example antrun:run is excuted after dependency:copy-dependencies by
virtue of plugin order. Preferable would be an explicit order definition. For
example, a plugin could export a 'phase-id' that another uses in its 'phase'
element.
org.apache.maven.plugins
maven-dependency-plugin
copy-dependencies
package
copy-dependencies
${project.build.directory}/thirdparty
true
maven-antrun-plugin
package
run
--
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: (MANTRUN-88) Profile properties not handled correctly
Profile properties not handled correctly
Key: MANTRUN-88
URL: http://jira.codehaus.org/browse/MANTRUN-88
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Reporter: Thomas Diesler
[INFO] [help:effective-settings]
[INFO]
Effective settings:
/home/tdiesler/.m2/repository
/home/tdiesler/svn/jboss.local.repository
jbossws
This executes
because 'jboss.local.repository' is set, however later the property has no value
[INFO] Executing tasks
[echo] Install to jboss.local.repository=${jboss.local.repository}
init:
[echo] version.id=3.0.2-SNAPSHOT
[echo] repository.id=3.0.2-SNAPSHOT
[echo] jboss.local.repository=${jboss.local.repository}
--
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: (MANTRUN-87) Improve propagation of properties
Improve propagation of properties - Key: MANTRUN-87 URL: http://jira.codehaus.org/browse/MANTRUN-87 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Reporter: Thomas Diesler It seems that maven properties cannot be propagated to the ant script unless explicitly set -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANTRUN-86) Cannot handle multiple tasks elements
Cannot handle multiple tasks elements
-
Key: MANTRUN-86
URL: http://jira.codehaus.org/browse/MANTRUN-86
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Reporter: Thomas Diesler
maven-antrun-plugin
install
run
Always executes the last tasks element although 'jboss.local.repository' is set
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] Cannot install to
jboss.local.repository=/home/tdiesler/svn/jboss.local.repository
[INFO] Executed tasks
--
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: (MASSEMBLY-234) Artifacts not deployed
[
http://jira.codehaus.org/browse/MASSEMBLY-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130681#action_130681
]
thomas diesler commented on MASSEMBLY-234:
--
Actually, this is not well commented at all.
The FAQ page
http://maven.apache.org/plugins/maven-assembly-plugin/faq.html
reads
Q: If the Assembly Plugin is run during the package phase, do my assemblies get
deployed during the deploy phase?
A: Yes. The assemblies created by the Assembly Plugin is attached to your
project so it gets deployed too.
and does not mention the assembly:attached nor the assembly:single goal
> Artifacts not deployed
> --
>
> Key: MASSEMBLY-234
> URL: http://jira.codehaus.org/browse/MASSEMBLY-234
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-1
> Environment: Windows XP, Maven 2.0.7, Java 1.5.0_09, latest version
> of all conspiring Maven plugins
>Reporter: Brian Williams
>Assignee: John Casey
> Fix For: 2.2-beta-2
>
>
> I attached my two assembly descriptors to the package phase, they get created
> correctly, but only the original JAR of my project gets deployed when I run
> "mvn deploy". Each of my descriptors makes a ZIP containing the JAR my
> project compiles plus other resources (don't ask me why they don't want them
> as part of the JAR).
> When I declared version 2.1 for the assembly plugin, my two assemblies
> deployed with my original JAR. This is the relevant section of my POM.xml:
> {{
> maven-assembly-plugin
> 2.1
>
>
> package
>
>
> assembly/windows.xml
> assembly/linux.xml
>
>
> assembly
>
>
> }}
--
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
