[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15135: ------------------------------------ My only remaining concern is that since implementing this mojo, we can't build JBDS. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/devstudio.product_master/} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products (default-publish-products) on project installer: Execution default-publish-products of goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products failed: org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at file:/mnt/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/. No repository found at file:/mnt/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/jbds/. -> [Help 1] {code} There needs to be a way to disable this mojo for update site builds which do not require it, such as the build of the p2-director embedded in JBDS. On the other hand, if that's an issue w/ Tycho 0.22.0, then we need a way to build JBDS (for now) with 0.21.0, and be able to disable all this new awesomeness in the parent pom (or else the build fails because it's trying to use a combination of Tycho 0.21.0 and repo-utils 0.22.1, which is incompatible). -- This message was sent by Atlassian JIRA (v6.3.11#6341)