When I run testsuite of EAP 6.1.0 using command [1], where JBOSS_HOME is a path EAP 6.1.0, the manualmode tests fail with error [2]: It uses path defined in jboss.dist property defined in testsuite/integration/pom.xml instead of the one provided -Djboss.dist which should redefine it. [1] ./integration-tests.sh -Dpublic-repos -DallTests -Dmaven.repo.local=${MAVEN_REPO_LOCAL} -Djboss.dist=${JBOSS_HOME} -Dmaven.test.failure.ignore=true -Dsurefire.forked.process.timeout=3600 [2] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7-redhat-1:run (build-manual-mode-servers) on project jboss-as-ts-integ-manualmode: An Ant BuildException has occured: The following error occurred while executing this line: [ERROR] /mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/testsuite/integration/src/test/scripts/manualmode-build.xml:52: /mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/build/target/jboss-as-7.2.0.Final-redhat-8/modules does not exist. [ERROR] around Ant part ...<ant antfile="/mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/testsuite/integration/manualmode/../src/test/scripts/manualmode-build.xml">... @ 4:180 in /mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/testsuite/integration/manualmode/target/antrun/build-main.xml
I am able to run the testsuite using simple workaround => by changing <jboss.dist>${jbossas.project.dir}/build/target/jboss-as-${jboss.as.release.version}</jboss.dist> to <jboss.dist>${jboss.dist}</jboss.dist> in testsuite/integration/pom.xml
Looks like this is failing because of: https://jira.codehaus.org/browse/MANTRUN-178 One workaround you could try is to define the jboss.dist property as an expression referencing another property, say jboss.dist.dir. This can have a value in the pom.xml properties section. You would then use -Djboss.dist.dir=/path/to/jboss and allow maven pom interpolation to supply the CLI value for ${jboss.dist} and have that picked up properly by the antrun plugin. It looks like the property resolver in the antrun plugin isn't using the MavenSession's getUserProperties() correctly.
*** Bug 982019 has been marked as a duplicate of this bug. ***
BZ 982019 contains attachments for osgi and manual mode failures
There's a high chance that the workaround suggested by John in comment #2 will work. I use it for other properties. I could get to it soon.
The workaround for this issue may potentially harm other scenarios, and needs to be tested really well. Hence it should really not go to EAP without getting to upstream first.
For the reasons above, I'm giving it an DEV NACK. Meaning that it won't be in EAP 6.2 yet (I can't set the eap_620 flag).
Ondra, why should the workaround suggested by John be potentially harmful in any way to other scenarios? Could you provide example of such scenario?
I prepared a fix for the OSGi part of this issue, as it is described in #982019 (that BZ was closed as duplicate, so resolving it as part of this issue). PR: https://github.com/jbossas/jboss-eap/pull/739
Fix for manualmode and patching modules: https://github.com/jbossas/jboss-eap/pull/736
Fixed in EAP 6.3.0 DR0. There is no more issue with mvn install EAP src, erasure of built EAP and then running integration tests with -Djboss.dist specified.