[
https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin....
]
Paul Leacu commented on JBTIS-504:
----------------------------------
Hey [~nickboldt] -
It's time to enable the EA components. So clearly I'll re-enable them in the
early access discovery plugin.xml. My question is what to do with the existing "not
available" released-side discovery plugin.xml. See comment:
https://issues.jboss.org/browse/JBIDE-20100?focusedCommentId=13110988&...
If I just eliminate all of the
certificationId="org.jboss.tools.discovery.certification.notavailable"
connectors then the user will have no idea that "Fuse Tooling" is available
under early access. Or does "not available" only apply to the release discovery
plugin - thus I would keep all of the "not available" connectors and simply
change the descriptor text to something like "Select the 'Enable Early
Access' check box for an early access installation. Also available in Red Hat JBoss
Developer Studio 8.x"
publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site
when available
-----------------------------------------------------------------------------------
Key: JBTIS-504
URL:
https://issues.jboss.org/browse/JBTIS-504
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 4.3.0.Alpha2
Reporter: Nick Boldt
Assignee: Paul Leacu
Fix For: 4.3.0.Alpha2
Attachments: is-in-dev.png, is-in-dev_JBDS.png
Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery
jars into the JBT/JBDS CR1 site so that the "not available" connectors will be
seen in JBT/JBDS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)