Branch: refs/heads/master Home: https://github.com/rhq-project/rhq Commit: dec8bae46446d4cde46fe13ed76585c2cfc164b8 https://github.com/rhq-project/rhq/commit/dec8bae46446d4cde46fe13ed76585c... Author: Jay Shaughnessy <jshaughn(a)redhat.com&gt; Date: 2014-06-27 (Fri, 27 Jun 2014) Changed paths: M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/VersionedRuntimeDiscovery.java M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/VersionedSubsystemDiscovery.java Log Message: ----------- 1070326 - (JON3-42) RFE: Allow AS7 deployments to provide version in the artifact name Adding one more thing to this feature, prevent discovery of siblings resolving to the same resource key. In the somewhat unlikely case that two distinct sibling deployments resolve down to the same logical deployment, don't let it get past discovery. For example, if the user has app-1.0.war and app-2.0.war and these are *really* different apps (and they would probably have to be since EAP would stop deployment if they had the same context). In this case both would be seen as app.war, and that is a problem on the RHQ side. In this sutuation generate an agent log warning that hopefully helps a user resolve the issue. Note that resource upgrade already prevents an upgrade of siblings with the same key, so this is an analogous change.