[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mdt-papyrus.dev] Deprecated folder in repository
|
Hello Philippe,
The pointed wiki page is not exactly up to date, but the general process is still the same.
1) Make sure the plugin / feature is accessible in the rmap (would be releng\org.eclipse.mdt.papyrus.releng.buckminster\papyrus-trunk-nightly-tests\build.rmap for the tests on master)
2) Add the plugin / feature to an existing feature that is already in the build (would be features\papyrus-tests-features\org.eclipse.papyrus.tests.feature in this case)
3) Register the test suite(s) in tests\junit\plugins\core\org.eclipse.papyrus.tests
4) Push to the public repository
Camille, could you confirm on the above point 3 that this is indeed the correct thing to do?
In the wiki on point 3, instead of SVN you will have to push the changes to the git repository.
I think that now that we moved to Gerrit the best process would be to push the changes to "refs/for/master" on Gerrit in order to trigger the reviewing process. According to Camille previous message you won't be able to push a new branch to the repo directly.
Hope this helps!
Laurent
-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de ROLAND, PHILIPPE
Envoyé : lundi 7 avril 2014 15:13
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Deprecated folder in repository
Hi Laurent,
Of course. I'm a bit busy right now, but I'll get to it in a few days.
Just one question : Is there something in particular I should do to add test plugins beyond the process described over in the developer guide (https://wiki.eclipse.org/Papyrus_Developer_Guide/Build_Process#How_to_add_a_plugin_and_or_a_set_of_plugins_in_the_build_process_of_Papyrus) ? the guide still mentions SVN so I'm not 100% sure that it's fully up-to-date.
Regards,
Philippe
-----Original Message-----
From: mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] On Behalf Of WOUTERS Laurent
Sent: Friday, April 04, 2014 4:57 PM
To: Papyrus Project list
Subject: Re: [mdt-papyrus.dev] Deprecated folder in repository
Hello all,
We have removed the "deprecated" folder in the master branch. You will see that a single tag named "last/<bundleID>" for each of the removed bundle has been created.
You can see the list the relevant tag with the command:
git tag -l last/*
You can also see the content of the tagged commits with:
git show last/<bundleID>
We still need to investigate what to do with the existing plugins and features that are not in the build (see list below).
For example, Philippe, would it be possible for you to add the org.eclipse.papyrus.team plugins to a build (main, extras, other)?
Regards,
Laurent
---- List of features and plugins not built org.eclipse.papyrus.alf.sdk-feature
org.eclipse.papyrus.customization.fragment.feature
org.eclipse.papyrus.design.profile.feature
org.eclipse.papyrus.extra.layout.feature
org.eclipse.papyrus.infra.queries.feature
org.eclipse.papyrus.team.feature
org.eclipse.papyrus.adl4eclipse.profile
org.eclipse.papyrus.adl4eclipsetool
org.eclipse.papyrus.adl4eclipsetool.assistant
org.eclipse.papyrus.codegen
org.eclipse.papyrus.def
org.eclipse.papyrus.design.profile.architecture
org.eclipse.papyrus.design.profile.architecture.edit
org.eclipse.papyrus.design.profile.architecture.editor
org.eclipse.papyrus.dev.java.utils
org.eclipse.papyrus.dev.view.services.edit.request
org.eclipse.papyrus.developer.profile
org.eclipse.papyrus.diagramdev.modelexplorer
org.eclipse.papyrus.diagramtemplate.doc
org.eclipse.papyrus.doc
org.eclipse.papyrus.documentation.plugin
org.eclipse.papyrus.documentation.plugin.edit
org.eclipse.papyrus.documentation.plugin.editor
org.eclipse.papyrus.domaincodegen.ui
org.eclipse.papyrus.domaincontextcodegen
org.eclipse.papyrus.domaincontextcodegen.edit
org.eclipse.papyrus.domaincontextcodegen.editor
org.eclipse.papyrus.editor.perspectiveconfiguration
org.eclipse.papyrus.emf.facet.custom.doc
org.eclipse.papyrus.emf.facet.custom.metamodel.editor
org.eclipse.papyrus.emf.facet.custom.metamodel.editor.doc
org.eclipse.papyrus.emf.facet.doc
org.eclipse.papyrus.facade
org.eclipse.papyrus.facade.codegen
org.eclipse.papyrus.facade.definition.editor
org.eclipse.papyrus.facade.edit
org.eclipse.papyrus.facade.editor
org.eclipse.papyrus.facade.utils
org.eclipse.papyrus.gmf.editPoliciesstates
org.eclipse.papyrus.gmf.editpartview
org.eclipse.papyrus.gmf.figureview
org.eclipse.papyrus.gmfgenextension
org.eclipse.papyrus.infra.core.serviceregistry
org.eclipse.papyrus.infra.core.serviceregistry.edit
org.eclipse.papyrus.infra.core.serviceregistry.editor
org.eclipse.papyrus.infra.core.serviceregistry.test
org.eclipse.papyrus.infra.emf.editor
org.eclipse.papyrus.infra.emf.embeddededitor
org.eclipse.papyrus.infra.emf.facet.queries
org.eclipse.papyrus.infra.emf.newchild
org.eclipse.papyrus.infra.extendedtypes.editor
org.eclipse.papyrus.infra.extendedtypes.elementtypeview
org.eclipse.papyrus.infra.gmfdiag.css.debug
org.eclipse.papyrus.infra.nattable.doc
org.eclipse.papyrus.java.template
org.eclipse.papyrus.layers.dev.ui
org.eclipse.papyrus.layers.documentation
org.eclipse.papyrus.layers.integrationtests
org.eclipse.papyrus.layers.stackmodel.tests
org.eclipse.papyrus.layout
org.eclipse.papyrus.layout.algorithms.gridAlgorithm
org.eclipse.papyrus.layout.algorithms.horizontalAlgorithm
org.eclipse.papyrus.layout.algorithms.horizontalSymmetryAlgorithm
org.eclipse.papyrus.layout.algorithms.horizontalTreeAlgorithm
org.eclipse.papyrus.layout.algorithms.radialAlgorithm
org.eclipse.papyrus.layout.algorithms.springAlgorithm
org.eclipse.papyrus.layout.algorithms.treeAlgorithm
org.eclipse.papyrus.layout.algorithms.verticalAlgorithm
org.eclipse.papyrus.layout.algorithms.verticalSymmetryAlgorithm
org.eclipse.papyrus.layout.subeditor.gmf
org.eclipse.papyrus.operation.editor.xtext
org.eclipse.papyrus.operation.editor.xtext.ui
org.eclipse.papyrus.osgi.profile
org.eclipse.papyrus.parsers
org.eclipse.papyrus.robotml.help
org.eclipse.papyrus.spem2.profile
org.eclipse.papyrus.sysml.sysmloveruml.codegen
org.eclipse.papyrus.team.collaborative.controlmode
org.eclipse.papyrus.team.collaborative.core
org.eclipse.papyrus.team.collaborative.strategy
org.eclipse.papyrus.team.collaborative.svn
org.eclipse.papyrus.team.svn
org.eclipse.papyrus.uml.compare.ui
org.eclipse.papyrus.uml.diagram.domain
org.eclipse.papyrus.uml.diagram.emftree
org.eclipse.papyrus.uml.ui.perspectiveconfiguration
-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de ROLAND, PHILIPPE Envoyé : vendredi 4 avril 2014 15:38 À : Papyrus Project list Objet : Re: [mdt-papyrus.dev] Deprecated folder in repository
Hi all,
It seems that I'm a bit late to the discussion, but for what it's worth I agree completely, having been confused by the presence of obsolete code in the past.
I also agree with having a dedicated folder outside of /plugins + separate branches for developer code; I'm currently working on plugins org.eclipse.papyrus.team.collaborative.*, which probably did come out a bit early, and can move them to their own branch and subfolder if we go ahead with this.
Regards,
Philippe
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
