Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
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.
CSS Java XSLT Shell
Branch: master
Failed to load latest commit information.
antlr4-runtime ROO-3656: Fix wrapping version numbers
aopalliance Generating Spring Roo Wrapping Repository
bcpg-jdk15 ROO-3656: Fix wrapping version numbers
bcprov-jdk15 ROO-3656: Fix wrapping version numbers
cloud-foundry-api Fix missing to mark transitive dependencies as optional.
commons-logging Fix missing to mark transitive dependencies as optional.
connector Generating Spring Roo Wrapping Repository
db2express ROO-3624: Deleting target folder from wrappings
derby-client ROO-3656: Fix wrapping version numbers
derby ROO-3656: Fix wrapping version numbers
felix-http-jetty ROO-3658: Apache Felix HTTP Jetty are logging to System.out
firebird ROO-3656: Fix wrapping version numbers
h2 Generating Spring Roo Wrapping Repository
hapax Updating wrapping versions
hsqldb Generating Spring Roo Wrapping Repository
inflector ROO-3656: Fix wrapping version numbers
javaparser Generating Spring Roo Wrapping Repository
javax-el Fix missing to mark transitive dependencies as optional.
javax-inject Fix missing to mark transitive dependencies as optional.
jgit
jline Generating Spring Roo Wrapping Repository
jsch Generating Spring Roo Wrapping Repository
json-simple ROO-3656: Fix wrapping version numbers
jtds ROO-3656: Fix wrapping version numbers
jtopen ROO-3656: Fix wrapping version numbers
mysql ROO-3656: Fix wrapping version numbers
oracle ROO-3624: Deleting target folder from wrappings
postgresql ROO-3656: Fix wrapping version numbers
protobuf-full
protobuf-lite Generating Spring Roo Wrapping Repository
repository ROO-3624: Updating Spring Roo wrapping repository
snakeyaml ROO-3656: Fix wrapping version numbers
src/main/assembly Generating Spring Roo Wrapping Repository
README.adoc Improve release process
pom.xml

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!

Something went wrong with that request. Please try again.