[
https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBTIS-504:
-----------------------------
Attachment: is-in-dev.png
is-in-dev_JBDS.png
Thanks to new script doc'd in JBIDE-20803, and some fancypants synching between
/staging/ and /development/ (using Beyond Compare), I've copied the files I updated in
/staging/ (and tested locally to verify) into these places:
/media/TOOLS-ssh/9.0/staging/updates/discovery.central/4.3.0.CR1a ->
/media/TOOLS-ssh/9.0/development/updates/discovery.central/4.3.0.CR1
/media/TOOLS-ssh/9.0/staging/updates/discovery.earlyaccess/4.3.0.CR1a ->
/media/TOOLS-ssh/9.0/development/updates/discovery.earlyaccess/4.3.0.CR1
/media/JBDS-ssh/9.0/staging/updates/discovery.central/9.0.0.CR1a ->
/media/JBDS-ssh/9.0/development/updates/discovery.central/9.0.0.CR1
/media/JBDS-ssh/9.0/staging/updates/discovery.earlyaccess/9.0.0.CR1a ->
/media/JBDS-ssh/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1
So, now in JBDS 9 CR1 and JBT 4.3 CR1, you can see this right out of the box (no -D flag
overrides needed):
!is-in-dev_JBDS.png!
!is-in-dev.png!
\o/ \m/ \o/ \m/
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)