The coolest feature, (which is still in the process of being implemented), will allow one to easily see what has changed between war file versions. (Say you have a configuration file containing data specific to your deployment, such as jdbc connection parameters. This will allow you to quickly validate if you've updated your files).
Like the gentoo tools it was based on, it is written in python. This is a quick project and has been developed and tested in the past couple of days (unittests have made my life a lot easier, during various refactorings throughout the week).
So my question to you, lazy web, is what do you think of a tool like this? Is it useful? Overkill? Redundant? How do you manage configuration changes in your J2EE deployments? Please feel free to post your comments below.
This is an interesting project, and one I wonder how useful it would really
be. I think in its current incarnation, the ability to simply see if there
is a difference in the two war files wouldn't be terribly useful. For
example would a simple recompilation highlight that the fact the two war's
were different?
I like this idea a lot. I know that it would be very helpful for quality
purposes if you had to track down something that went wrong and if/when it
changed. We keep all our old versions around (we basically do symlinks to
point to the actual live version), and it would be nice to see exactly what
changed between two wars.
Alan- I got it so it is now diffing. I need to provide some sort of
integration with editors or mergers now.
Matt, if you want to start digging around in class files, you might be
interested in the classfile module found in the javaclass project:
http://www.python.org/pypi/javaclass. The module provides a Python API to
access details concerning the methods, attributes, interfaces (and so on)
inside Java class files. (The project itself was slightly more ambitious
but isn't currently being developed.)