]
Paul Leacu edited comment on JBTIS-504 at 10/5/15 3:32 PM:
-----------------------------------------------------------
This proposal attempts to address two issues:
1. The 'not available' Integration Stack connectors are obscuring the real
stuff you can install.
2. The original Jira (20100) that said there was no way to know that Fuse Tooling was
available from EA when you get to the initial discovery window.
Keeping all of the existing connectors as 'not available' from the release side
and pointing them to the 'Enable Early Access' seems redundant and
"sucks".
Removing the "not available" connectors from the release side window doesn't
solve #2 above.
Max suggested having just one entry for all of the missing EA IS components. This seemed
logical to me. Take a look at these attachments and let me know what you think.
JBDSIS Discovery:
!disc-jbdsis.png|thumbnail!
!disc-jbdsis-ea.png|thumbnail!
JBTIS Discovery:
!jbtis-disc.png|thumbnail!
!jbtis-disc-ea.png|thumbnail!
The obvious issue is that the generic connector stays around after you install the EA
components.
was (Author: pleacu):
This proposal attempt to address to issues:
1. The 'not available' Integration Stack connectors are obscuring the real
stuff you can install.
2. The original Jira (20100) that said there was no way to know that Fuse Tooling was
available from EA when you get to the initial discovery window.
Keeping all of the existing connectors as not available from the release side and pointing
them to the 'Enable Early Access' seems redundant and "sucks".
Removing the "not available" connectors from the release side window doesn't
solve #2 above.
Max suggested having just one entry for all of the missing EA IS components. This seemed
logical to me. Take a look at these attachments and let me know what you think.
JBDSIS Discovery:
!disc-jbdsis.png|thumbnail!
!disc-jbdsis-ea.png|thumbnail!
JBTIS Discovery:
!jbtis-disc.png|thumbnail!
!jbtis-disc-ea.png|thumbnail!
The obvious issue is that the generic connector stays around after you install the EA
components.
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: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png,
disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.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.