* The plugin is for SQ 5.4+ ; what is the next LTS version ? And is there an expected release date ?
* The code highlighting mechanism is still done using the CodeColorizerFormat class. We had a (very quick) look at the new Highlighting classes, but were unable to understand how to "glue" everything and migrate the existing classes. Is there a "Highlighting for dummies" somewhere ?
* OpenEdge codebases are usually quite large (several millions SLOC). This means that in several locations (the Code tab being the most annoying one), it's not possible see all directories and files. Is there a way to control the number of lines displayed here ?
* The roadmap (at http://www.sonarqube.org/roadmap/ ) mentions a cartography feature. Is it still planned ?
* A technical question which may not be related to SQ at all, but I don't know enough of Maven and the sonar-packaging plugin to be sure : I'm getting a different JAR file for the plugin when I compile this multi-module project with Maven 3.0 and Maven 3.3. Using Maven 3.0 leads to the right result, while Maven 3.3 generates an invalid JAR file as it adds too many dependencies in the META-INF/lib folder. Does that spark an idea to anybody ? Otherwise, I'll try to report the problem with more information.
And finally, I'd like to congratulate the entire team for this fantastic tool !
* OpenEdge codebases are usually quite large (several millions SLOC). This means that in several locations (the Code tab being the most annoying one), it's not possible see all directories and files. Is there a way to control the number of lines displayed here ?Would be interesting to give some precise figures as well as your hardware specs so that we can investigate the performance issue.
* The code highlighting mechanism is still done using the CodeColorizerFormat class. We had a (very quick) look at the new Highlighting classes, but were unable to understand how to "glue" everything and migrate the existing classes. Is there a "Highlighting for dummies" somewhere ?You can have a look at the latest API usage here: https://github.com/SonarSource/sonarqube/blob/master/plugins/sonar-xoo-plugin/src/main/java/org/sonar/xoo/lang/SyntaxHighlightingSensor.java This API will become the official one in 5.6.
Thanks, will have a look !
* OpenEdge codebases are usually quite large (several millions SLOC). This means that in several locations (the Code tab being the most annoying one), it's not possible see all directories and files. Is there a way to control the number of lines displayed here ?Would be interesting to give some precise figures as well as your hardware specs so that we can investigate the performance issue.
My sentence wasn’t really clear ; in fact, it’s not a performance problem, but just a problem to see all entries. The following example (only a few lines in the screenshot) contains 250 directories approximately, but only the first 100 entries are displayed.
Browsing code and issues for a specific directory is difficult to achieve as I don’t think there’s a way to filter by directory. If I use the filter “interface”, only files matching “interface” are displayed, but not the directory src/maia/ba/interface (second line of the screenshot) and src/maia/dbdc/interface (which is not even listed in the UI due to the 100 items limitation).
Another example is in the issues filter :
Only the first 15 directories are displayed, when there might be a lot more. To my mind, there’s no need to display every entry (as it will just make the filter completely unreadable and useless), but the ability to change the number of items would be a nice to have !
* The roadmap (at http://www.sonarqube.org/roadmap/ ) mentions a cartography feature. Is it still planned ?Not in 2016 AFAIK.
:-(
* A technical question which may not be related to SQ at all, but I don't know enough of Maven and the sonar-packaging plugin to be sure : I'm getting a different JAR file for the plugin when I compile this multi-module project with Maven 3.0 and Maven 3.3. Using Maven 3.0 leads to the right result, while Maven 3.3 generates an invalid JAR file as it adds too many dependencies in the META-INF/lib folder. Does that spark an idea to anybody ? Otherwise, I'll try to report the problem with more information.I'm interested in a detailed report since I'm not aware of such issue.
In case you have time, you can reproduce the problem by cloning the Git repo and executing mvn package with Maven 3.0.5 and 3.3.9. Or let me know if you want me to create a simple test case, that might be easier to debug. The difference is here :
$ jar tf oe-mvn3.0/openedge-plugin/target/sonar-openedge-plugin-1.9.1.jar | grep /lib/
META-INF/lib/
META-INF/lib/commons-lang-2.6.jar
META-INF/lib/slf4j-api-1.7.19.jar
META-INF/lib/openedge-checks-shaded-1.3.4.jar
META-INF/lib/commons-io-2.4.jar
$ jar tf oe-mvn3.3/openedge-plugin/target/sonar-openedge-plugin-1.9.1.jar | grep /lib/
META-INF/lib/
META-INF/lib/antlr-2.7.7.jar
META-INF/lib/commons-lang-2.6.jar
META-INF/lib/slf4j-api-1.7.19.jar
META-INF/lib/guava-19.0.jar
META-INF/lib/openedge-checks-shaded-1.3.4.jar
META-INF/lib/listing-parser-1.3.6.jar
META-INF/lib/proparse-1.0.6.jar
META-INF/lib/database-parser-1.1.10.jar
META-INF/lib/antlr4-runtime-4.5.2-1.jar
META-INF/lib/javax.inject-1.jar
META-INF/lib/guice-4.0.jar
META-INF/lib/commons-io-2.4.jar
META-INF/lib/openedge-checks-1.3.4.jar
META-INF/lib/aopalliance-1.0.jar
In short, the openedge-checks-shaded module (which relocates antlr in the .api. package) depends on openedge-checks, and generates a dependency-reduced-pom.xml file. Then openedge-plugin then depends on openedge-checks-shaded, and thus openedge-checks dependencies shouldn’t be imported ; this is working fine with Maven 3.0, but not with 3.3. Another thing I’ve found during my tests is that this only happens when building the multi-module project ; when building openedge-plugin alone, the JAR file is correctly created. Given those facts, I’m really not sure the sonar-packaging-plugin could be the cause…
--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/43b27506-c997-47dc-9989-53cb9d909d4b%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/7b12bd38-0345-4bef-959a-a048191c236b%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/7b12bd38-0345-4bef-959a-a048191c236b%40googlegroups.com.
--Gilles QUERRET
Riverside Software
15d route de Bellevue • 69440 Mornant • France
Mob : +33 662.525.532
Ann
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/7b12bd38-0345-4bef-959a-a048191c236b%40googlegroups.com.
--Gilles QUERRET
Riverside Software
15d route de Bellevue • 69440 Mornant • France
Mob : +33 662.525.532
--Gilles QUERRET
Riverside Software
15d route de Bellevue • 69440 Mornant • France
Mob : +33 662.525.532
--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/49221290-ca23-4e94-afb9-45f199a6c124%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.