[jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115568#comment-13115568 ] 

Nick Boldt commented on JBTIS-504:
----------------------------------

[~pleacu] Please document here which URLs will contain your latest plugin jars. Will they be Alpha2? Alpha3? /staging/ ? /snapshots/ ?

Also, please ensure that the site's plugins/ folder only contains 2 plugins, not 18. 

eg., http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-stack/discovery/4.3.0.Alpha2/plugins/ (good)
http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha2/plugins/ (bad - too many plugins!)



> 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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)