[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [corona-dev] Plugin Consolidation - Context Container Services
|
The plugin consolidation was the first, and major, step. Now that they are consolidate, it will be much easier to refactor (rename) the package names.
Think of the consolidated plugin as everything that is needed for the 'container'. There is no need to always require the same multiple plugins.
I did not rename the 'org.eclipse.corona.collaboration' package because Jim was working on migration to ECF v0.9.5. Now that he is done, the classes in that packaged will be moved to 'org.eclipse.corona.event...'.
The same refactoring (renaming) of model container classes could be done as well. Not sure if it makes sense to rename '...model.container...' to '...container.model...'.
-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
Sent: Thursday, January 04, 2007 6:09 AM
To: Corona development
Subject: Re: [corona-dev] Plugin Consolidation - Context Container Services
I find that plugin names after consolidation do not reflect the content.
I mean that plugin name isn't a prefix of packages inside the plugin.
Example: plugin org.eclipse.corona.container contains:
- org.eclipse.corona.collaboration.*
- org.eclipse.corona.container.*
- org.eclipse.corona.model.*
This makes it a bit more difficult to find a plugin which contains
package you are looking for.
Marcin
O'Flynn, Dennis napisał(a):
> Refactoring to consolidate plugins continues. The recent effort has
> focused on server-side context container services.
>
> All plug-ins that provide ContextContainer services have been
> consolidated into: org.eclipse.corona.container.services
>
> All plug-ins that provide ProjectContextContainer services have been
> consolidated into: org.eclipse.corona.container.project.services
>
> Attached is an updated team project set for your convenience.
>
> The contents of this e-mail are intended for the named addressee only.
> It contains information that may be confidential. Unless you are the
> named addressee or an authorized designee, you may not copy or use it,
> or disclose it to anyone else. If you received it in error please
> notify us immediately and then destroy it.
>
>------------------------------------------------------------------------
>
>_______________________________________________
>corona-dev mailing list
>corona-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/corona-dev
>
>
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
