[jbosstools-dev] Request for comment on introduction of org.jboss.tools.common.core

[Nick Boldt]

+1 to the idea. We're moving from 3.x to 4.0, so now is a perfect time 
to get some long-overdue refactoring done. Additional comments in the JIRA.

Thanks for adding more wikidoc on how to (and when to) add new plugins! 
Had a quick scan and it looks pretty decent.

Cheers,

Nick

On 08/23/2012 06:19 AM, Rob Stryker wrote:
> Hi all:
>
> Since the 'common' component is our lowest level component, which almost
> all of jbt has a dependency on, this issue affects basically everyone here.
>
> As was mentioned before, for all the reasons common needs to be split,
> the beginning step is the creation of a new plugin. To avoid adding yet
> another junk plugin with no benefit, I've drafted a new process for
> additions of new plugins:
> https://community.jboss.org/wiki/ApprovalProcessForAddingAPluginAndOrFeatureToAnExistingComponent
>
>
> The new plugin will possibly be named org.jboss.tools.common.core, and
> will hold about 60-70% of what is currently in org.jboss.tools.common.
> Strong efforts will be made to make sure all consumers have no issues,
> that package names aren't changed, that class names aren't changed, and
> that everything continues to go smoothly, but, since things don't always
> go 100%, it is very important we all stay aware of this issue.
>
> The jira requesting approvals for this issue is here:
> https://issues.jboss.org/browse/JBIDE-12469
>
> This is just a first step. Assuming this split goes well, the next steps
> will be (up to discussion of course) to continue organizing the common
> module in a safe way with clear boundaries between plugins and features.
>
> Let's not get too far ahead of ourself, though. For now, I'd like
> everyone (if they have time) to read and comment on the above jira,
> which simply creates org.jboss.tools.common.core and moves all non-ui
> classes from o.j.t.common into o.j.t.common.core.
>
> If *anyone* sees anything wrong in the plan, PLEASE mention it. I'd also
> like to mention that voting yes now does not mean you agree to the patch
> (as there isn't one yet). It just means you agree to the plan.
>
> Thanks again.
>
> - Rob Stryker, troublemaker

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com