Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus/Papyrus Developer Guide/Release Standard Operating Procedure: Doc"
Line 2: | Line 2: | ||
## level 3 | ## level 3 | ||
## | ## | ||
+ | |||
+ | ## email to papyrus intra | ||
+ | ## email to papyrus dev | ||
+ | |||
+ | Hi everyone ! | ||
+ | Today is build day so if you can refrain yourselves from pushing troublesome features we would greatly appreciate it. | ||
+ | Papyrus Core Team | ||
#Prerequire | #Prerequire |
Revision as of 04:43, 3 June 2015
- Comment
- level 3
- email to papyrus intra
- email to papyrus dev
Hi everyone ! Today is build day so if you can refrain yourselves from pushing troublesome features we would greatly appreciate it. Papyrus Core Team
- Prerequire
- eclipse <version> nightly Eclipse for RCP and RAP Developers
- papyrus git new branch on master
- SimRel
- Clone simrel git repository: by egit or directly with command line: git clone git://git.eclipse.org/gitroot/simrel/org.eclipse.simrel.build.gi
- Import the project inside your eclipse workspace
- Import Eclipse Papyrus Developer Tools
- Papyrus Releng
- Import releng project in workspace
- Update dependencies from Agregation Build Models
- right click on the *.pom.xml and oomph papyrus.setup
- /releng/org.eclipse.papyrus.oomph/setups/papyrus.setup
- /releng/top-pom-dev.xml
- /releng/top-pom-extra-tests.xml
- /releng/top-pom-extras.xml
- /releng/top-pom-main-tests.xml
- /releng/top-pom-main.xml
- /releng/top-pom-rcp.xml
- right click on the *.pom.xml and oomph papyrus.setup