[jbosstools-issues] [JBoss JIRA] (JBDS-2874) Support updating JBDS via BYOE (update site) w/o having to update product too

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBDS-2874 at 1/16/14 12:24 PM:
------------------------------------------------------------

The old way - if you asked to update JBDS Core Features (BYOE) you would be forced to update the Branded Product feature too:
-----
!update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png!
-----

Now, with a change like this in site/*.p2.inf (for JBDS 8.0.0.Alpha1)...

{code:title=site/com.jboss.jbds.p2.inf}
# JBDS-2874 this allows us to update a JBDS product via BYOE feature w/o updating the product (package definition) itself
requires.1.namespace = org.eclipse.equinox.p2.iu
requires.1.name = com.jboss.jbds.product.feature.feature.group
requires.1.range = [8.0.0, 9.0.0)
{code}

we get this:

*Help > About > Installation Details > Installation History BEFORE UPDATE*
!update-BYOE-without-updating-product_BEFORE.png!

-----

*Help > About > Installation Details > Installation History AFTER UPDATE*
!update-BYOE-without-updating-product_result.png!

For JBDS 8.0.0.Alpha2, the code is slightly different due to refactorings done in JBDS-2669:

{code:title=site/com.jboss.devstudio.core.p2.inf}
# JBDS-2874 this allows us to update a JBDS product via BYOE feature w/o updating the product (package definition) itself
requires.1.namespace = org.eclipse.equinox.p2.iu
requires.1.name = com.jboss.devstudio.core.feature.feature.group
requires.1.range = [8.0.0, 9.0.0)
{code}


                
      was (Author: nickboldt):
    The old way - if you asked to update JBDS Core Features (BYOE) you would be forced to update the Branded Product feature too:

!update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png!

Now, with a change like this in site/*.p2.inf (for JBDS 8.0.0.Alpha1)...

{code:title=site/com.jboss.jbds.p2.inf}
# JBDS-2874 this allows us to update a JBDS product via BYOE feature w/o updating the product (package definition) itself
requires.1.namespace = org.eclipse.equinox.p2.iu
requires.1.name = com.jboss.jbds.product.feature.feature.group
requires.1.range = [8.0.0, 9.0.0)
{code}

we get this:

*Help > About > Installation Details > Installation History BEFORE UPDATE*
!update-BYOE-without-updating-product_BEFORE.png!

*Help > About > Installation Details > Installation History AFTER UPDATE*
!update-BYOE-without-updating-product_result.png!

For JBDS 8.0.0.Alpha2, the code is slightly different due to refactorings done in JBDS-2669:

{code:title=site/com.jboss.devstudio.core.p2.inf}
# JBDS-2874 this allows us to update a JBDS product via BYOE feature w/o updating the product (package definition) itself
requires.1.namespace = org.eclipse.equinox.p2.iu
requires.1.name = com.jboss.devstudio.core.feature.feature.group
requires.1.range = [8.0.0, 9.0.0)
{code}


                  
> Support updating JBDS via BYOE (update site) w/o having to update product too
> -----------------------------------------------------------------------------
>
>                 Key: JBDS-2874
>                 URL: https://issues.jboss.org/browse/JBDS-2874
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Nick Boldt
>         Attachments: update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png, update-BYOE-without-updating-product_BEFORE.png, update-BYOE-without-updating-product_result.png
>
>
> I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both. 
> Do we want this?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira