On 02/12/2007, at 1:12 PM, Jason Dillon wrote:
Cool! A few comments though...
Right now aliases are defined in layout.xml, I'd like to not have
morew config for this. What is the point of execute-alias?
The idea is to be able to create aliases with options and arguments.
For instance, I should be able to do that:
> alias startServer1 'start-server -G server.name=yellow -D
otherProperty=otherValue'
then
> execute-alias startServer1
Currently, people could create external files and source them to do
the same thing. However, I think that the above approach may be more
handy.
The rsh bits are still on the experimental side and subject to
change. I think we'd be better off lea?ing them for 2.2
integration, which was what I had intended.
I observed couple of problems in here and there; however, I believe
the rsh stuff works sufficiently well at the moment to be enabled in
2.1. This could be flagged as a feature preview planned to be
completed for 2.2. This way we could start to collect user feedback
and re-adjust the feature for 2.2.
What do you think? If you do not like it, then I am happy to commit
this change after 2.1.
Thanks,
Gianny
But overall... Cool beans that other folks are starting to help
with GShell!!! Perhaps we need a little more discussion on who is
doing what for now and the next release?
--jason
-----Original Message-----
From: Gianny Damour <[EMAIL PROTECTED]>
Date: Sun, 2 Dec 2007 12:40:41
To:[email protected]
Subject: Re: Our 2.1 assemblies are nearly 2x the size of 2.0.2
Hi,
Some heads-up.
I will soon add gshell-remote-client/common/server, gshell-whisper
and mina dependencies so that we can remote control servers. In other
words, it will increase a little bit more.
This may still change, however here is a list of the new commands:
* alias: to create an alias;
* unalias: to remove an alias;
* execute-alias: to execute an alias;
* remote/rsh: rsh client;
* remote-rsh-server: rsh server;
* remote-control/server-control: to execute a control operation start/
stop, for a remote server. This command rsh to a gshell instance
where the server is to be started or stopped and execute the proper
command.
Aliases will be stored in etc/aliases.xml and users will be able to
alter that if they want via CLI option. remote-control/server-control
uses a hierarchical tree to defined hosts along with how to remote
login to a gshell running on this instance and commands to control
servers.
Thanks,
Gianny
On 02/12/2007, at 12:29 PM, Jason Dillon wrote:
The core muck is a little over 1m, but for the G integration we are
using Groovy for commands, which adds about 2.5m for the core
runtime and then its got a few deps too. I can work on optimizing
this a bit, have not really paid much attention, aside from trying
to keep the GShell core size as small as possible.
I think we can put most of its deps in the repo and just hardcode
them in the classworlds conf for now. Next version will
dynamically pull them out of the repo in the same way that mvn
plugins do.
--jason
On Dec 1, 2007, at 5:16 PM, Jeff Genender wrote:
Damn gshell...WTF?
:-)
I couldn't resist ;-)
Jeff
Jason Dillon wrote:
No doubt some increase is from the gshell libs. We can probably
optimize them a little and use repository references and such...
--jason
-----Original Message-----
From: "Bruce Snyder" <[EMAIL PROTECTED]>
Date: Sat, 1 Dec 2007 14:52:44
To:[email protected]
Subject: Re: Our 2.1 assemblies are nearly 2x the size of 2.0.2
On Nov 30, 2007 3:59 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
It looks like the size of our images is increasing dramatically
(nearly 2x).
For example, the geronimo-jetty6-minimal snapshots have been
growing
like this (these image sizes are from the snapshot repo):
16604006 Jul 26 18:54
geronimo-jetty6-minimal-2.1-20070726.182538-1-bin.tar.gz
17086729 Jul 26 18:53 geronimo-jetty6-
minimal-2.1-20070726.182538-1-bin.zip
22310769 Nov 1 03:19
geronimo-jetty6-minimal-2.1-20071101.014839-2-bin.tar.gz
22744083 Nov 1 03:18 geronimo-jetty6-
minimal-2.1-20071101.014839-2-bin.zip
30812531 Nov 30 22:45
geronimo-jetty6-minimal-2.1-20071130.211933-3-bin.tar.gz
31248864 Nov 30 22:43 geronimo-jetty6-
minimal-2.1-20071130.211933-3-bin.zip
The javaee5 images have also grown significantly.
57099671 Jul 26 18:39 geronimo-jetty6-jee5-2.1-20070726.182538-1-
bin.tar.gz
58685668 Jul 26 18:36 geronimo-jetty6-jee5-2.1-20070726.182538-1-
bin.zip
55113050 Nov 1 03:28
geronimo-jetty6-javaee5-2.1-20071101.014839-1-bin.tar.gz
56827820 Nov 1 03:25 geronimo-jetty6-
javaee5-2.1-20071101.014839-1-bin.zip
71313050 Nov 30 22:54
geronimo-jetty6-javaee5-2.1-20071130.211933-2-bin.tar.gz
73094816 Nov 30 22:50 geronimo-jetty6-
javaee5-2.1-20071130.211933-2-bin.zip
I haven't looked into the cause yet ... but does anybody have
some ideas
on the culprit?
FWIW, we've experienced the same thing with ServiceMix. I think it
might be a problem with Maven and how it's resolving and including
transitive dependencies.
Bruce
