[jbosstools-issues] [JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBDS-2669 at 1/6/14 10:56 AM:
-----------------------------------------------------------

+1 to Mickael's idea. Also like Denis' idea of switching to com.redhat.jbdevstudio instead of com.jboss.devstudio, but not sure if we're allowed to use a com.redhat namespace. 

So we would therefore have something like this:

*Option A*

{quote}
com.jboss.jbds.product => *com.jboss.devstudio.product.plugin*
com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package*
{quote}

*Option B*

{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package*
{quote}

Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package", like this?

*Option C*

{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package*
{quote}

[~maxandersen] [~dgolovin] [~mickael_istria] WDYT?
                
      was (Author: nickboldt):
    +1 to Mickael's idea. So we would therefore have one of these two:

*Option A*

{quote}
com.jboss.jbds.product => *com.jboss.devstudio.product.plugin*
com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package*
{quote}

*Option B*

{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package*
{quote}

Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package", like this?

*Option C*

{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package*
{quote}

                  
> rename/refactor JBDS product .feature / plugin / .product to have less confusing names
> --------------------------------------------------------------------------------------
>
>                 Key: JBDS-2669
>                 URL: https://issues.jboss.org/browse/JBDS-2669
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: build, installer, updatesite
>    Affects Versions: 7.0.0.GA
>            Reporter: Nick Boldt
>            Priority: Critical
>             Fix For: 8.0.0.Alpha2
>
>
> We should consider some better names for these artifacts so they collide less and are more obvious which is which.
> 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/com.jboss.jbds.product.feature/feature.properties
> ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site
> 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/com.jboss.jbds.product/plugin.properties and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/com.jboss.jbds.product/META-INF/MANIFEST.MF
> ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true
> 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.jboss.jbds.product
> ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product"

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