Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [technology-pmc] eclipse scout and jshint

In this particular case, the comment was added for the express purpose of ensuring that end users do not see certain validation messages when jshint is installed. It’s a pretty clear-cut case of a works with dependency. The project is integrating with jshint, but jshint is not required for full functionality, so works with.


- Konstantin



From: Gunnar Wagenknecht
Sent: Monday, October 12, 2015 11:49 AM
To: Konstantin Komissarchik
Cc: Matthias.Zimmermann@xxxxxxxxxxxxxxxx;Technology PMC
Subject: Re: [technology-pmc] eclipse scout and jshint



> Am 12.10.2015 um 20:39 schrieb Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx>:


> The issue is that this in the code that’s delivered to end users.


So is all code at Eclipse.


I still don't see a need for a CQ. All that comment does is configure a code scanning/analysis plug-in in some IDE.


What if that _javascript_ file would contain:


/* vi: tabstop=4



Does that require a works-with CQ for vim?





Back to the top