[ https://issues.jboss.org/browse/JBDS-3071?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3071: ---------------------------------- Did a quick test to see if we could simply exclude the IUs from the installer jar... {code} diff --git a/installer/pom.xml b/installer/pom.xml index 0ca122d..53decb0 100644 --- a/installer/pom.xml +++ b/installer/pom.xml @@ -130,7 +130,7 @@ </artifactItem> </artifactItems> <outputDirectory>${project.build.directory}/update/jbds</outputDirectory> - <excludes>**/*.pack.gz</excludes> + <excludes>**/*.source_*.jar, **/*.pack.gz</excludes> {code} ... and YES, that works... until someone tries to install the source features that are listed in the installer jar (but which don't exist). For this to work we'd need to regen the metadata. Therefore a better solution is probably to build an actual update site w/ Tycho which excludes source features, and another which includes them (for use in the update site). Might even be able to transform one category.xml into another so we don't have to maintain two nearly-identical copies of the same file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)