Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] [Quality] Checkstyle... coming soon
Hi, Ernesto,

Yes, AFAIK, Checkstyle only works on Java, although I haven’t looked into that.  Céline is leading the Checkstyle effort here, so perhaps she could better answer that.  Xtend has some very non-Java syntax, and I don’t know what Checkstyle would do with it.

However, as far as generated sources are concerned, this Gerrit patch does exclude everything in src-gen (EMF and Xtext generated stuff) and xtend-gen (Xtend generated stuff).

There was a discussion a while back about applying the formatting profile to the repository.  The Gerrit contribution I referenced below does include the formatting profile, so that much is already covered.  I will leave it to the team to decide when and how you want to format the repository.

cW

On 7 April, 2016 at 14:22:13, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:

Great! Thanks.

My understanding is that Checkstyle is only for Java, is that correct? I'm asking because we are using Xtend quite a bit. Ideally we would have something for that as well. Furthermore, we may want to configure Checkstyle to ignore the xtend-gen folders, as suggested here https://sdqweb.ipd.kit.edu/wiki/Palladio_Coding_Conventions#Handle_Xtend_Generated_Files.

Also, I suppose we'll have to apply the common format to all sources, right? I recall Celine saying that we should use the Papyrus format. If so, where can we get it? Is there a way to apply it to the whole project rather than having to do each file individually?



On Thu, Apr 7, 2016 at 2:02 PM Christian Damus <give.a.damus@xxxxxxxxx> wrote:
Hi, Team,

The Checkstyle configuration of the Papyrus-RT source projects is a part of the overall Oomph preference management configuration proposal in Gerrit:


This builds on the other contribution (68693) for an Oomph setup model, as the setup model has to create the Checkstyle configuration file in the workspace metadata area to connect the projects to the Papyrus-RT checkstyle configuration maintained in git.

I welcome review of this contribution.

Thanks,

Christian

On 7 April, 2016 at 08:33:07, Céline JANSSENS (celine.janssens@xxxxxxxxxxx) wrote:

Hi all,

For your information, a checkstyle is under study and will be deployed soon on the project.

This is the next step in the quality of our project.
The purpose will be to have an homogeneous code, and to give to the contributors a baseline of what is expected as a standard for the project.

The final goal would be to have a set of tools (Sonar, Checkstyle, RCPTT, Junit, ...) working together to give us a clear overview of the quality progression of the Papyrus RT project.
And see if we are moving in the right direction.

Best regards

Céline
--

 
  Céline JANSSENS
 Software Engineer
+33 (0)2 44 47 23 23
  Mail : cej@xxxxxxxxxxx
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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