What I don't understand is why doesn't the target-platform-validation see this missing dependency? In general, it should and used to fail when something is transitively missing... (in this case com.thoughtworks.xstream).

Three items in our tp cannot be installed into clean luna m6 ------------------------------------------------------------ Key: JBIDE-16910 URL: https://issues.jboss.org/browse/JBIDE-16910 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.2.0.Beta1 Reporter: Rob Stryker Assignee: Nick Boldt Fix For: 4.2.0.Beta2 Attachments: bugForNick.png cd jbosstools-target-platforms git checkout 4.40.x mvn clean verify -Dmirror-target-to-repo.includeSources=true cd ~/apps/eclipse mkdir lunam6 cd lunam6 // acquire tar gz file tar xvzf (filename for luna m6) cd eclipse ./eclipse Help -> Install new software Select "local", point to jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ Wait for it to calculate what can or cannot be installed. See 3 items that cannot be installed (See screenshot) Error: {code} Cannot complete the install because one or more required items could not be found. Software being installed: Atlassian Connector for Eclipse Usage Monitoring 3.2.2.v20130909 (com.atlassian.connector.eclipse.monitor.feature.group 3.2.2.v20130909) Missing requirement: Atlassian Connector for Eclipse Usage Data Collector 3.2.2.v20130909 (com.atlassian.connector.eclipse.monitor.core 3.2.2.v20130909) requires 'bundle com.thoughtworks.xstream 0.0.0' but it could not be found Cannot satisfy dependency: From: Atlassian Connector for Eclipse Usage Monitoring 3.2.2.v20130909 (com.atlassian.connector.eclipse.monitor.feature.group 3.2.2.v20130909) To: com.atlassian.connector.eclipse.monitor.core [3.2.2.v20130909] {code}