Hi,
To follow this up, the Oomph setup model for developers is now published on the website:
https://www.eclipse.org/papyrus-rt/content/setup/papyrus-rt-developer.setup
And when bug 491815 is resolved, then the setup model will be available in the central Oomph catalogue, so you may want to follow that bug.
Cheers, On 15 April, 2016 at 11:07:39, Christian Damus (give.a.damus@xxxxxxxxx) wrote:
Hi, Team,
With the merge of Gerrit 68572 for
bug
489782, we now have consistent Eclipse tooling configuration
applied across all of the Papyrus-RT source projects, including
- formatter profile
- code clean-up profile
- Java compilation error/warning settings
- Checkstyle
- PDE API Analysis (I think this was already in place for most,
if not all, projects)
The consistency of these settings is managed by the Oomph
Project Configuration tooling. The master configuration is
maintained in the org.eclipse.papyrusrt.umlrt.core
project and is pushed from there to all of the others.
Note that there are, at this point, so very
many Checkstyle warnings that it is probably a good idea to
suppress the annotations in the editor. I do it with as depicted in
the attached graphic for both warnings and infos. Also, you will
only get the Papyrus-RT checkstyle configuration metadata required
to actually do the correct checks if you use Oomph to import at
least the top-level Papyrus-RT project from the in-progress setup
model, available in Gerrit here. But, you probably
don’t have the Checkstyle tooling installed if you didn’t use this
set-up, anyways.
Cheers,
Christian
|
