[jbosstools-issues] [JBoss JIRA] (JBIDE-23761) ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site

[ https://issues.jboss.org/browse/JBIDE-23761?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23761: ------------------------------------ And coretests is still red: {code} [WARNING] Mirror tool: Problems resolving provisioning plan.: [Unable to satisfy dependency from AM2-v20170121-0052-B6049.JBoss Tools - Core Tests 1.0.0.A2E87EkycKlP9bFjuEy7D6Tor56H0Dg37IIg3sE7 to org.jboss.ide.eclipse.as.test.feature.source.feature.group [3.2.3.v20170119-2212].; Unable to satisfy dependency from AM2-v20170121-0052-B6049.JBoss Tools - Core Tests 1.0.0.A2E87EkycKlP9bFjuEy7D6Tor56H0Dg37IIg3sE7 to org.jboss.ide.eclipse.as.test.feature.feature.group [3.2.3.v20170119-2212].] {code} But the coretests site contains these features: {code} [ ] org.jboss.ide.eclipse.as.test.feature.source_3.2.3.v20170120-2034.jar 20-Jan-2017 17:00 3.6K [ ] org.jboss.ide.eclipse.as.test.feature_3.2.3.v20170120-2034.jar 20-Jan-2017 17:00 2.5K {code} So... why is the build trying to resolve 3.2.3.v20170119-2212 when the latest is 3.2.3.v20170120-2034 ? Well... it's not a timing issue -- could be a problem with the maven reactor / target platform pulling from two different jbosstools-server_master builds: {code} http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser... http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser... and http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser... http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser... So... two solutions: a) rebuild the jbosstools-server to remove the old B1394 build from the composite. b) add -Djbosstools_site_suffix=latest/all/repo to the coretests (and other aggregate jobs) so that it only reads a single upstream repo per component, rather than the 2-site composite. -- This message was sent by Atlassian JIRA (v7.2.3#72005)