[Cosmo-dev] split open and melt

[Randy Letness]

Sounds good.  When you say split the pim and account browser, do you 
mean making  those separate .war files?  I also would like to create a 
separate module for all our ical4j extensions.  I tried to do this for 
.7 but with all my maven knowledge (almost none) I couldn't quite get it 
working.

-Randy

Brian Moseley wrote:
> those attentive to the svn commit list may have noticed that i created
> a branch named "split" earlier today. i'm using this branch to explore
> the idea of splitting the cosmo subproject into several subprojects,
> as we discussed in a thread earlier this week.
>
> my first step is to tease the model and service apis apart from the
> Hibernate storage implementation. this will let us package the api
> interfaces and classes in one jar and the Hibernate classes in
> another. then the pim, admin, and protocol subprojects, when they are
> split apart, will only have to compile against the api jar. more
> importantly, the unit tests for these subprojects will run very
> quickly, since we won't have to wait for the Hibernate unit tests to
> start up derby and load all of the spring beans from the various
> layers. i'm probably going to need Randy's help to make sure
> everything works as it should after the split.
>
> once we get that partitioning done, then i'm going to split the pim
> (including the account browser) out into its own subproject. this will
> require Bear's help to get the dojo js stuff and the war:inplace stuff
> working correctly.
>
> if we have time after that, i'll also pull the admin ui and the dav,
> feed, and cmp bits out into their own subprojects. these are lower
> priority, but it would still be nice to have the capability of
> building them separately, even if we always release them together.
>
> i think this its' probably 5-7 days of effort on my part to get all
> this working, plus maybe a day or two each from Randy and Bear. if all
> goes well, we may try to drop this into the .10 bucket.
>
> any thought