Folks, > > My current thinking is that we should split the avalon project into a > > 'common', 'spec' and 'impl' project. > > > > Thoughts? > > Seems like we're getting a plethora of subprojects instead of > the plethora of sub-subprojects we had before. > > Can't we just arrange the source code into: > > avalon/src/java/ > | > +- spec/ > | > +- impl/ > > ? > > This would make interface/impl compilation & packaging easier, plus > we get to keep things into one project which should be much easier > than splitting it over three projects.
We're confusing CVS refactoring with real work again (no offence). It would be more Maven friendly with separate project hierarchys. So -1 for incluing any impl of Avalon in the avalon/ tree. - Paul __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
