+1 to deprecation. IMO the change isn't really that big. At least it isn't very disruptive in user code. Even less so if we add the addModuleDescriptor() you propose, which I think would be reasonable.
--knut On Sat, 11 Sep 2004 09:40:43 -0400, James Carman <[EMAIL PROTECTED]> wrote: > I understand that. But, what if users DO use it? What happens when we > release 1.1 with these features in there that eliminate the processModule() > methods in RegistryBuilder and replace them with another method like > addModuleDescriptor()? I guess one solution would be to "cripple" > RegistryBuilder by ONLY allowing constructDefaultRegistry(). Then, in 1.1, > we would allow it to be more robust. Another solution would be to deprecate > the other stuff in the 1.0 release telling users that there will be a > different mechanism for customizing the registry in 1.1 (use at your own > discretion). Maybe the deprecation would be better, since there are > actually users out there already using it. > > > > -----Original Message----- > From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] > Sent: Saturday, September 11, 2004 9:30 AM > To: [email protected] > Subject: Re: [RESULT] Release HiveMind 1.0-rc-2 > > I'm not sure how the internal restructuring will affect users, even if > it widely affects HiveMind? Typical users will use HiveMindFilter or > RegistryBuilder.getDefaultRegistry() and those will likely not change. > The extra options will only be visible to advanced users. > > I really don't want to hold up 1.0! > > On Sat, 11 Sep 2004 09:06:47 -0400, James Carman > <[EMAIL PROTECTED]> wrote: > > Are we going to address these new ideas before 1.0 release? If we really > do > > re-structure the RegistryBuilder, that's quite a dramatic change to the > core > > of HiveMind and should probably be done before an official release of 1.0. > > I think it's a nice clean-up/refactoring and will make things more > > understandable or intuitive (and easier to describe in an article). > > > > > > > > -----Original Message----- > > From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] > > Sent: Saturday, September 11, 2004 9:03 AM > > To: [email protected] > > Subject: [RESULT] Release HiveMind 1.0-rc-2 > > > > Howard Lewis Ship: +1 (binding) > > Harish Krishnaswamy: +1 (binding) > > Knut Wannheden: +1 (binding) > > Erik Hatcher: +1 (binding) > > James Carman: +1 (no response) > > > > I'll get started on the label and the release! > > > > ---------- Forwarded message ---------- > > From: Howard Lewis Ship <[EMAIL PROTECTED]> > > Date: Sat, 4 Sep 2004 10:52:03 -0400 > > Subject: [VOTE] Release HiveMind 1.0-rc-2 > > To: [email protected] > > > > The system works ... we've found and fixed a few bugs in rc-1. > > > > Here's the fixes: > > > > http://issues.apache.org/jira/browse/HIVEMIND-44 > > http://issues.apache.org/jira/browse/HIVEMIND-47 > > http://issues.apache.org/jira/browse/HIVEMIND-48 > > http://issues.apache.org/jira/browse/HIVEMIND-49 > > > > I'm pretty sure we've nailed the mutithreading and class loading bugs > > at this point. It's now time to get exposure on those fixes in the > > form of rc-2. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- > Howard M. Lewis Ship > Independent J2EE / Open-Source Java Consultant > Creator, Jakarta Tapestry > Creator, Jakarta HiveMind > http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
