[jbosstools-issues] [JBoss JIRA] (JBTIS-388) Establish a separate JBDSIS target platform with no community-specific bits.

Establish a separate JBDSIS target platform with no community-specific bits. ---------------------------------------------------------------------------- Key: JBTIS-388 URL: https://issues.jboss.org/browse/JBTIS-388 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: target-platform Affects Versions: 4.2.1.Final-TP Reporter: Paul Leacu Assignee: Paul Leacu Priority: Blocker Fix For: 4.2.1.Final-TP Currently the JBDSIS target platform is a straight copy of the JBTIS TP. The JBTIS TP includes community.target which has dependent features which should not be picked up in the JBDSIS production target platform repository. e.g. <unit id="org.jboss.tools.community.central.feature.feature.group" version="1.3.0.Final-v20141016-1914-B105"/> <unit id="org.jboss.tools.community.project.examples.feature.feature.group" version="2.0.0.Final-v20141016-1914-B105"/> Solution is to have the target-platform pom create the jbdsis target platform (without merging the community.target file). ref: http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform... # .target files http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform... http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform... http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform... http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform... Reason: See above Project page/sources: n/a Version: 4.2.1.CR2 License and owner: EPL Original p2 repo: http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform... JBoss mirror: n/a Include Sources: Yes Affected projects: JBTIS components Include in JBDS: Yes - JBDSIS Type of dependency: distribution List of bundles added/removed: none