Sounds good. I think it would be preferable if you can check in your
changes in smaller working increments instead of all-at-once (assuming
it would take a while to get all the simplifications in) as that would
allow us to make software changes while you're doing the simplifying and
ensure that the Roller checkout always remains buildable and deployable
during the process. However, if you need a complete check-in freeze for
a period of time from the rest of the team just let us know.
Note you may wish to keep a separate weblogger-jar and weblogger-war
submodules if in the future you're expecting a third weblogger-osgi
submodule (which would include weblogger-jar but not the weblogger-war
stuff), or if you're seeing a potential need for separate
weblogger-weblogic, weblogger-websphere, etc., submodules that will
contain container-specific configuration.
But either way is fine with me.
Glen
On 04/06/2013 04:43 PM, Dave wrote:
One thing that makes it really irritating to deal with (and maintain) the
Roller code is the fact that is is needlessly split between 9 different
Maven modules. Would anybody be opposed to combining modules and reducing
the number down to 2? I experimented with this idea in my GitHub
"rollarcus" project here:
http://rollerweblogger.org/roller/entry/rollarcus_9_to_2 and it worked
nicely.
- Dave
