Skip to content
This repository has been archived by the owner on Jul 8, 2019. It is now read-only.

Run SonarTsPlugin AND SonarSource/SonarTS #182

Open
guillaume317 opened this issue Nov 20, 2017 · 5 comments
Open

Run SonarTsPlugin AND SonarSource/SonarTS #182

guillaume317 opened this issue Nov 20, 2017 · 5 comments

Comments

@guillaume317
Copy link

guillaume317 commented Nov 20, 2017

Hi Team,

Is it possible to run together on a same instance your plugin and the new SonarSource/SonarTS one ?
Both plugins have the same name.
When I try to rename it, another problem occurs with the following message:
"java.lang.IllegalArgumentException: Multiple entries with same key: ts=TypeScript and ts=TypeScript "

Thanks

@nixel2007
Copy link

No, you can't. Even if you handle the same key issue, you'll face the same extension error - only one plugin can be registred to analyze ts extension. To make work both plugins, this plugin must be re-written to "custom rules plugin" api, extending the official one.

@philipooo
Copy link

Would be nice if we could use this plugin side by side. I love the way how tslint-output can be imported with the help of this plugin. The original SonarQube plugin has no way doing this.

@ClaudioLelis
Copy link

Now in SonarQube 7.4 seems like SonarTSPlugin does not working. Is that true? I uninstalled the SonarSource/SonarTS and even not worked.

@philipooo
Copy link

Btw SonarSource/SonarTS now supports import of tslint output.

@ClaudioLelis
Copy link

Yes, but I can not automatically run TSLint through sonar-scanner, and can not manage TSLint core and custom rules, right?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants