How We can parse .xqy File in sonar? - parsing

Is There any sonar xquery plugin which can parse and check the naming convention of xquery files.
What types of files we need to create for xquery plugin?

Related

How to generate self-contained specification of openAPI

Intellij's SwaggerHub Smartbear plugin has functionality 'Export self-contained specification(YAML)' which will resolve all the remote $ref(s) and generate local
definitions of domain models in the generated output document.
Is there a way to do it programmatically for making it as part of build pipeline? Any java program or scripts can we write for the same?

Bazel: hermetic use of jar command?

We have a custom Skylark rule that invokes jar after using the Thrift compiler to generate .java files, modeled after genproto.bzl.
What is the recommended way to invoke an external jar command in a hermetic way? Should we use new_http_archive to pull in the JDK archive (and how would this work with the DMG Oracle provides for OSX) with something like jdk.BUILD?
You have #local_jdk//:jar that expose the jar binary coming from the jdk used by Bazel.

Is there any way to decompile grails/groovy jar file?

I have a groovy/grails jar file. I want to decompile it into groovy files. Is there any tool to do that. I have tried some online decopilers , they all decmpile the files into java not groovy. I have created the jar using gradle jar command. I'm using grails version 3.1.11 and groovy version: 2.4.7 and gradle verion: 2.13
You can use any Java decompiler, but you will not get Groovy code back, as no such tool exists (to my knowledge)
This is one of the weaknesses of non-Java JVM languages. Groovy does a lot of reflection and other such trickery in creating its bytecode, so if you decompile the .class file, you'll have a lot of noise. This is similarly reflected in Groovy stacktraces. You have to train yourself to find the signal despite all of the noise. The good news is that both Eclipse and IntelliJ can debug Groovy code nicely, so you can step through to find the issue you're dealing with.

Specifying desired packages for Gradle Javadoc task

I'm trying to convert an ant build file to Gradle and I was wondering if there exists a way to specify which packages should be in the javadoc in the same way 'packagenames' works in ant?
Thanks
Jonathan
See the 'includes'/'excludes' properties, or related methods. The patterns use the same syntax as ant.
javadoc {
exclude "**/internal/**"
}
As another example, if the build process generates Java source files into a build directory, the Javadocs can be generated using:
javadoc {
source = "$buildDir/"
include( "**/*.java" )
}
This ensures that only .java files are parsed. Note that the parentheses are optional.

Xtext 2.0 maven or ant project

I want to build my own xtext 2.0 project from command line.
Could anybody share real working xtext 2.0 maven pom.xml or ant build.xml file?
do you know http://code.google.com/a/eclipselabs.org/p/spray/. they build Xtext projects using Maven Tycho.
You can use this Maven archetype that creates an Xtext project with a multi module Maven layout and Tycho (manifest-first approach):
https://github.com/fuinorg/emt-xtext-archetype
Several projects that you could refer to:
https://github.com/xtext-dev/maven-xtext-example
a standard maven-xtext sample using tycho, including maven pom settings and example project. I built my xtext project following this guide.
https://github.com/aphethean/xtext-maven-examples
It'll help if you wanna write your own main class.
Also,
https://github.com/applause/applause
It's not a maven xtext project, but a very good example to show how to separate grammar core and code generator logics.
Hope this would help. :)

Resources