[jbosstools-issues] [JBoss JIRA] (JBIDE-14363) Creation of 'core' component in base

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-14363:
-------------------------------------

The problem is that what's in common.core now is not necessarily all fit for a true core. THere's plenty of utilities that are, but also lots of classes that aren't. 

I honestly really like the idea of fresh starts with people consciously modifying classes for re-use and putting them somewhere new and shiny. All code must be 100% javadoc'd, api stable, a very very strong set of requirements... test cases for every single class. 

It's possible to do this within common, but, if we're going to do all that work, add test cases for every class, separate it into plugins based on deps, etc,  why not just give it a new component name also? I think it will definitely help keep things separate. 
                
> Creation of 'core' component in base
> ------------------------------------
>
>                 Key: JBIDE-14363
>                 URL: https://issues.jboss.org/browse/JBIDE-14363
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: common/jst/core
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Rob Stryker
>            Assignee: Max Rydahl Andersen
>             Fix For: 4.1.0.Beta1
>
>
> The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements:
> 1) Only code designed for re-use can live there
> 2) Only fully and properly java-doc'd code can live there
> 3) Only code for use by TWO OR MORE components can live there. 
> 4) Addition of dependencies for this component will be strictly regulated
> 5) Code must be properly tested and have tests cases demonstrating it. 
> 6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example:
> {code}
>    org.jboss.tools.core.platform
>    org.jboss.tools.core.platform.ui
>    org.jboss.tools.core.wtp
>    org.jboss.tools.core.wtp.ui
> {code}
> Bundles such as these would require test bundles, as well as features that keep them separate. 
> {code}
>     org.jboss.tools.core.platform.feature
>     org.jboss.tools.core.wtp.feature
> {code}

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