[
https://issues.jboss.org/browse/JBDS-3115?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-3115:
-------------------------------------------
That the categories are mixed up is definitely not right - those should be consistent for
same connectorid's.
But lets get a few things straightened out.
Central connectors are not a 1-to-1 mapping to eclipse features.
connectors can have 1 or many features and 2 connectors can have overlapping features.
The original point of having AngularJS feature in both main and central is so the
AngularJS w/Forge has a connector id to point to that works in both cases of wether you
have earlyaccess or not enabled. In this case this would be for Web development since
ionic can be used without hybrid mobile development too.
If Mobile/Hybrid *also* thinks it is good to have a ionic angularJS support installed
this can be added - but that would be an *addition* - for now it sounds like something
that fits to be added under the existing hybrid mobile tooling connector ?
Include Ionic Palette in Central
--------------------------------
Key: JBDS-3115
URL:
https://issues.jboss.org/browse/JBDS-3115
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: p2-product
Affects Versions: 8.0.0.CR1
Reporter: Denis Golovin
Assignee: Denis Golovin
Priority: Blocker
Fix For: 8.0.0.CR1
Attachments: 3115-jbds-vs-jbt-connector.differences.central.png,
3115-jbds-vs-jbt-connector.differences.png, central after early access.png, central before
early access.png
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)