[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [gmf-dev] Refactoring of the IBM gmf runtime contribution...
|
Hi Fred,
it's not true that there is no "real" extra value. I already mentioned
two major advantages. Another one is the possibility to branch and tag
within constant time, i.e. regardless how many items the repository
contains. I've seen myself waiting for tagging a medium sized project
over an ISDN connection more than 30 minutes. Also, subversion keeps
track of all changes that are made to the working copy after the last
synch with the repository where with CVS you always need to connect the
server.
I worked with CVS myself for about 10 years and switched to subversion
one year ago due to its advantages. The concepts are very similar to
CVS, so I think people that are trained with CVS should be able to make
the transition within really short time.
I don't know, in which respect the current tooling (like releng) makes
use of CVS but assume it mainly consists of checking out (tagged)
versions. I can not imagine that it is much effort to optionally use
subversion in place of CVS.
Two years ago I worked in a company that still used RCS - they also
avoided to learn other tools for no real extra value -- I hope you don't
mind me beeing a bit polemic ;-)
I definitely can live with CVS but would appreciate if we could make the
transition to subversion.
Best regards,
Henrik
Frederic Plante wrote:
>
> I disagree with this initiative.
>
> We already have ~ 15 people trained on CVS and used to its workflows.
> We should avoid having to learn other tools for no real extra value.
> Also, the releng tool is assuming CVS, seems like we have much higher
> priority tasks than making this work.
>
> Thanks
>
> - Fred
>
> _________________________________
> Frédéric Plante
> Rational Software, IBM Software Group
> 770 Palladium Drive, Ottawa, ON, Canada
> tel: (613) 591-7034
>
>
>
>
> *"Richard Gronback" <Richard.Gronback@xxxxxxxxxxx>*
> Sent by: gmf-dev-bounces@xxxxxxxxxxx
>
> 08/25/2005 04:19 PM
> Please respond to
> "GMF Project developer discussions."
>
>
>
> To
> "GMF Project developer discussions." <gmf-dev@xxxxxxxxxxx>
> cc
>
> Subject
> RE: [gmf-dev] Refactoring of the IBM gmf runtime contribution...
>
>
>
>
>
>
>
>
>
> Hi All,
>
> I inquired about Subversion again, and it seems there is a chance we can
> pioneer the effort. The only difficulty I see is in the build/releng
> tooling, which currently works with CVS but which is supposed to work
> with other providers.
>
> The sooner we can switch the better, so unless anyone has an objection,
> I will pursue this with Denis.
>
> Thanks,
> Rich
>
> -----Original Message-----
> From: gmf-dev-bounces@xxxxxxxxxxx [mailto:gmf-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Henrik Rentz-Reichert
> Sent: Wednesday, August 24, 2005 7:20 PM
> To: GMF Project developer discussions.
> Subject: Re: [gmf-dev] Refactoring of the IBM gmf runtime
> contribution...
>
> Hi all,
>
> speaking of refactoring (including source file renaming and folder
> structure changes) -- subversion (SVN) keeps track of those changes very
> nicely and has other advantages over CVS (like atomic commits to mention
> one further). There also is subversion team support available for
> eclipse (subclipse). Would it be feasible (and compliant with the
> eclipse web site policy) to use SVN rather than CVS?
>
> Regards,
>
> Henrik
>
> Richard Gronback wrote:
>
> >Hi Steve,
> >
> >I'm fine with it being a single shot check-in with the refactored
> packages. No need to have a duplication under the 'contributions'
> directory (if I understand the question correctly). Of course, those
> aimed at EMFT should probably not be checked into the GMF /plugins
> module, so perhaps it's best to put them under 'contributions' for now?
> So, either way you propose is fine, as long as we maintain a record of
> the refactoring (which the script itself represents).
> >
> >Be aware that the naming convention for tests is
> org.eclipse.gmf.tests.* and not as you have listed below with
> org.eclipse.gmf.*.tests. A similar naming scheme applies to examples,
> where they should be in org.eclipse.gmf.examples.* packages.
> >
> >>From the conventions document:
> >
> >org.eclipse.<subproject>.tests.<component>[.*] - tests
> >org.eclipse.<subproject>.examples.<component>[.*] - examples
> >
> >Also, note that tests are located in a /tests module within our CVS
> structure and currently reside in a single plug-in. There is no
> /examples module currently in CVS, so can you please create one when you
> commit them (and place them there)?
> >
> >I'll modify the feature projects and map files for the build when this
> is done. It doesn't appear there is a conflict with the existing
> runtime packages, so the current build will not break (which is nice).
> >
> >Anyone else see something we've missed?
> >
> >Thanks!
> >- Rich
> >
> >
> >-----Original Message-----
> >From: gmf-dev-bounces@xxxxxxxxxxx on behalf of Steven Shaw
> >Sent: Wed 8/24/2005 4:39 PM
> >To: gmf-dev@xxxxxxxxxxx
> >Subject: [gmf-dev] Refactoring of the IBM gmf runtime contribution...
> >
> >Hello all,
> >
> >We're are planning to refactor the naming of the IBM GMF contribution
> to
> >conform to the org.eclipse.gmf.runtime naming convention. Some
> exceptions
> >apply for plug-ins that will be submitted to the EMF technology
> project.
> >This will affect all plug-ins in the
> >dev.eclipse.org:/home/technology/org.eclipse.gmf/contributions/ibm-gmf-
> runtime
> >repository.
> >
> >We could move the runtime components into the main repository directory
> at
> >the same time (pending feedback - Rich?). The current plan would be to
> do
> >the refactoring inside the contribution directory and move it in a
> second
> >stage.
> >
> >This refactoring is scheduled for this weekend or early next week.
> Please
> >make sure to deliver any outstanding activities that you wish to be
> >refactored by that timeframe. If you have a problem with this
> schedule,
> >please respond and we'll try to accommodate.
> >
> >Will will provide a script after our delivery for clients that we do
> not
> >have visibility of that will perform the refactoring changes in their
> >code.
> >
> >Here is a current list of plug-ins and the proposed name changes
> >(extracted from our script):
> >
> >q(com.ibm.xtools.aurora.doclet) => q(org.eclipse.gmf.runtime.doclet),
> >q(com.ibm.xtools.common.core) =>
> q(org.eclipse.gmf.runtime.common.core),
> >q(com.ibm.xtools.common.core.examples.service) =>
> >q(org.eclipse.gmf.runtime.common.examples.service),
> >q(com.ibm.xtools.common.core.provider) =>
> >q(org.eclipse.gmf.runtime.common.core.provider),
> >q(com.ibm.xtools.common.core.tests) =>
> >q(org.eclipse.gmf.runtime.common.core.tests),
> >q(com.ibm.xtools.common.ui) => q(org.eclipse.gmf.runtime.common.ui),
> >q(com.ibm.xtools.common.ui.action) =>
> >q(org.eclipse.gmf.runtime.common.ui.action),
> >q(com.ibm.xtools.common.ui.action.ide) =>
> >q(org.eclipse.gmf.runtime.common.ui.action.ide),
> >q(com.ibm.xtools.common.ui.pathvariables.ide) =>
> >q(org.eclipse.gmf.runtime.common.ui.pathvariables.ide),
> >q(com.ibm.xtools.common.ui.printing) =>
> >q(org.eclipse.gmf.runtime.common.ui.printing),
> >q(com.ibm.xtools.common.ui.printing.win32) =>
> >q(org.eclipse.gmf.runtime.common.ui.printing.win32),
> >q(com.ibm.xtools.common.ui.services) =>
> >q(org.eclipse.gmf.runtime.common.ui.services),
> >q(com.ibm.xtools.common.ui.services.action) =>
> >q(org.eclipse.gmf.runtime.common.ui.services.action),
> >q(com.ibm.xtools.common.ui.services.action.tests) =>
> >q(org.eclipse.gmf.runtime.common.ui.services.action.tests),
> >q(com.ibm.xtools.common.ui.services.dnd) =>
> >q(org.eclipse.gmf.runtime.common.ui.services.dnd),
> >q(com.ibm.xtools.common.ui.services.dnd.ide) =>
> >q(org.eclipse.gmf.runtime.common.ui.services.dnd.ide),
> >q(com.ibm.xtools.common.ui.services.properties) =>
> >q(org.eclipse.gmf.runtime.common.ui.services.properties),
> >q(com.ibm.xtools.common.ui.tests) =>
> >q(org.eclipse.gmf.runtime.common.ui.tests),
> >q(com.ibm.xtools.diagram) => q(org.eclipse.gmf.runtime.diagram.core),
> >q(com.ibm.xtools.diagram.ui) => q(org.eclipse.gmf.runtime.diagram.ui),
> >q(com.ibm.xtools.diagram.ui.actions) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.actions),
> >q(com.ibm.xtools.diagram.ui.dnd) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.dnd),
> >q(com.ibm.xtools.diagram.ui.examples.geoshapes) =>
> >q(org.eclipse.gmf.runtime.diagram.examples.geoshapes),
> >q(com.ibm.xtools.diagram.ui.examples.logic) =>
> >q(org.eclipse.gmf.runtime.diagram.examples.logic),
> >q(com.ibm.xtools.diagram.ui.examples.logic.semantic) =>
> >q(org.eclipse.gmf.runtime.diagram.examples.logic.model),
> >q(com.ibm.xtools.diagram.ui.examples.logic.semantic.edit) =>
> >q(org.eclipse.gmf.runtime.diagram.examples.logic.model.edit),
> >q(com.ibm.xtools.diagram.ui.examples.services.decorator) =>
> >q(org.eclipse.gmf.runtime.diagram.examples.decorator),
> >q(com.ibm.xtools.diagram.ui.examples.services.layout) =>
> >q(org.eclipse.gmf.runtime.diagram.examples.layout),
> >q(com.ibm.xtools.diagram.ui.geoshapes) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.geoshapes),
> >q(com.ibm.xtools.diagram.ui.printing) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.printing),
> >q(com.ibm.xtools.diagram.ui.printing.render) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.printing.render),
> >q(com.ibm.xtools.diagram.ui.properties) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.properties),
> >q(com.ibm.xtools.diagram.ui.providers) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.providers),
> >q(com.ibm.xtools.diagram.ui.providers.ide) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.providers.ide),
> >q(com.ibm.xtools.diagram.ui.render) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.render),
> >q(com.ibm.xtools.diagram.ui.resources.editor) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.resources.editor),
> >q(com.ibm.xtools.diagram.ui.resources.editor.ide) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.resources.editor.ide),
> >q(com.ibm.xtools.diagram.ui.tests) =>
> >q(org.eclipse.gmf.runtime.diagram.ui.tests),
> >q(com.ibm.xtools.draw2d.ui) => q(org.eclipse.gmf.runtime.draw2d.ui),
> >q(com.ibm.xtools.draw2d.ui.render) =>
> >q(org.eclipse.gmf.runtime.draw2d.ui.render),
> >q(com.ibm.xtools.draw2d.ui.render.tests) =>
> >q(org.eclipse.gmf.runtime.draw2d.ui.render.tests),
> >q(com.ibm.xtools.draw2d.ui.tests) =>
> >q(org.eclipse.gmf.runtime.draw2d.ui.tests),
> >q(com.ibm.xtools.gef.ui) => q(org.eclipse.gmf.runtime.gef.ui),
> >q(com.ibm.xtools.gef.ui.tests) =>
> q(org.eclipse.gmf.runtime.gef.ui.tests),
> >q(com.ibm.xtools.gmf.doc.isv) => q(org.eclipse.gmf.runtime.doc.isv),
> >q(com.ibm.xtools.gmf.source) => q(org.eclipse.gmf.runtime.source),
> >q(com.ibm.xtools.gmf.ui.pde.examples) =>
> >q(org.eclipse.gmf.runtime.gmf.ui.pde.examples),
> >q(com.ibm.xtools.emf.msl.commands) =>
> >q(org.eclipse.gmf.runtime.emf.commands.core),
> >q(com.ibm.xtools.emf.msl.commands.tests) =>
> >q(org.eclipse.gmf.runtime.emf.commands.core.tests),
> >q(com.ibm.xtools.emf.msl.core) => q(org.eclipse.gmf.runtime.emf.core),
> >q(com.ibm.xtools.emf.msl.core.tests) =>
> >q(org.eclipse.gmf.runtime.emf.core.tests),
> >q(com.ibm.xtools.emf.msl.example.pde.general.ui) =>
> >q(org.eclipse.gmf.runtime.emf.examples.general),
> >q(com.ibm.xtools.emf.msl.ocl) =>
> q(org.eclipse.gmf.runtime.emf.ocl.core),
> >q(com.ibm.xtools.emf.msl.ocl.tests) =>
> >q(org.eclipse.gmf.runtime.emf.ocl.core.tests),
> >q(com.ibm.xtools.emf.msl.ui) => q(org.eclipse.gmf.runtime.emf.ui),
> >q(com.ibm.xtools.emf.msl.ui.properties) =>
> >q(org.eclipse.gmf.runtime.emf.properties.ui),
> >q(com.ibm.xtools.emf.msl.ui.tests) =>
> >q(org.eclipse.gmf.runtime.emf.ui.tests),
> >q(com.ibm.xtools.emf.msl.ui.properties.tests) =>
> >q(org.eclipse.gmf.runtime.emf.properties.ui.tests),
> >q(com.ibm.xtools.emf.type) => q(org.eclipse.gmf.runtime.emf.type.core),
> >q(com.ibm.xtools.emf.type.tests) =>
> >q(org.eclipse.gmf.runtime.emf.type.ui.tests),
> >q(com.ibm.xtools.emf.type.ui) =>
> q(org.eclipse.gmf.runtime.emf.type.ui),
> >q(com.ibm.xtools.emf.ui.providers.transfer) =>
> >q(org.eclipse.gmf.runtime.emf.transfer.ui.providers),
> >q(com.ibm.xtools.emf.clipboard) => q(org.eclipse.emf.copypaste),
> >q(com.ibm.xtools.emf.clipboard.example.pde.copypaste.ui) =>
> >q(org.eclipse.emf.copypaste.examples),
> >q(com.ibm.xtools.emf.metamodel.example.pde.rmplibrary) =>
> >q(org.eclipse.emf.examples.library),
> >q(com.ibm.xtools.emf.metamodel.example.pde.rmplibrary.edit) =>
> >q(org.eclipse.emf.examples.library.edit),
> >q(com.ibm.xtools.emf.metamodel.example.pde.rmplibrary.editor) =>
> >q(org.eclipse.emf.examples.library.editor),
> >q(com.ibm.xtools.emf.ocl) => q(org.eclipse.emf.ocl),
> >q(com.ibm.xtools.emf.ocl.tests) => q(org.eclipse.emf.ocl.tests),
> >q(com.ibm.xtools.emf.ocl.example.pde.interpreter.ui) =>
> >q(org.eclipse.emf.ocl.examples.interpreter),
> >q(com.ibm.xtools.emf.ocl.example.pde.query.ui) =>
> >q(org.eclipse.emf.ocl.examples.query),
> >q(com.ibm.xtools.emf.ocl.example.pde.validation.core) =>
> >q(org.eclipse.emf.ocl.examples.validation),
> >q(com.ibm.xtools.emf.query) => q(org.eclipse.emf.query),
> >q(com.ibm.xtools.emf.query.tests) => q(org.eclipse.emf.query.tests),
> >q(com.ibm.xtools.emf.query.example.pde.statements.ui) =>
> >q(org.eclipse.emf.query.examples.statements),
> >q(com.ibm.xtools.emf.query.ocl) => q(org.eclipse.emf.query.ocl),
> >q(com.ibm.xtools.emf.query.ocl.tests) =>
> >q(org.eclipse.emf.query.ocl.tests),
> >q(com.ibm.xtools.emf.validation) => q(org.eclipse.emf.validation),
> >q(com.ibm.xtools.emf.validation.ui) =>
> q(org.eclipse.emf.validation.ui),
> >q(com.ibm.xtools.emf.validation.ui.ide) =>
> >q(org.eclipse.emf.validation.ui.ide),
> >q(com.ibm.xtools.emf.validation.ocl) =>
> q(org.eclipse.emf.validation.ocl),
> >q(com.ibm.xtools.emf.validation.tests) =>
> >q(org.eclipse.emf.validation.tests),
> >q(com.ibm.xtools.emf.validation.example.pde.adapter.ui) =>
> >q(org.eclipse.emf.validation.examples.adapter),
> >q(com.ibm.xtools.emf.validation.example.pde.general.ui) =>
> >q(org.eclipse.emf.validation.examples)
> >
> >Regards,
> >
> >-Steve
> >_______________________________________________
> >gmf-dev mailing list
> >gmf-dev@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/gmf-dev
> >
> >
> >
> >-----------------------------------------------------------------------
> -
> >
> >_______________________________________________
> >gmf-dev mailing list
> >gmf-dev@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/gmf-dev
> >
> >
>
> --
> .............................
>
> Dr. Henrik Rentz-Reichert
>
> Hafnerstr. 1
> 78476 Allensbach
>
> fon 07533 / 93 42 43
> fon 07533 / 93 42 42 (priv.)
> fax 07533 / 93 42 44
>
> mailto://hrr@xxxxxxxxx
>
> _______________________________________________
> gmf-dev mailing list
> gmf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/gmf-dev
> _______________________________________________
> gmf-dev mailing list
> gmf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/gmf-dev
>
>------------------------------------------------------------------------
>
>_______________________________________________
>gmf-dev mailing list
>gmf-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/gmf-dev
>
>
--
.............................
Dr. Henrik Rentz-Reichert
Hafnerstr. 1
78476 Allensbach
fon 07533 / 93 42 43
fon 07533 / 93 42 42 (priv.)
fax 07533 / 93 42 44
mailto://hrr@xxxxxxxxx
