Most of what I'm doing are only deletions since the new modules were
already created when sandbox/javaee5 was merged with trunk. For the
"rework items", I am currently planning to leave the names of the
configurations unchanged. I will change
assemblies/geronimo-jetty-minimal to assemblies/geronimo-jetty6-minimal
to match the other 3 assemblies in naming convention.
Joe
Jason Dillon wrote:
Hrm... I had hoped that refactoring like this would have been delayed
until 1.2 was out the door. As with so many module renames, sync'ing
the 1.2 tree with trunk using SVK is going to be nearly impossible.
Maybe once SVK has more Perforce-like integration tracking then it can
handle renames, moves, but right now I do not believe it can.
--jason
On Dec 11, 2006, at 9:42 AM, Joe Bohn wrote:
In a short while (probably in about 3 hours or so), I plan to delete
the and rename several Jetty items in Geronimo. This is because we
are no longer supporting the j2ee assembly in trunk which IIUC is now
devoted to JavaEE5. There are also a few loose ends for the Jetty
JavaEE5 assembly that need to be finished off and this will make it
easier. Here's what I plan to do (if there are no objections):
Delete:
- geronimo/server/trunk/modules/geronimo-jetty/*
- geronimo/server/trunk/modules/geronimo-jetty-builder/*
- geronimo/server/trunk/modules/geronimo-jetty-clustering-wadi/*
- geronimo/server/trunk/configs/jetty/*
- geronimo/server/trunk/configs/jetty-clustering-builder-wadi/*
- geronimo/server/trunk/configs/jetty-clustering-wadi/*
- geronimo/server/trunk/configs/jetty-deployer/*
- geronimo/server/trunk/configs/dojo-jetty/*
- geronimo/server/trunk/configs/uddi-jetty/*
- geronimo/server/trunk/configs/webconsole-jetty/*
- geronimo/server/trunk/configs/jetty/*
- geronimo/server/trunk/assemblies/geronimo-jetty-j2ee/*
Rework/rename/etc... as necessary for Jetty6
- geronimo/server/trunk/configs/welcome-jetty/*
- geronimo/server/trunk/configs/remote-deploy-jetty/*
- geronimo/server/trunk/configs/ca-helper-jetty/
- geronimo/server/trunk/assemblies/geronimo-jetty-minimal/*
There will still be some more potential cleanup:
- Removing the geronimo-boilderplate-j2ee and including content in
geronimo-boilerplate-jee5? We could keep the j2ee one around but I'm
not sure there is much value. thoughts?
Thanks,
Joe