Used to hold Spring Roo’s wrapping modules. These have a different lifecycle from the remainder of Roo, so belong outside of the “roo” repository.
Java CSS XSLT Shell
Permalink
Failed to load latest commit information.
antlr4-runtime ROO-3656: Fix wrapping version numbers Aug 7, 2015
aopalliance Generating Spring Roo Wrapping Repository Apr 29, 2015
bcpg-jdk15 ROO-3656: Fix wrapping version numbers Aug 7, 2015
bcprov-jdk15 ROO-3656: Fix wrapping version numbers Aug 7, 2015
cloud-foundry-api Fix missing to mark transitive dependencies as optional. Jul 23, 2015
commons-logging Fix missing to mark transitive dependencies as optional. Jul 23, 2015
connector Generating Spring Roo Wrapping Repository Apr 29, 2015
db2express ROO-3624: Deleting target folder from wrappings May 13, 2015
derby-client ROO-3656: Fix wrapping version numbers Aug 7, 2015
derby ROO-3656: Fix wrapping version numbers Aug 7, 2015
felix-framework ROO-3672: This bundle wraps the standard Maven artifact org.apache.fe… Sep 7, 2015
felix-http-jetty Update the classes that compose the patch to the solution applied by … Aug 31, 2015
firebird ROO-3656: Fix wrapping version numbers Aug 7, 2015
h2 Generating Spring Roo Wrapping Repository Apr 29, 2015
hapax Updating wrapping versions Jul 23, 2015
hsqldb Generating Spring Roo Wrapping Repository Apr 29, 2015
inflector ROO-3656: Fix wrapping version numbers Aug 7, 2015
javaparser Generating Spring Roo Wrapping Repository Apr 29, 2015
javax-el Fix missing to mark transitive dependencies as optional. Jul 23, 2015
javax-inject Fix missing to mark transitive dependencies as optional. Jul 23, 2015
jgit Generating Spring Roo Wrapping Repository Apr 29, 2015
jline ROO-3670: Updating JLine wrapping with patched Springsource version Sep 7, 2015
jsch Generating Spring Roo Wrapping Repository Apr 29, 2015
json-simple ROO-3656: Fix wrapping version numbers Aug 7, 2015
jsoup Creating JSOUP HTML Parser wrapping Apr 25, 2016
jtds ROO-3656: Fix wrapping version numbers Aug 7, 2015
jtopen ROO-3656: Fix wrapping version numbers Aug 7, 2015
mysql ROO-3656: Fix wrapping version numbers Aug 7, 2015
oracle ROO-3624: Deleting target folder from wrappings May 13, 2015
postgresql ROO-3656: Fix wrapping version numbers Aug 7, 2015
protobuf-full Generating Spring Roo Wrapping Repository Apr 29, 2015
protobuf-lite Generating Spring Roo Wrapping Repository Apr 29, 2015
repository ROO-3624: Updating Spring Roo wrapping repository May 15, 2015
snakeyaml ROO-3656: Fix wrapping version numbers Aug 7, 2015
src/main/assembly Generating Spring Roo Wrapping Repository Apr 29, 2015
.gitignore Creating JSOUP HTML Parser wrapping Apr 25, 2016
README.adoc Improve release process Aug 7, 2015
pom.xml Creating JSOUP HTML Parser wrapping Apr 25, 2016

README.adoc

Spring Roo Wrapping

Spring Roo wrapping repository

This Git repository contains various script files that enable easy production of OSGi-compliant bundles using a technique known as "wrapping". These are generally used by Spring Roo and its add-ons.

The goals of the JAR wrappers are:

  • Turn a non-OSGi JAR into an OSGi-enabled JAR.

  • Patch libraries by replacing or adding artifacts inside the JAR.

The output JAR is then usable in Roo or other OSGi containers

Prerequisites

In order to complete these instructions, you must have rights to deploy files to http://repo.spring.io/spring-roo/.

All wrapped JARs are deployed under the following directory:

/org/springframework/roo/wrapping

To perform wrapping you need:

  • A proper installation of Java 6 or above

  • Maven 3.0.1+ properly installed and working with your Java 5+

  • Internet access so that Maven can download required dependencies

  • Upload privileges to the above location

  • GPG setup (see main Spring Roo readme.txt for instructions)

If you want to host an OSGi-compliant JAR that does not need wrapping at http://repo.spring.io/spring-roo/, be sure to create an .ASC file of the JAR and pom.xml using gpg --ab <filename> and upload the ASC files as well.

GIT Policies

The same Git policies apply to this repository as the normal Roo repository.

Naming conventions

By being pkgArtifactId and pkgVersion the artifactId and the version of the "input" non-OSGi JAR, the wrappings must follow the naming conventions below:

  • The groupId must be org.springframework.roo.wrapping

  • The artifactId must be groupId.pkgArtifactId

  • The version must be pkgVersion.wrapper.version

Note
wrapper.version is a three-digit string that identifies the version of each wrapper in order to know the latest release of that wrapper.

Releasing

The wrapping repository is separated from the normal Roo repository at Maven Central so that each project in the wrapping repository can be released as part of its own release cycle. The wrapping projects are NOT released during the normal Roo release cycle and the Roo CI server does NOT perform any wrapping module releases.

As such, it is expected that developers wishing to make wrapped JAR available will manually produce/edit the relevant subdirectory of the wrapping JAR and then connect to https://repo.spring.io/ to deploy the JAR manually.

Important
Before releasing, ensure you increment the final three-digit suffix for the version number displayed in the pom.xml. This ensures everyone is on the latest release you have made.

Help

If you have general questions on Roo’s wrapping approach, please use the Stackoverflow. You can access it at http://stackoverflow.com/questions/tagged/spring-roo. Thanks for your interest in Spring Roo!