[jbosstools-issues] [JBoss JIRA] (JBIDE-12469) Creation of org.jboss.tools.common.core component and associated feature

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-12469:
----------------------------------------

In general, we expect plugin org.jboss.tools.common.blah to contain classes that have for package org.jboss.tools.common.blah*. If we rename org.jboss.tools.common to org.jboss.tools.common.core, will this kind of convention be respected?
What about simply keeping org.jboss.tools.common as bundle, and extract from here the not-that-common stuff to create some other org.jboss.tools.common.ui ?
I fear splitting the bundle without renaming packages will lead to some ambiguity on which bundle provides which package.
                
> Creation of org.jboss.tools.common.core component and associated feature
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-12469
>                 URL: https://issues.jboss.org/browse/JBIDE-12469
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: common/jst/core
>    Affects Versions: 4.0.0.M1
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.0.0.M1
>
>         Attachments: JBIDE-12469.scope2.txt
>
>
> As part of the refactor of the "common" component, this jira will track the addition of a new plugin. Some complain that common already has too many plugins, so this new plugin's creation will follow a careful process to ensure the new plugin has a purpose, is not repetitive, and helps move the component into a cleaner direction rather than a messier one. 
> The process (in progress) is being formed over at https://community.jboss.org/wiki/DevelopingForJBossTools

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