[jbosstools-issues] [JBoss JIRA] (JBDS-2134) Extras site contains JBDS feature

Nick Boldt (JIRA) jira-events at lists.jboss.org
Fri May 11 14:31:19 EDT 2012


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

Nick Boldt edited comment on JBDS-2134 at 5/11/12 2:30 PM:
-----------------------------------------------------------

Things to fix, if we like my suggestion:

move ~/trunk/devstudio.jboss.com/updates/5.0/staging/extras/composite*.xml to ../central/core/composite*.xml
revert ~/trunk/devstudio.jboss.com/updates/5.0/staging/extras/composite*.xml to previous state (only the one site, without ref to ../ site)

{code}
r9243 | nickboldt | 2012-05-07 14:03:46 -0400 (Mon, 07 May 2012) | 2 lines
Changed paths:
   M devstudio.jboss.com/updates/5.0/staging/extras/compositeArtifacts.xml
   M devstudio.jboss.com/updates/5.0/staging/extras/compositeContent.xml

JBDS-2122 add ref to ../ to resolve upstream deps on JBDS Core and JBDS TP (eg., to find mylyn, egit, etc.)
{code}

New sites would therefore be:

* https://devstudio.jboss.com/updates/5.0/staging/central/core/
* https://devstudio.jboss.com/updates/5.0/staging/central/soa-tooling/
then after GA:
* https://devstudio.jboss.com/updates/5.0/central/core/
* https://devstudio.jboss.com/updates/5.0/central/soa-tooling/

----

Should prolly do the same for JBT, too - create a new site for use with Central, revert the old site:

{code}
r40879 | nickboldt | 2012-05-09 13:28:44 -0400 (Wed, 09 May 2012) | 2 lines
Changed paths:
   M download.jboss.org/jbosstools/updates/development/indigo/compositeArtifacts.xml
   M download.jboss.org/jbosstools/updates/development/indigo/compositeContent.xml

in addition to having the site provided via p2 metadata, link to http://download.jboss.org/jbosstools/updates/indigo/SR2/ via the composite site http://download.jboss.org/jbosstools/updates/development/indigo/
{code}

new sites would be something like:
 * http://download.jboss.org/jbosstools/updates/development/indigo/central/core/
 * http://download.jboss.org/jbosstools/updates/development/indigo/central/soa-tooling/
then after GA:
 * http://download.jboss.org/jbosstools/updates/stable/indigo/central/core/
 * http://download.jboss.org/jbosstools/updates/stable/indigo/central/soa-tooling/

                
      was (Author: nickboldt):
    Things to fix, if we like my suggestion:

move ~/trunk/devstudio.jboss.com/updates/5.0/staging/extras/composite*.xml to ../central/core/composite*.xml
revert ~/trunk/devstudio.jboss.com/updates/5.0/staging/extras/composite*.xml to previous state (only the one site, without ref to ../ site)

{code}
r9243 | nickboldt | 2012-05-07 14:03:46 -0400 (Mon, 07 May 2012) | 2 lines
Changed paths:
   M devstudio.jboss.com/updates/5.0/staging/extras/compositeArtifacts.xml
   M devstudio.jboss.com/updates/5.0/staging/extras/compositeContent.xml

JBDS-2122 add ref to ../ to resolve upstream deps on JBDS Core and JBDS TP (eg., to find mylyn, egit, etc.)
{code}

New sites would therefore be:

* https://devstudio.jboss.com/updates/5.0/staging/central/core/
* https://devstudio.jboss.com/updates/5.0/staging/central/soa-tooling/
then after GA:
* https://devstudio.jboss.com/updates/5.0/central/core/
* https://devstudio.jboss.com/updates/5.0/central/soa-tooling/

----

Should prolly do the same for JBT, too - create a new site for use with Central, revert the old site:

{code}
r40879 | nickboldt | 2012-05-09 13:28:44 -0400 (Wed, 09 May 2012) | 2 lines
Changed paths:
   M download.jboss.org/jbosstools/updates/development/indigo/compositeArtifacts.xml
   M download.jboss.org/jbosstools/updates/development/indigo/compositeContent.xml
{code}

in addition to having the site provided via p2 metadata, link to http://download.jboss.org/jbosstools/updates/indigo/SR2/ via the composite site http://download.jboss.org/jbosstools/updates/development/indigo/

new sites would be something like:
 * http://download.jboss.org/jbosstools/updates/development/indigo/central/core/
 * http://download.jboss.org/jbosstools/updates/development/indigo/central/soa-tooling/
then after GA:
 * http://download.jboss.org/jbosstools/updates/stable/indigo/central/core/
 * http://download.jboss.org/jbosstools/updates/stable/indigo/central/soa-tooling/

                  
> Extras site contains JBDS feature
> ---------------------------------
>
>                 Key: JBDS-2134
>                 URL: https://issues.jboss.org/browse/JBDS-2134
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: updatesite
>    Affects Versions: 5.0.0.Beta3
>         Environment: http://devstudio.jboss.com/updates/5.0/staging/extras/
>            Reporter: Vlado Pakan
>            Assignee: Nick Boldt
>             Fix For: 5.0.0.CR1
>
>         Attachments: installdialog.png
>
>
> Update site http://devstudio.jboss.com/updates/5.0/staging/extras/ contains also JBDS feature.
> !installdialog.png!

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

        


More information about the jbosstools-issues mailing list