[overlord-issues] [JBoss JIRA] (RTGOV-411) Timestamped version of overlord-commons-config being included in rtgov EAP module

[ https://issues.jboss.org/browse/RTGOV-411?page=com.atlassian.jira.plugin.... ] ivan mckinley commented on RTGOV-411: ------------------------------------- Suppose this isn't really a bug in rtgov. http://docs.codehaus.org/display/MAVEN/Repository+-+SNAPSHOT+Handling its working as expected. it will utilize the latest snapshot in https://repository.jboss.org/nexus/content/repositories/snapshots/ for the jbossas release which is copied to the modules folder of the release - https://repository.jboss.org/nexus/content/repositories/snapshots/org/ove... copied to $targetfolder/overlord-rtgov-jbossas-2.0.0-SNAPSHOT/modules/rtgov/org/overlord/rtgov/main contents of acs-epn-2.0.0-SNAPSHOT.jar active-collection-2.0.0-SNAPSHOT.jar activity-2.0.0-SNAPSHOT.jar analytics-2.0.0-SNAPSHOT.jar ep-core-2.0.0-SNAPSHOT.jar ep-drools-2.0.0-SNAPSHOT.jar ep-mvel-2.0.0-SNAPSHOT.jar epn-core-2.0.0-SNAPSHOT.jar module.xml overlord-commons-config-2.0.1-20140324.184906-3.jar rtgov-common-2.0.0-SNAPSHOT.jar jboss-as modules does not recognise this as the latest version as module.xml references 2.0.1-SNAPSHOT and not 2.0.1-<latestdate>.jar overlord-commons-config-2.0.1-20140324.184906-3.jar note: this applies to the other components which make use of the overlord commons version propert $overlord-commons.version -- 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