New unified build-process for iron*-software and move to Github
From today, our iron-software uses a unified build process by using Maven instead of a wild mix of different build tools.
As all projects now are structured (mostly) the same, we also decided to move all sourcecode over to our Github account.
Software available via Github
This includes all of the following software:
Updated version numbers
We also updated the version numbers of our software as the following:
- irond: 0.3.4 to 0.4.0
- ifmapj: 0.1.4 to 0.1.5
- ifmapj-examples: 0.1.4 to 0.1.5
- ifmapcli: 0.0.2 to 0.0.3
- irongui: 0.4.0 to 0.4.1
- irondhcp: 0.3.0 to 0.3.1
- ironvas: 0.1.0 to 0.1.1
Changes to software
Some of our software also got some new features with the new released version:
- irond, ifmapj and ifmapj-examples now include experimental support for IF-MAP 2.1.
- ifmapcli: new tool to publish
<request-for-investigation>-metadata between a device and an IP adress (can be used pretty fine together with ironvas Subscriber functionality :-) )
- ifmapcli, irongui, irondhcp and ironvas now use ifmapj v0.1.5
New distribution strategy
So, our new distribution strategy/process will look like this:
- all sourcecode is now available via Github
- every release will be assigned a tag on its corresponding Github repostory, beginning with these initial releases
- the current binary distributions of all software will be hosted on this website via the download section
- all prior binary distributions will be available via the archive in the download section
Note: to get any iron* project to work, just download it from Github and run
$ mvn package; it will create a source and a bundle-archive in the target directory.
The bundle-archive is ready to go if you unzip it and run the contained jar-archive with
$ java -jar <archive>.jar.
If there are any comments or errors within the software or the move to Github, please feel free to contact us via email@example.com Apr 2013