[jbosstools-issues] [JBoss JIRA] (JBDS-3071) JBDS Installer shouldn't contain source features/plugins

[ https://issues.jboss.org/browse/JBDS-3071?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3071: ---------------------------------- [~dgolovin] as far as I can see the installer build process simply unpacks the previously-built JBDS update site zip: {code:title=https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/pom.xml#L117-L135} <execution> <id>unpack</id> <phase>prepare-package</phase> <goals> <goal>unpack</goal> </goals> <configuration> <artifactItems> <artifactItem> <groupId>com.jboss.devstudio.core</groupId> <artifactId>com.jboss.devstudio.core.site</artifactId> <version>${project.version}</version> <type>zip</type> </artifactItem> </artifactItems> <outputDirectory>${project.build.directory}/update/jbds</outputDirectory> <excludes>**/*.pack.gz</excludes> </configuration> </execution> {code} Then that folder is composited directly using https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/... within the root of the installer jar. So... we would need to perform a p2 installation instead of a simple unpack, or else an unpack followed by a metadata regeneration so the site wouldn't contain source plugins/features. -- This message was sent by Atlassian JIRA (v6.2.6#6264)