[
https://issues.jboss.org/browse/DROOLS-364?page=com.atlassian.jira.plugin...
]
David Ward commented on DROOLS-364:
-----------------------------------
I do not know about the "exploded ear" scenario, but it appears that whereas
DROOLS-340 fixed the "mvn jboss-as:deploy" issue on Macs (my OS), it is still
broken on Windows. Given that this new bug (DROOLS-364) was written based on an error on
Windows, it is probable it is the same path error.
Given that, I am attaching a reproducer that might help in debugging this situation.
Again, this is for the "mvn jboss-as:deploy" usecase on Windows, not the
"exploded ear" scenario. However, they are probably the same path error.
Instructions:
1) Download and install a fresh JBoss EAP 6.1.1.
2) Download kie-eap-integration-brms-6.0.1.Final-brms-layer.zip from Nexus and extract it
on top of JBoss EAP 6.1.1.
3) Download the attached reproducer from this jira, which is aligned with Drools
6.0.1.Final: jbossas-deploy-reproducer.zip
4) Extract jbossas-deploy-reproducer.zip, and from within it's directory - on WINDOWS
- execute "mvn jboss-as:deploy".
5) On Windows, the error should look similar to the attached
windows-jboss-as-deploy-server.log.
ClasspathKieProject fails vfs: path for jar deployments and exploded
ear
------------------------------------------------------------------------
Key: DROOLS-364
URL:
https://issues.jboss.org/browse/DROOLS-364
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.Final
Environment: JBoss AS 7.1.1
Reporter: Nicolas-Xavier Vanderlinden
Assignee: Mark Proctor
Drools is not able to load kmodule.xml from an exploded ear.
17:24:45,116 WARN Unable to load pom.properties tried recursing down
from\Project\Geline\jboss-as-7.1.1.Final\standalone\deployments\geline.ear\service-impl-1.4.0-SNAPcontent
null
17:24:45,116 ERROR Unable to build index of kmodule.xml
url=vfs:/E:/Project/Geline/jboss-as-7.1.1.Final/standalone/deployments/geline.ear/service-impl-1.4.0-SNAPSHOT.jar/META-INF/kmodule.xml
null
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira