| RE: [corona-dev] Corona CVS Repository Updates |
|
> disconnect from existing cvs module
rename and re-add with new Project Name and new CVS Module name I can't see any other solution, I'm
afraid. But I also think that "Losing the history now is probably not
important". Pawel From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Everitt, Glenn Item 3 The plugin ...server.container.project
contains package ...container.manager. Names do not match at all. The Project Name doesn’t match at
all however the plugin name and the package name do match. The Project
Name can be changed (just Refactor | Rename – that’s what I did )
but the cvs module can’t be changed. Should I disconnect from
existing cvs module rename and re-add with new Project Name and new CVS Module
name and lose the cvs history? Losing the history now is probably not
important. What do you think? Glenn From: Comments to plugin refactoring: 1. There are still dependencies on 3rd party packages: Packages "org.apache.xalan" and
"org.apache.xerces" are imported by ...
server.container.project and ...server.repository.team. The package
"org.apache.xalan" can be removed from Import-Packages, but xerces is
used in code by server.repository.team. There is also required package
org.apache.log4j, which is used for logging. 2. Event handling is split among different packages: ...client.collaboration.event and
...client.project.event do not depend on UI in fact. Additionally ...common.project and
...common.collaboration deal only with event routing So they can all be merged to ...event. The new plugin ...event contains: ...client.collaboration.event ...client.project.event ...common.project ...common.collaboration Alternative solutions:
two new plugins: ...event.collaboration and ...event.project
or: ...event.client and ...event.common ...client.collaboration.ui can be renamed
to event.ui 3. The plugin ...server.container.project contains package
...container.manager. Names do not match at all. 4. The plugin ...server.container.common contains only interfaces
IRepository, IRepositoryDescriptor and IProjectListener. They do not concern
container. 5. Plugins "repository.adapter.team" and
"repository.adapter.wp" can be merged to one: ...repository.adapter.default 6. Do we maintain the distinction to client - common? Pawel From: The name ‘org.eclipse.corona’
is the name of the plugin. Within it, there are several java packages:
The objective is to create the root From: org.eclispe.corona - I hope the spelling bug is only in
e-mail. The name seems too generic for me. I would
leave the "core" suffix, so tools are included in core, as for
example core.tools package. Pawel From: Time to resynch again… Glenn and I have refactored
‘org.eclipse.corona.core’ to remove 3rd party library
dependencies. Consequently, we have been able to migrated
‘org.eclipse.org’ form Compuware’s internal CVS repository to
Eclipse’s Corona CVS repository. We also took the opportunity to
establish this as the ‘root’ plugin for all The new plugin is named ‘org.eclispe.corona’.
It is a consolidation of the following plugins:
In addition to committing the new plugin, many plugin
manifests have also been updated. Please discontinue using the ‘core’ and
‘tools’ bundles. These bundles will be deleted from our CVS
repository soon. 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. 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. 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. 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. 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. |