[jbosstools-issues] [JBoss JIRA] (JBDS-1959) publish JBDS version of Central directory.xml file into JBDS core update site

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBDS-1959 at 1/22/12 11:54 PM:
------------------------------------------------------------

Steps (a) - (e) are done. 

I added the 6 JBDS SOA Tooling features (BPEL, Drools/Guvnor, ESB, jBPM, Modeshape, Teiid, plus an extra feature including the 3 runtime detectors in a single entry. Also commented out jRebel and GWT, as suggested above.

If we wanted, we could use different icons for the various pieces of functionality; for now, they're all set up to use the JBDS redball.

Next respin of JBDS Core aggregate site will include new JBDS central discovery plugin. 

https://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-5.0_trunk.updatesite/ >=1640

--

Once done, to enable it instead of the JBoss Tools one, run JBDS like this:

./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/product/devstudio-directory.xml

-- 

Then we can worry about changing (f) in JBDS installer and documenting new publishing process in (g).

!JBDS1959-snap.png!



                
      was (Author: nickboldt):
    Steps a - e are done. 

I added the 6 JBDS SOA Tooling features (BPEL, Drools/Guvnor, ESB, jBPM, Modeshape, Teiid, plus an extra feature including the 3 runtime detectors in a single entry. Also commented out jRebel and GWT, as suggested above.

If we wanted, we could use different icons for the various pieces of functionality; for now, they're all set up to use the JBDS redball.

!JBDS1959-snap.png!

Next respin of JBDS Core aggregate site will include new JBDS central discovery plugin. 

https://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-5.0_trunk.updatesite/ >=1640

--

Once done, to enable it instead of the JBoss Tools one, run JBDS like this:

./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/product/devstudio-directory.xml

-- 

Then we can worry about changing (f) in JBDS installer and documenting new publishing process in (g).



                  
> publish JBDS version of Central directory.xml file into JBDS core update site
> -----------------------------------------------------------------------------
>
>                 Key: JBDS-1959
>                 URL: https://issues.jboss.org/browse/JBDS-1959
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: central, updatesite
>    Affects Versions: 5.0.0.M5
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 5.0.0.Beta1
>
>         Attachments: JBDS1959-snap.png
>
>
> Like we have for JBT, we need that:
> a) the update site for JBDS core contain a devstudio-directory.xml file: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/product/devstudio-directory.xml
> b) it be linked from the site's index.html page (to support mirrors)
> c) the directory file link to a different discovery plugin, available only in JBDS: ~/trunk/product/plugins/com.jboss.jbds.central.discovery
> d) this plugin must be wrapped w/ a feature and published onto the update site: ~/trunk/product/features/com.jboss.jbds.central.discovery.feature
> e) readme files explaining how to access the different versions of the file for testing purposes: ~/trunk/product/README.Central.{localhost,milestone}.testing.txt
> --
> f) tweak jbdevstudio.ini to load the correct URL for the site:
>   ... -vmargs -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/5.0/staging/devstudio-directory.xml
> g) update the releng guide publishing instructions / email template for this new tweak to record README/testing information for QE; also ensure that the discovery jar's plugin.xml points at the correct URL for downloading features, eg., http://devstudio.jboss.com/updates/5.0/soa-tooling/ vs. http://devstudio.jboss.com/updates/5.0/staging/soa-tooling/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira