Normally I try to be positive, but I am having a very hard time with this change.
You have now made the core dependent on twiddle, which in turn is dependent on a load of other things like commons-cli, forehead, classworlds, castor, dunno what else. Do we really need to add all this? What about all the other ways to start the server e.g. raw embedding, a WinNT service, ??? Even a basic Windows bat script would be useful. What about IDE support as well - I used to be able to just run the server directly by invoking Main, but I don't seem to have that option any more. What do I need to do to get this back again? And where was the advance notice? I couldn't see any discussion on the list and this wasn't exactly a zero-impact change. All in all I think this was a bad move and would ask you to back some of the more intrusive bits out - at least remove core's dependency on twiddle. -- Jeremy > -----Original Message----- > From: Jason Dillon [mailto:[EMAIL PROTECTED] > Sent: Sunday, August 24, 2003 10:56 AM > To: [EMAIL PROTECTED] > Subject: [twiddle] Twiddle is now booting Geronimo > > > I finished my initial checkin to allow a Twiddle command to start > Geronimo. > > To start Geronimo, after building you can: > > cd target > ./geronimo-DEV/bin/start > > or > > cd target > ./geronimo-DEV/bin/twiddle geronimo/start > > Right now you need to be in the target directory. I will resolve this > soon, but for now dat is how it be ;-) > > Help (via ./geronimo-DEV/bin/start --help) looks like: > > usage: geronimo/start [options] > > Options: > -d,--deploy <arg> Deploy URL > -h,--help Display this help message > -m,--mlet <arg> MLet URL > > So you can change the config urls. It does spit out a lot of debug > too, which I will get around to fixing, though some of that is > dependent on getting the Commons Logging package to properly handle > trace for Log4j (patch pending... right James?). > > Unfortunately Commons CLI does not order options, so the options are a > bit scrambled... need to see about fixing this. > > Removed the CLI bits from Main, as StartCommand handles these details > now. The top-level run goal should still work as I changed it to > behave like the twiddle script. > > Twiddle boots with Werken Forehead to make the initial setup of > classpath nice and simple for me. You can control Forehead via > etc/forehead.conf > > * * * > > I still need to create windows scripts (ick). > > Also we need to start thinking a little about the release structure. I > am currently thinking of a structure similar to... well you know... > something like this: > > geronimo-<release>/ > README.txt > LICENSE.txt > VERSION.txt > docs/ > <html docs> > bin/ > <scripts> > lib/ > <boot-libraries> > etc/ > forehead.conf > twiddle.conf > twiddle/ > geronimo.conf > <twiddle-command-configs> > config/ > global/ > lib/ > <libs global to all configs> > resources/ > <resources files global to all configs> > deploy/ > <deployments global to all configs> > <config-name>/ > lib/ > <libraries> > resources/ > < resources files> > deploy/ > <deployment files> > tmp/ > <temporary files> > data/ > <non-transient data/state files> > log/ > <log files> > > I am wondering if anyone else has any ideas. > > --jason > >
