]
Paul Leacu commented on JBTIS-504:
----------------------------------
[~nickboldt] - Thanks for the review.
* I've corrected the aesthetics by tweeking the composite repository names to be
more consistent.
*
are corrected to contain the JBDS EA plugin.
* The IS plugins have been fully vetted by QE. I had QE do a quick smoke test of the
IS discovery changes last night.
I still need to go through my Jenkins jobs and optimize/ clean up. I could ask QE to go
though another smoke test of what's there now. I think if you're okay with the
current structure we can go live now.
cc: [~ldimaggio] [~mmalina] [~maxandersen] [~akazakov]
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, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png,
JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png,
JBTIS-preview2-EA.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.