[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:all-tabpanel ]

Nick Boldt updated JBTIS-504:
-----------------------------
    Attachment: ea-in-non-ea.png


Paul: can you purge the extraneous plugins from your 4.3.0.Alpha2 development folder? Or do you need me to do that? Surely you only have 1 or 2 plugins linked from the directory.xml files, so there's no need for a dozen nearly-identical copies of the same plugin in what should be a folder containing a SINGLE release. 

In this folder we see... 

* an extraneous directory.xml file not linked from anywhere, which refs an old version of your plugin: B425 (from Sept 17)
* several old copies of the earlyaccess plugin (from B419 - B430) - yet there's a different EA folder with only 3 builds: B436 - B438: http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/plugins/
* several old copies of the non-ea plugin from B419 - B438

Then there's the problems in your EA site:

* it doesn't contain both your plugins, only the EA one... so pointing a user at that site's directory.xml will only resolve the EA content, not the combination of EA and regular content. Seeing both at the same time paints a more realistic picture of what an end-user will see when the whole thing's live.

And finally, I have to ask... why do you have two copies of the directory.xml files?

* http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-integration-stack-directory.xml and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-directory.xml are indentical so why produce both?

* http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-integration-stack-directory.xml and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml are NOT identical, and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml lists the same JBT plugin TWICE, rather than listing the core and EA plugins (there ought to be 4 different plugins listed).

Here's what a valid site looks like:

http://download.jboss.org/jbosstools/mars/stable/updates/discovery.earlyaccess/4.3.0.Final/jbosstools-directory.xml

or

https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/devstudio-directory.xml

Hope that helps!
!ea-in-non-ea.png!


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