Our team has developed a handful of applications. To provide you with some of that technology, we've created this page. Enjoy the work, but remember...if you make changes, give em back. We want to provide others with the same opportunity. The collective mind is better than just a few so please embrace the open source methodology. If you have something to contribute, feel free to use our issue tracking system. Attach a patch to your ticket and we'll review it for inclusion.
Happy Hacking!
Tools
Git
We use Git as our version control system. We chose it because it provides us with the best set of features for our needs. If you'd like to get the source you'll need it as well.
To work with our source download and install Git
Eclipse
We use Eclipse for Java dev. The biggest reason is that it is simply the best Java IDE. With the constant work on the platform and attention to the right details, they have produced a great place to work.
To work with our Java source code download and install Eclipse
Our Work
Stack
The Axiom Stack source is open to the world. This means that you can help! To start working with the source code you should follow these steps.
- Obtain the source. From a terminal type:
git clone git://github.com/axiomsoftware/axiom-stack.git
- Load the project file from the branch
- Please be sure to review the README.txt file within the branch
- When you've finished something create a patch and shoot it over
git diff > changes.diff
- Put the diff in our Google Group or in our issue tracking system
Lucene
We've had to make a couple of changes to Lucene to support our specific implementation. Therefore we are providing those changes to you. You'll need them.
- Obtain the source. From a terminal type:
git clone git://github.com/axiomsoftware/axiom-lucene.git
- Load the project file from the branch
Blog
A proof of concept application that turned out to be relatively useful was our blog. We use this over at Axiom Blog. This goes into development when we find something we need. You can help to push this project forward. To do so follow these steps:
- Obtain the source. From a terminal type:
git clone git://github.com/axiomsoftware/axiom-blog.git
- You'll want to then put this application inside the 'apps' directory in your stack directory.
- Take a look at the readme file for more information.
Inspector
Our team, other developers, and implementers requested a better way to debug and visualize what they were working on. We answered. Behold the inspector. Written as an object viewer it started with the quest to be able to quickly add objects to a hierarchy. It soon turned into an IDE for Axiom Stack. It provides the ability to debug and create objects. You can step through code as well to follow the call trace. It's quite useful. To get it follow these steps:
- Obtain the source. From a terminal type:
git clone git://github.com/axiomsoftware/axiom-inspector.git
- You'll want to then put this application inside the 'modules' directory in your stack directory.
- Make sure to add the proper items to your 'app.properties' file.
rhino.debugger = true inspector.user = [username] inspector.password = [password] inspector.mountpoint = inspector modules = inspector
- You need to add the mountpoint to your applications rewrite.properties file as it attaches itself to the root object.
/inspector = /inspector

