The items I originally listed
scripts
schemas
online deployer
hot-deploy
are now present and AFAICT working in the assemblies build. IIUC
correctly everyone has reluctantly agreed to wait with an offline
deployer until we can make it work well, hopefully next week. Jeff and
Bruce have indicated on IRC that they are OK with this. I've created
GERONIMO-1306 to track this and will proceed to delete it after a final
build to check that everything still works.
thanks
david jencks
On Dec 5, 2005, at 11:52 AM, David Jencks wrote:
I'm not sure I can get an offline deployer working by tuesday for
inclusion in 1.0. If I can get anything working the most likely
success would be 2 tools that mimic the packaging plugin and assembly
plugin except use the geronimo repo and config store instead of the
maven repo. So, offline deployment would require 2 steps:
1. build a car into the geronimo repo
2. install the car from the geronimo repo into the geronimo
config-store
I think this is a better sequence of events anyway, since you get a
distributable car file out of it.
Do you prefer to delay 1.0 release or ship 1. 0 without an offline
deployer and supply it in a few days as a separate download?
I consider an online deployer more essential than an offline deployer,
and would like to get that integrated into the assemblies build ASAP.
The new offline deployer is going to be a separate tool anyway and
would require an indeterminate amount of work to make the
modules/assembly build use it, work that I am certain I don't have
time for until after apachecon and in any case no interest in doing
since we are about to kill the module anyway.
thanks
david jencks
On Dec 5, 2005, at 11:40 AM, Jeff Genender wrote:
I agree with Bruce on this.
Jeff
Bruce Snyder wrote:
On 12/5/05, David Jencks <[EMAIL PROTECTED]> wrote:
My understanding is that we all agree that for 1.0 we will use the
jetty/tomcat only builds from assemblies rather than the
modules/assembly build that includes both. I'd like to remove the
modules/assembly build today.
Here's what I know is missing from the new assemblies/* builds:
scripts
schemas
online deployer tool
hot-deploy config
Of these the most problematical is the online deployer tool.
Offline
deployment won't work the same way with the new builds, and I'm
working
on a separate replacement. However offline deployment is used in
the
modules/assembly build.
I'd like to remove the modules/assembly build now and work on these
missing pieces without having to maintain 2 build systems.
Opinions?
BTW I'm planning to do the scripts by building a jar containing them
and unpacking in each assembly, and the schemas by (probably)
enhancing
the assembly plugin.
I suggest we get these items fixed before actually removing the
modules/assembly dir. What's wrong with leaving it in place until
we're sure that everything is copasetic?
Bruce
--
perl -e 'print
unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
