Jabox

Open Source A.L.M.

Download

Download The latest binary here:


Jabox 0.0.8
Launch

Launch the application.
Develop

Start developing with your favorite tools.
Jabox Blog
New jabox version 0.0.8

This version contains a lot of nice features. The most important of those are:


Information Icons


Everywhere in the application there are now those question mark icons. Whenever you are not certain of the functionality of a specific item you only need to hover over the related icon. For the important features there is also a link to a corresponding URL that explains in more detail the problem that is solved by it.



Sign Artifact Releases

In order to be able to upload artifacts in the maven central, you need to sign your released artifacts (see http://maven.apache.org/guides/mini/guide-central-repository-upload.html ). This can be easily done by using the maven-gpg-plugin. Of course you don't want to sign your artifacts during normal builds so you need to create a profile to avoid the overhead. In order to automate the process for newly created projects there is now this checkbox that can allow you to inject the needed profile in the pom.xml of the new project.
 


Pre-validated Configuration

Maven configuration is pretty complex and sometimes the errors of those configurations are not being surfaced until it is too late, like during a release phase. Now, whenever a connector is configured in Jabox, the data are being validated on the fly in order to make sure that the connector is working properly. This way any data that is given will be validated for their format and content.





Changelog


here is the detailed changelog:

  • Set (Embedded only) Hudson to download and use Maven (v2.2.1) during first build
  • Add info icon with tooltips
  • Add verification to Beanstalk service
  • Add verification to Subversion service
  • Add verification to Redmine service
  • Add URL validators
  • Sign the released artifacts (optionally)
  • Set server-jabox container to be expanded inside the JABOX_HOME directory (default ~/.jabox)
  • Add credentials for ITS services (Redmine/Bugzilla/Jtrac)
  • Give CLI feedback when downloading files.
 
New version is out: 0.0.7

New Jabox version: 0.0.7


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
 
New version is out: 0.0.6

New Jabox version: 0.0.6


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


A) One-Click Releases


Wouldn't you like to be able to make releases of your project by the click of one button? This is possible if you have the correct tools, and Hudson is definitely a must-have in your swiss-army-knife for software development.

Hudson has a nice plugin that's called m2release-plugin. If you activate it on a maven job it gives you a release button that can be used to make the releases for the project. The embedded Hudson is now being injected with this plugin so that you don't need to install it manually. Moreover all new jobs are being configured automatically to activate the plugin. This way Jabox gives you out-of-the-box release cycles with one click.

B) Bidirectional Traceability


Wouldn't be nice to have the possibility to track down all the commits that have been done for a specific issue? Or the other way around, know for what reason a specific commit has been done in your project? Building a bidirectional traceability between Issues and Commits is a very nice time-saver feature.

Redmine has the possibility to be configured as a repository viewer. Once you give the necessary information it will give you a tab so that you can browse your code from your browser (if you have the necessary credentials of course). But this is just the beginning because once the Redmine knows your repo, it can pull the commit comments from it. There you can reference to specific issues using their IDs, so that redmine can create a link between them. Even better you can give commands to redmine to close an issue through your comment's text if you like.

Redmine plugin for Jabox now contains a checkbox that will configure automatically the repo for you.

From the other side, Hudson has the possibility to be configured so that the changeset that is being shown for the builds can be decorated with links that point to the redmine repo viewer, in order to give you the specific changed files or even the differences applied to them side-by-side. 

Jabox's new projects on Hudson will now configure automatically the redmine-plugin for you.



Changeset


Here is a list of the changes on version 0.0.6:


New Features:

  • added "addRepositoryConfiguration" checkbox in Redmine plugin to automatically configure Repository of Source code (checked by default).
  • Injected m2release-plugin on embedded Hudson during startup in order to provide releases out-of-the-box.
  • Automatically configure Hudson's m2release-plugin for new jobs.
  • Automatically configure Hudson's redmine-plugin to connect changesets with Redmine's repository.
  • update Hudson version to 1.353
  • Automatically add SCM configuration to newly created maven projects.
  • Create Embedded Artifactory plugin.
  • Create Embedded Hudson plugin.
Changes:
  • Set first created Server to Default automatically
  • Default Server can be deselected now by clicking on Star icon
Bugs:
  • Default Server cannot be deleted
 
New version is out: 0.0.5

A new version just came out to correct a problem with the Beanstalk plugin:


The plugin now supports "Project Name" field in order to add the name of your created project in Beanstalk.


In order to use the plugin, you need to sign-up in Beanstalk first and create your project as a Subversion repository. Then pass the Account URL, the Project Name and the credentials to jabox in order to be able to login and commit your project.


Check-out the Screencasts section in order to see the plugin in action.


Beanstalk thank you for your beautiful service, as for the rest of you be very careful as the use of this service is dangerously addictive.
 
<< Start < Prev 1 2 3 4 Next > End >>

Page 1 of 4
Polls
What is your favorite IDE?
 
Donation