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

Nick Boldt edited comment on JBTIS-504 at 10/8/15 10:47 PM:
------------------------------------------------------------

Aesthetically, comparing these two:

{quote}
"JBoss Developer Studio 9.x - Integration Stack" - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/compositeArtifacts.xml
"JBoss Tools Integration Stack 4.3 - Development Milestone"  - http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/compositeArtifacts.xml
{quote}

I see divergent title conventions. This is non-blocking, but sloppy. 

* Why 9.x but 4.3 (not 4.3.x) ? 
* Why is only one of them a "Development Milestone" ? 
* Why change the ordering from "9.x - Integration Stack" to "Integration Stack 4.3" ?
* And shouldn't that be "*Red Hat* JBoss Developer Studio", to adhere to correct branding rules?

----

Functionally speaking:

https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/devstudio-directory.xml and https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/devstudio-directory.xml contain the same 3 plugins. Why build both when the contents are the same? Did you mean to include the JBDS EA plugin in there too?

http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml contains only 3 of the 4 required plugins, as did 9.0.0.Alpha2/devstudio-directory.xml above. Why not include all 4?

http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-directory.xml contains all 4! Hooray! We have a fully-functional site for testing, which will show all the JBT, JBTEA , JBTIS, and JBTISEA content in a single Central view.

* [^JBTIS-preview1.png] & 
* [^JBTIS-preview2-EA.png]

Successfully installed everything.

But for JBDS IS preview:

* [^JBDSIS-preview1.png] &
* [^JBDSIS-preview2-EA.png]

... sadly there's no Arquillian available when Early Access is enabled, because the JBDS EA plugin is missing from the URL you provided as the testing site. :(

So, this is only a problem w/ the test site, not the eventual JBDS site into which you'll add your plugins. But it will certainly confuse QE and break install-grinder tests. 

Can you produce a discovery site w/ all 4 JBDS plugins in it?






was (Author: nickboldt):
Aesthetically, comparing these two:

{quote}
"JBoss Developer Studio 9.x - Integration Stack" - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/compositeArtifacts.xml
"JBoss Tools Integration Stack 4.3 - Development Milestone"  - http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/compositeArtifacts.xml
{quote}

I see divergent title conventions. This is non-blocking, but sloppy. 

* Why 9.x but 4.3 (not 4.3.x) ? 
* Why is only one of them a "Development Milestone" ? 
* Why change the ordering from "9.x - Integration Stack" to "Integration Stack 4.3" ?
* And shouldn't that be "*Red Hat* JBoss Developer Studio", to adhere to correct branding rules?

----

Functionally speaking:

https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/devstudio-directory.xml and https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/devstudio-directory.xml contain the same 3 plugins. Why build both when the contents are the same? Did you mean to include the JBDS EA plugin in there too?

http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml contains only 3 of the 4 required plugins, as did 9.0.0.Alpha2/devstudio-directory.xml above. Why not include all 4?

http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-directory.xml contains all 4! Hooray! We have a fully-functional site for testing, which will show all the JBT, JBTEA , JBTIS, and JBTISEA content in a single Central view.

[^JBTIS-preview1.png] & [^JBTIS-preview2-EA.png]

Successfully installed everything.

But for JBDS IS preview:

[^JBDSIS-preview1.png]
[^JBDSIS-preview2-EA.png]

... sadly there's no Arquillian available when Early Access is enabled, because the JBDS EA plugin is missing from the URL you provided as the testing site. :(

So, this is only a problem w/ the test site, not the eventual JBDS site into which you'll add your plugins. But it will certainly confuse QE and break install-grinder tests. 

Can you produce a discovery site w/ all 4 JBDS plugins in it?





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