Hi Serge, Take a look at issue: http://nagoya.apache.org/jira/browse/JS2-30
Right now, to expedite refactoring, I am going to put things into commons, but I am definitely +1 on an "api" or "core" sub-project containing only interfaces and exceptions. After the component refactoring, we can start on segregating "api" from "commons." On Wed, 2004-05-19 at 12:06, Serge Huber wrote: > At 16:48 19.05.2004, you wrote: > >While I'm +1 on moving the interfaces out from the component > >implementations, I'm not so sure about moving them into commons. > > The other problem I have with commons is that it seems to become a place > where anything global goes, with no real structure. Maybe we should create > a "interfaces" or "apis" project ? > > Regards, > Serge Huber. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- ****************************************** * Scott T. Weaver * * <[EMAIL PROTECTED]> * * <http://www.einnovation.com> * * -------------------------------------- * * Apache Jetspeed Enterprise Portal * * Apache Pluto Portlet Container * * * * OpenEditPro, Website Content Mangement * * <http://www.openeditpro.com> * ****************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
