[
https://issues.jboss.org/browse/RTGOV-411?page=com.atlassian.jira.plugin....
]
Gary Brown commented on RTGOV-411:
----------------------------------
Looks like there is a mismatch between the actual retrieved artifact (timestamped) and the
one that gets recorded in the module.xml using the filter.
Workaround solution is to build overlord-commons locally. Longer term solution:
1) Only use non-snapshot version for overlord-commons - not ideal
2) Don't include the version in the artifacts stored within the module
3) Get rid of the module
(3) is potentially an option, as over time it has become a bit redundant. All other
deployed artifacts actually reference overlord-rtgov.war, and only this war references the
org.overlord.rtgov module. Placing all of the artifacts into the war will also make
supporting domain mode easier.
Timestamped version of overlord-commons-config being included in
rtgov EAP module
---------------------------------------------------------------------------------
Key: RTGOV-411
URL:
https://issues.jboss.org/browse/RTGOV-411
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Eric Wittmann
Assignee: Gary Brown
Attachments: testout.log.zip
Reported by "imckinle" - after building rtgov from master, the rtgov EAP module
included a timestamped version of the overlord-commons-config JAR rather than the
-SNAPSHOT version. This resulted in a parse error in the module.xml.
http://pastebin.test.redhat.com/199474
http://pastebin.test.redhat.com/199477
--
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