Spice-* and Loom

One thing I have been thinking about is what we should do about the
relationship between loom and spice-xmlpolicy, spice-extension and
spice-classman. They are all very specific to loom and in retrospect are
unlikely to be used anywhere else. What I was thinking was that we could
migrate into loom package hierarchy. It would not be any real change for
anything but hopefully then we can reduce extra work of maintaining
separately. Ie We would end up merging all the docs into Loom website but
everything else will stay separate.

Cheers,

Peter Donald

*-----------------------------------------------------*
* "Faced with the choice between changing one's mind, *
* and proving that there is no need to do so - almost *
* everyone gets busy on the proof."                   *
*              - John Kenneth Galbraith               *
*-----------------------------------------------------*

> -----Original Message-----
> From: jcontainer-interest-admin-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org [mailto:jcontainer-
> [email protected]] On Behalf Of peter royal
> Sent: Monday, March 29, 2004 10:02 PM
> To: jcontainer-interest-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org
> Subject: Re: Release
> 
> On Mar 28, 2004, at 9:59 PM, [email protected] wrote:
> > While we are waiting for MetaClass infrastructure @ Codehaus to be
> > created
> > is there anything else that needs doing in jcontainer that I can hack
> > on?
> 
> I somewhat re-organized the issues in jira.. after talking with mauro
> most of what i have slated for 1.0 can really be pushed to 1.1 and then
> a 1.0 can be cut sometime soon... maybe take a peek in there and see if
> there is anything that needs doing that interests ya
> -pete