Bugzilla – Full Text Bug Listing
| Summary: | Move GEF3D to GIT | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Jens Von Pilgrim <developer> |
| Component: | Gef3d | Assignee: | Project Inbox <gef3d.misc-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | milesparker |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Just wondering where we are with this? Oh duh, we were waiting for Miles to respond. :) (In reply to comment #0) > and convert the current projects to a structure similar to the one used in the > AMP project. That is, the following tree would be created: > > + draw3d > + features > + org.eclipse.draw3d.feature > + plugins > + org.eclipse.draw3d > + org.eclipse.draw3d.geometry > + org.eclipse.draw3d.graphics3d > + org.eclipse.draw3d.lwjgl > + org.eclipse.draw3d.jogl > + org.eclipse.draw3d.ui > + tests > + org.eclipse.draw3d.test > + gef3d > + features > + org.eclipse.gef3d.feature.examples > + org.eclipse.gef3d.feature > + plugins > + org.eclipse.gef3d > + org.eclipse.gef3d.ext > + org.eclipse.gef3d.ext.emf > + org.eclipse.gef3d.gmf > + org.eclipse.gef3d.gmf.editors > + org.eclipse.gef3d.gmf.graph.viewer > + org.eclipse.gef3d.gmf.map.editor > + examples > + org.eclipse.gef3d.examples.ecore > + org.eclipse.gef3d.examples.graph > + org.eclipse.gef3d.examples.uml2 > + doc > + plugins > + org.eclipse.gef3d.doc > + releng > + org.eclipse.gef3d.releng I'd suggest not following in my footsteps here. :) To keep things simple I'd suggest keeping the structure with just the top-level as plugins,features,etc.. and gef3d and draw3d in the same dirs. Adds unnecesary complexity unless there is a good reason to do this. > > I have already moved the x3d plugin into folder tags/archive in the svn > repository, as we do no longer maintain that project and it's not necessary to > migrate it. > There are some projects I'm not sure whether we'd need them: > org.eclipse.gef3d.feature.sdk -- this feature contains doc and source projects > org.eclipse.gef3d.source -- source plugin > org.eclipse.gef3d.updatesite -- probably outdated update site > org.eclipse.gef3d.feature.test -- only contains the draw3d test plugin. Do we > need a draw3d.feature.test instead? > > Miles, how do you build the sdk and source features? Do you have any > suggestions regarding the new structure? Do we need additional projects or > would you suggest to remove or merge some projects? We just need the releng dir. Let's copy over feature.sdk only so that we can get any meta-data we need from there. The source isn't needed, nor updatesite. For test, you probably jsut need one test feature. > I'm not sure whether we'd need the log history, that is, do we need a complete > migration or is a simple import enough? As described on > http://wiki.eclipse.org/Git/Migrating_to_Git , the migration could be done by > the webmaster or ourselves. Miles, what do you think is best? I'd do it through webmaster if they have time. You could just re-assign to them, but there is enough stuff to potentially get wrong there that I don't feel comfortable actually doing the migration itself. OK then, I would suggest the following main folders:
- features
- plugins
- tests
- examples
- releng
Since features and releng are to be re-created for the nightly build anyway, I would suggest to not migrate them and only migrate the plugins as follows:
+ plugins
+ org.eclipse.draw3d
+ org.eclipse.draw3d.geometry
+ org.eclipse.draw3d.graphics3d
+ org.eclipse.draw3d.jogl
+ org.eclipse.draw3d.lwjgl
+ org.eclipse.draw3d.ui
+ org.eclipse.gef3d
+ org.eclipse.gef3d.doc
+ org.eclipse.gef3d.ext
+ org.eclipse.gef3d.ext.emf
+ org.eclipse.gef3d.gmf
+ tests
+ org.eclipse.draw3d.test
+ examples
+ org.eclipse.gef3d.examples.ecore
+ org.eclipse.gef3d.examples.graph
+ org.eclipse.gef3d.examples.uml2
Jens
requested migration to git, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=359798 |
In order to simplify the configuration of a nightly-build system etc., Miles has proposed to move the GEF3D repository to GIT. For that, I would have to file a request to the Eclipse webmasters, settings up a new GIT repository and migrate the existing code. Before filing that request, I would like to discuss some open issues: migration timeline: July 2011 ? mapping of current code to new Git repos: I would suggest to use one GIT repository git.eclipse.org/gitroot/gef3d/org.eclipse.gef3d.git and convert the current projects to a structure similar to the one used in the AMP project. That is, the following tree would be created: + draw3d + features + org.eclipse.draw3d.feature + plugins + org.eclipse.draw3d + org.eclipse.draw3d.geometry + org.eclipse.draw3d.graphics3d + org.eclipse.draw3d.lwjgl + org.eclipse.draw3d.jogl + org.eclipse.draw3d.ui + tests + org.eclipse.draw3d.test + gef3d + features + org.eclipse.gef3d.feature.examples + org.eclipse.gef3d.feature + plugins + org.eclipse.gef3d + org.eclipse.gef3d.ext + org.eclipse.gef3d.ext.emf + org.eclipse.gef3d.gmf + org.eclipse.gef3d.gmf.editors + org.eclipse.gef3d.gmf.graph.viewer + org.eclipse.gef3d.gmf.map.editor + examples + org.eclipse.gef3d.examples.ecore + org.eclipse.gef3d.examples.graph + org.eclipse.gef3d.examples.uml2 + doc + plugins + org.eclipse.gef3d.doc + releng + org.eclipse.gef3d.releng I have already moved the x3d plugin into folder tags/archive in the svn repository, as we do no longer maintain that project and it's not necessary to migrate it. There are some projects I'm not sure whether we'd need them: org.eclipse.gef3d.feature.sdk -- this feature contains doc and source projects org.eclipse.gef3d.source -- source plugin org.eclipse.gef3d.updatesite -- probably outdated update site org.eclipse.gef3d.feature.test -- only contains the draw3d test plugin. Do we need a draw3d.feature.test instead? Miles, how do you build the sdk and source features? Do you have any suggestions regarding the new structure? Do we need additional projects or would you suggest to remove or merge some projects? I'm not sure whether we'd need the log history, that is, do we need a complete migration or is a simple import enough? As described on http://wiki.eclipse.org/Git/Migrating_to_Git , the migration could be done by the webmaster or ourselves. Miles, what do you think is best? Cheers, Jens