CVS/SVN structure is not restricted - you can set it up any way you'd like.
However, if you're a Modeling project, it's advised that you use a
layout like this, so that other Modelers can easily find your code in
the usual places.
/svnroot/modeling/org.eclipse.emf.foo/
/plugins/
/features/
/tests/
/doc/
Traditionally, we enforced that you had two folders in parallel:
/cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.foo/
/cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.foo.releng/
But with Athena that's no longer required - you can choose to use this
folder instead:
/svnroot/modeling/org.eclipse.emf.foo/releng/
Once you have everything in SVN (or CVS, doesn't matter which), you can
start creating your /releng/ or /org.eclipse.emf.foo.releng/ folder
contents.
When I'm creating a new releng project, I copy from an existing working
one, and update paths/strings to match the new project.
Here's the one I generally use:
http://anonsvn.jboss.org/repos/jbosstools/trunk/jmx/releng/
You might want to copy from another Modeling project - GMT MoDisco:
http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/
http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/releng/trunk/org.eclipse.gmt.modisco.releng/maps/infrastructure.map
You will have to create your map file manually, pointing at each and
every feature/plugin you will be building. But, once that's done, you
can use `build.steps=map2psf,...` in your build.properties file to
(re)generate .psf files (Project Set Files) for your developers so they
too can fetch your sources easily. Publish a link to those files in your
wiki, and they can download them and import them into Eclipse to easily
grab all your source projects. *Very handy!*
Christian Krause wrote:
Dear Nick Boldt,
I'm Christian Krause and I'm currently setting up a new EMFT component
called EMF Henshin. At this point I have to decide what the module
structure of our SVN will look like. We would like to use an automated
build system and for this purpose I was browsing the Athena wiki and
parts of your releng blog. I do not understand yet how the whole thing
works, but for now it would help me already if you could give me a hint
on how our module layout should look like for this. I would guess we
would have to modules in our SVN:
org.eclipse.emf.henshin
org.eclipse.emf.henshin.releng
where the former contains the plug-ins, features and docs, and the
latter contains the build files. Is that correct?
I will try find my way through the documentation. Anyway, if you can
point me to other resources than I mentioned already, I would appreciate it.
Thanks for your time and best regards,
Christian
-------- Original-Nachricht --------
Betreff: Re: Project info for EMF Henshin
Datum: Thu, 15 Oct 2009 14:49:13 +0200
Von: Ed Merks <ed.me...@itemis.de>
An: Christian Krause <christian.kra...@cwi.nl>
CC: Bernd Kolb <bernd.k...@sap.com>, Anne Jacko <e...@eclipse.org>, EMF
Tiger <emftr...@cs.tu-berlin.de>, Nick Boldt <nickbo...@gmail.com>
Christian,
I'm not sure SVN is a great choice, but then I'm not sure it's a bad one
either...
Other folks are generally using this structure, i.e., don't use one
module per plugin but rather nest them into a structure like this:
You might want to talk to Nick Boldt about how you'll be doing your builds.
Cheers,
Ed
Christian Krause wrote:
Thanks, Ed. One more question about the SVN setup: what should the
namespace of the plug-ins be? I would guess org.eclipse.emf.henshin.*.
So as a list of initial modules I would enter something like:
org.eclipse.emf.henshin.model
org.eclipse.emf.henshin.common
org.eclipse.emf.henshin.interpreter
Does that sound ok to you?
Cheers,
Christian
Christian,
Comments below.
Christian Krause wrote:
Dear Ed and Bernd,
I'm glad that our project was approved (the only issue was that we
had to change the name from Tiger to Henshin).
I am now filling out the form for the "New Project Provisioning
Request". I need to enter some project info there. In particular
they ask for "New Eclipse Project:" and "Host Top-Level Project:".
I'm tempted to write "Eclipse Modeling Framework Henshin" as project
name.
That sounds fine.
For the host top-level there is already a default value set to
"technology".
It should be Modeling. In particular it will be a subproject of the
Eclipse Modeling Framework Technology project (EMFT) which in turn is
a subproject of Modeling.
Can I leave that as it is and is the name ok like that?
Cheers,
Christian
--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
