Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Source project configuration
I just tried saving a modification and got a warning/error message (attached). What does it mean? What happens if a "save participant" failed?

Screenshot 2016-04-15 11.37.36.png





On Fri, Apr 15, 2016 at 11:33 AM Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:
Great! Thanks Christian.

A silly question: the formatting is applied on save only, right? In particular, it is not applied by the Oomph setup or the build, correct? If so, the only way of getting rid of the checkstyle warnings is to touch the files, right?

As we discussed previously Checkstyle only deals with Java and not with Xtend, but Xtend does support formats. Do you know if there is a way to configure Xtend2 project settings/preferences? I haven't found any.

Also, I noticed that the introduction of Checkstyle results in some errors in Codegen. I'll take a look and check the solutions in.

As for the Oomph setup, now that we have the dependencies sorted out, is there anything else missing or can we merge it? I know that the EMF and Xtext generation is still not there, but we could push those later and in the meantime have the .setup file available for download, no?



On Fri, Apr 15, 2016 at 11:07 AM 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


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

Back to the top