On this release the most notable tasks that were implemented are the following:

SCP Repository Manager plugin

A new plugin for Repository Management has been added. This encapsulates the possibility to upload your releases/snapshots to a remote server filesystem using an SCP command. Once you configure your SCP repository it is important to take into account that maven will reject uploading the files until you accept the server’s hostname in command line, so you will need to do a manual deploy from the command line in order to accept it. Maybe in the future there will be a way to automatically accept it from the web interface of Jabox.

Single Storage location

The embedded servers are being configured by default to store their data inside the ${JABOX_HOME}/.jabox/ directory. This way you will have a single storage location making easier to process of backup / migration. You also need only one location to make sure that it is writable by the user’s process. Of course you can always override the location of each embedded server (Hudson / Artifactory / Nexus) to be your preferable directory by setting the necessary environment / property variable (e.g. HUDSON_HOME)

Here is how the directory structure looks like now:

UTF-8 source encoding

Have you ever seen this WARNING in maven console?

[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!

If you have worked some time with maven, you have certainly see it more than once. But what exactly does this mean? Well by default maven is doing source manipulation using your platform encoding, which is least to say not healthy for your project, since it will behave differently in Windows/Linux compilation.

The best practice guides us to configure our encoding inside the maven pom.xml file. Jabox will by default set your project to use UTF-8 encoding, but you can change the default value to your own preference:

The result will be the following INFO line in maven console:

[INFO] Using 'UTF-8' encoding to copy filtered resources.

Now your builds are platform independent. For more information about maven source file encoding see: http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding

Tight Integration with Maven tools

Maven has the possibility to be configured to have the knowledge for the services used for development, in order to make tight integration with your tools. You can define the “Source Control” the “Issue Tracker” or even the “Continuous Integration” urls for the current project. This information is already known in Jabox and now it delegates this information to Maven.

Moreover Jabox is not just delegating the URL of the service, but knows how to construct the project URL page for each service, this way you will be directed directly to the project page.

A good example of this is the use of m2eclipse plugin in Eclipse, which can open for you the requested URL inside Eclipse for faster navigation:

Changelog

Here is the changelog:

• Add SCP Repository manager plugin
• Set embedded Nexus Home directory to be ${JABOX_HOME/.nexus/ but leave the possibility to override it.
• Set embedded Hudson Home directory to be ${JABOX_HOME}/.hudson/ but leave the possibility to override it.
• Set embedded Artifactory Home directory to be ${JABOX_HOME}/.artifactory/ but leave the possibility to override it.
• Automatically add utf-8 configuration to maven pom.xml (optionally)
• Automatically add necessary plugins to embedded Hudson.
• Automatically add issueManagement configuration to maven pom.xml
• Automatically add cis configuration to maven pom.xml