GroupId for CAR file
It seems that car-maven-plugin now installs the zipped car at o.a.g.configs by default. If the target/repository contains o.a.g.plugins.monitoring/... should the car not be installed at o.a.g.plugins.monitoring in .m2 repo? If a groupId is explicitly given, e.g. mrc-server-car in sandbox/monitoring, the artifact is installed correctly. But client-tomcat is installed at o.a.g.configs. Am I missing something? Thanks Anita Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ
Re: GroupId for CAR file
Never mind.. I had older CARs in the repo. Thanks Anita --- Anita Kulshreshtha [EMAIL PROTECTED] wrote: It seems that car-maven-plugin now installs the zipped car at o.a.g.configs by default. If the target/repository contains o.a.g.plugins.monitoring/... should the car not be installed at o.a.g.plugins.monitoring in .m2 repo? If a groupId is explicitly given, e.g. mrc-server-car in sandbox/monitoring, the artifact is installed correctly. But client-tomcat is installed at o.a.g.configs. Am I missing something? Thanks Anita Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
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 -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Apache Geronimo - http://geronimo.apache.org/ Castor - http://castor.org/
Re: Our 2.1 assemblies are nearly 2x the size of 2.0.2
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:dev@geronimo.apache.org 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 -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Apache Geronimo - http://geronimo.apache.org/ Castor - http://castor.org/
Re: Our 2.1 assemblies are nearly 2x the size of 2.0.2
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:dev@geronimo.apache.org 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
Re: GShell 1.0-alpha-1 update
On Nov 30, 2007, at 8:42 AM, Kevan Miller wrote: I'm hoping to get GShell 1.0-alpha-1 out in the next week or so, really as soon as the deps are published I will start the ball moving. I could use a little help in the mean time for things like legal oversight and anything else I might have missed to help make the vote+release as smooth as possible, So if you have a few minutes spare it would be nice if you could build the tree and poke around a bit er something. Hi Jason, I took a look at the GShell source. Things look good. Two files had old-style src license headers. I'm updating those. Cool, thx. Remaining work, legal-wise, is getting license/notice files in your jars (and updating notice/license file in the root directory). Let's sync up later today. Can discuss the maven-remote-resources plugin and see if we can get it working for GShell... Hrm... maybe I got mixed up... I've got too many plugins I'm working on these days. Could have sworn I enabled m-r-r-p for GShell... Lemme peep again. --jason
Re: Our 2.1 assemblies are nearly 2x the size of 2.0.2
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:dev@geronimo.apache.org 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
[jira] Created: (GERONIMO-3661) Optimize GShell libs for G server assemblies
Optimize GShell libs for G server assemblies Key: GERONIMO-3661 URL: https://issues.apache.org/jira/browse/GERONIMO-3661 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Reporter: Jason Dillon Assignee: Jason Dillon Priority: Blocker Fix For: 2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: GShell 1.0-alpha-1 update
Okay, I put it back in... publishing new snaps now. --jason On Nov 30, 2007, at 8:42 AM, Kevan Miller wrote: On Nov 29, 2007, at 3:18 AM, Jason Dillon wrote: Folks, I've halted any significant changes to GShell so we can push out a stable release for Geronimo to consume in the next week or so. Right now it is pending some dependency releases: * plexus-cdc-anno * plexus-component-annotations * maven-remote-resources-plugin * groovy-maven-plugin * cobertura-maven-plugin I've got the ball rolling on each of those and with a wee bit of luck and probably a healthy dose of pestering folks, we should get all of these resolved to facilitate the first *official* GShell release... yay! I'm hoping to get GShell 1.0-alpha-1 out in the next week or so, really as soon as the deps are published I will start the ball moving. I could use a little help in the mean time for things like legal oversight and anything else I might have missed to help make the vote+release as smooth as possible, So if you have a few minutes spare it would be nice if you could build the tree and poke around a bit er something. Hi Jason, I took a look at the GShell source. Things look good. Two files had old-style src license headers. I'm updating those. Remaining work, legal-wise, is getting license/notice files in your jars (and updating notice/license file in the root directory). Let's sync up later today. Can discuss the maven-remote-resources plugin and see if we can get it working for GShell... --kevan
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:dev@geronimo.apache.org 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
Re: Our 2.1 assemblies are nearly 2x the size of 2.0.2
AWESOME Gianny Damour wrote: 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:dev@geronimo.apache.org 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
Re: Our 2.1 assemblies are nearly 2x the size of 2.0.2
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 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. 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:dev@geronimo.apache.org 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:dev@geronimo.apache.org 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
Re: Our 2.1 assemblies are nearly 2x the size of 2.0.2
Maybe a wiki page of some sort laying out the goals for any upcoming GShell release where people can tag their name next to areas their tooling around in. It'd by no means be some sort of gold rush claim to parts of gshell. It would just let people know what areas they might need to tread softly in, for fear of mucking up someone's work. It would also help to draw light to what areas of gshell are getting ignored. Those sad, lonely little areas. ~Jason Warner On Dec 1, 2007 9:12 PM, Jason Dillon [EMAIL PROTECTED] 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 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. 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:dev@geronimo.apache.org 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:dev@geronimo.apache.org 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
Re: Our 2.1 assemblies are nearly 2x the size of 2.0.2
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:dev@geronimo.apache.org 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:dev@geronimo.apache.org 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
