Community
Participate
Working Groups
During migration TopCased to Eclipse.org, new plug-ins were created to factorize common behaviors between C generation and reversing, and to isolate much more these components. Besides, some plug-in name suffixes were kept to simplify this migration and some plug-ins could be shared between other components. So, plugins should be renamed and moved in a better location. Here is the current tree: - org.eclipse.umlgen.gen.c /plugins /org.eclipse.umlgen.c.common /org.eclipse.umlgen.gen.c /org.eclipse.umlgen.gen.c.builder /org.eclipse.umlgen.gen.c.properties /org.eclipse.umlgen.gen.c.ui - org.eclipse.umlgen.gen.java /plugins /org.eclipse.umlgen.gen.java /org.eclipse.umlgen.gen.java.ui - org.eclipse.umlgen.gen.rtsj /plugins /org.eclipse.umlgen.dsl.asl /org.eclipse.umlgen.dsl.asl.edit /org.eclipse.umlgen.dsl.asl.editor /org.eclipse.umlgen.dsl.eth /org.eclipse.umlgen.dsl.eth.edit /org.eclipse.umlgen.dsl.eth.editor /org.eclipse.umlgen.gen.autojava /org.eclipse.umlgen.gen.autojava.launcher /org.eclipse.umlgen.gen.autojava.thirdparty - org.eclipse.umlgen.reverse.c /org.eclipse.umlgen.reverse.c /org.eclipse.umlgen.reverse.c.sync.util /org.eclipse.umlgen.reverse.c.ui - releng I'd suggest: - to rename "org.eclipse.umlgen.gen.autojava.thirdparty" to "org.eclipse.umlgen.rtsj.profile". Indeed, this contains only the RTSJ UML Profile and the built libraries ("annotations" and "framework" for the generated code) is intended to be accessed as a build artifact from org.eclipse.umlgen.gen.rtsj/libraries - to relocate the plugins from this way: - org.eclipse.umlgen.dsl /plugins /org.eclipse.umlgen.dsl.asl /org.eclipse.umlgen.dsl.asl.edit /org.eclipse.umlgen.dsl.asl.editor /org.eclipse.umlgen.dsl.eth /org.eclipse.umlgen.dsl.eth.edit /org.eclipse.umlgen.dsl.eth.editor - org.eclipse.umlgen.rtsj /plugins /org.eclipse.umlgen.rtsj.profile - org.eclipse.umlgen.c /plugins /org.eclipse.umlgen.c.common - org.eclipse.umlgen.gen.c /org.eclipse.umlgen.gen.c /org.eclipse.umlgen.gen.c.builder /org.eclipse.umlgen.gen.c.properties /org.eclipse.umlgen.gen.c.ui - org.eclipse.umlgen.gen.java /plugins /org.eclipse.umlgen.gen.java /org.eclipse.umlgen.gen.java.ui - org.eclipse.umlgen.gen.rtsj /plugins /org.eclipse.umlgen.gen.autojava /org.eclipse.umlgen.gen.autojava.launcher - org.eclipse.umlgen.reverse.c /org.eclipse.umlgen.reverse.c /org.eclipse.umlgen.reverse.c.sync.util /org.eclipse.umlgen.reverse.c.ui
An other way is to sort per technology to generate/consume: - org.eclipse.umlgen /plugins /org.eclipse.umlgen.dsl.asl /org.eclipse.umlgen.dsl.asl.edit /org.eclipse.umlgen.dsl.asl.editor /org.eclipse.umlgen.dsl.eth /org.eclipse.umlgen.dsl.eth.edit /org.eclipse.umlgen.dsl.eth.editor - org.eclipse.umlgen.java /plugins /org.eclipse.umlgen.gen.java /org.eclipse.umlgen.gen.java.ui - org.eclipse.umlgen.rtsj /plugins /org.eclipse.umlgen.rtsj.profile /org.eclipse.umlgen.gen.autojava /org.eclipse.umlgen.gen.autojava.launcher (/org.eclipse.umlgen.gen.rtsj) (/org.eclipse.umlgen.gen.rtsj.launcher) - org.eclipse.umlgen.c /plugins /org.eclipse.umlgen.c.common /org.eclipse.umlgen.gen.c /org.eclipse.umlgen.gen.c.builder /org.eclipse.umlgen.gen.c.properties /org.eclipse.umlgen.gen.c.ui /org.eclipse.umlgen.reverse.c /org.eclipse.umlgen.reverse.c.sync.util /org.eclipse.umlgen.reverse.c.ui
I have a preference for this last cutting up (https://bugs.eclipse.org/bugs/show_bug.cgi?id=438144#c1). It allows : - to group each business issue in a single place (generators, reverse engines, user interfaces, profiles, designs... around a same language/technology to address). - to group cross-technologies software in a single place too (org.eclipse.umlgen folder). - to identify distinctly and easily some leaders on each group . Please, give me your opinion before adopting this. As this refactoring may have some important impacts, it would be reluctant to wait that the current developments and reviews should be committed in Git before applying this change.
(In reply to Cedric Notot from comment #2) > I have a preference for this last cutting up > (https://bugs.eclipse.org/bugs/show_bug.cgi?id=438144#c1). > > It allows : > - to group each business issue in a single place (generators, reverse > engines, user interfaces, profiles, designs... around a same > language/technology to address). > - to group cross-technologies software in a single place too > (org.eclipse.umlgen folder). > - to identify distinctly and easily some leaders on each group . > > Please, give me your opinion before adopting this. > > As this refactoring may have some important impacts, it would be reluctant > to wait that the current developments and reviews should be committed in Git > before applying this change. I meant 'relevant', not 'reluctant' of course.
Have a look on it: http://www.patrick-wied.at/blog/rename-files-and-folders-with-git, to correctly make the renaming and move of the plugins in Git.
Waiting for the best organization and consensus, I'm just going to rename the org.eclipse.umlgen.gen.autojava.thirdparty plugin (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=471422)
