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

[Paul Leacu (JIRA)]

     [ https://issues.jboss.org/browse/JBTIS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Leacu updated JBTIS-388:
-----------------------------
    Description: 
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).

Reason: ...
Project page/sources: ...
Version: ....
License and owner: ...
Original p2 repo: http://third-party-vendor.com/path/to/updates-site/
JBoss mirror: http://downloads.jboss.org/jbosstools/updates/requirements/<projectName>
Include Sources: Yes|No
Affected projects:
Include in JBDS: Yes|No
Type of dependency: testing|central-only|distribution
List of bundles added/removed:


  was:
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.

Solution is to have the target-platform pom create the jbdsis target platform (without merging the community.target file).




> 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
>
> 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).
> Reason: ...
> Project page/sources: ...
> Version: ....
> License and owner: ...
> Original p2 repo: http://third-party-vendor.com/path/to/updates-site/
> JBoss mirror: http://downloads.jboss.org/jbosstools/updates/requirements/<projectName>
> Include Sources: Yes|No
> Affected projects:
> Include in JBDS: Yes|No
> Type of dependency: testing|central-only|distribution
> List of bundles added/removed:



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)