[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=13116701#comment-13116701 ] 

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

Perhaps this is a dumb question, but I just realized that the sites you linked to above are /development/ URLs, not /staging/ ones.

I would have thought you'd present staging URLs first for review, then push that content to /development/ ONCE IT WAS VETTED. 

Am I crazy to think that you shouldn't just push things to /development/ without first QEing them? Or did I miss the QE signoff email which preceded the release from /staging/ to /development/ ? (It's possible -- I get a lot of email.) :D

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.



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