Download JAR files tagged by accordingly with all dependencies

Maven plugin that automatically increases the version number accordingly, it support commit hash too!

Gradle plugin that combines git tags and semantic versioning, and sets the gradle version property accordingly.

Provides a custom ViewProvider which evaluates @ViewDescription's and instanciates Views accordingly if the current User, authenticated through Spring Security, has the necessary permissions to use them.

Analyses the JPA entities in a specified package and generates DDL statements for schema generation. Besides the Entity annotation, this plugin processes the Hibernate Envers annotation Audited and generates AUD tables accordingly.

The Price and Promotion Label Execution (PPLE) SDK by Scandit is a tool for validating price labels. It provides the capabilities for validating the price and aggregating this information to a web tool. For each scanned label, the SDK validates its price and indicates whether it is correct, incorrect or unknown. Your application can be then designed to function based on this information. Mismatched data then can be uploaded to the web tool and tasked accordingly.

This module provides four Enhancement Engines for the DBpedia Spotlight RESTful services. This includes the Annotate Engine - supporting the whole processing workflow as well as a Spotting, Candidate and Disambiguation Engine that can be used by Users that whant only to use part of DBpedia Spotlights functionalities within their own Enhancement Engines. Users that do not want to send their Content to the public Spotlight server can also install a local Spotlight server and change the Configuration of the Engines accordingly.

This project produces the Mojo that can build a proper release.xml for the SQuirreLSQL update site, given a directory where the updated jar artifacts are located. This plugin accepts a directory in it's configuration and expects to find three sub-directories there : core, plugins and i18n. It then categorizes the artifacts found in those directories accordingly in the final release.xml file, that is generated in the specified folder.

--------------------------------------------------------------------------- Version for VIVO 1.9 This uses the source and test code from the Version for VIVO 1.10, edited to make it compatible with VIVO 1.9. It also borrows some code from VIVO 1.10 itself, changes the package name to avoid conflicts, and adds it here. * Vitro 1.9 uses Jena 2, not Jena 3, and Commons Lang 2, not 3, so modify the "import" statements in the Data Distribution code accordingly. * Vitro 1.9 has an earlier version of "...webapp.utils.sparqlrunner" package, so borrow the source from Vitro 1.10, move it to a different package so it won't conflict with the 1.9 version, modify it to use Jena 2 and Commons Lang 2, and modify the Data Distribution API code to use this sparqlrunner package. * Vitro 1.9 has an earlier version of "...webapp.utils.configuration" package, so borrow the source from Vitro 1.10, move it to a different package so it won't conflict with the 1.9 version, modify it to use Jena 2 and Commons Lang 2, and modify the Data Distribution API code to use this configuration package. Make these modifications, compile, JAR it up, and deploy. ---------------------------------------------------------------------------

--------------------------------------------------------------------------- Version for VIVO 1.8 This uses the source and test code from the Version for VIVO 1.10, edited to make it compatible with VIVO 1.8. It also borrows some code from VIVO 1.10 itself, changes the package name to avoid conflicts, and adds it here. * Vitro 1.8 uses Jena 2, not Jena 3, and Commons Lang 2, not 3, so modify the "import" statements in the Data Distribution code accordingly. * Vitro 1.8 does not have a "...webapp.utils.sparqlrunner" package, so borrow the source from Vitro 1.10, move it to a different package (just for compatibility with the 1.9 version), modify it to use Jena 2 and Commons Lang 2, and modify the Data Distribution API code to use this sparqlrunner package. * Vitro 1.9 has an earlier version of "...webapp.utils.configuration" package, so borrow the source from Vitro 1.10, move it to a different package so it won't conflict with the 1.9 version, modify it to use Jena 2 and Commons Lang 2, and modify the Data Distribution API code to use this configuration package. Make these modifications, compile, JAR it up, and deploy. --------------------------------------------------------------------------- Because VIVO 1.8 is not available as a Maven package, we have extracted the class files, JARed them up, and stored them in a file-based repository within this project. But that doesn't include any transitive dependencies, so any package that this code requires must be explicitly listed as a dependency. ---------------------------------------------------------------------------