Aaron Mulder wrote:
> [X ] Add these features to the existing bin/deployer.jar tool > [ ] Create a new bin/xyz.jar tool with only these features, so we > have an "offline" deployer and a "JSR-88" or "J2EE" deployer.
Hiram Chirino wrote:
To simplify all the modes of operation I would recommend we follow the command structure that tools like "cvs" and "svn" use. So you would like something like:
admin.jar [general options] deploy [list of valid deploy command options] admin.jar [general options] undeploy [list of valid undeploy options] admin.jar [general options] start [list of valid start options] admin.jar [general options] start [list of valid stop options] admin.jar [general options] list modules [list of valid list options] admin.jar [general options] list targets [list of valid list options] admin.jar --help
I really like Hiram's idea above. IMO, our goal is to make things easier, not more complex. I think that a single tool will be easier to understand than two. Additionally, a simplified command set within the single tool will further ease the deployment process.
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&5R\\"F9E<G)E=\\$\\!F<FEI+F-O;0\\`\\`");'
The Castor Project http://www.castor.org/
Apache Geronimo http://geronimo.apache.org/
