|
From: Juergen H. <ju...@in...> - 2005-06-19 09:10:13
|
Well, I guess the proper naming partly depends on what granularity we're gonna use over here at the core CVS. If we don't go down the fine-grained module route but rather keep things at a course-grained subproject level, "spring-projects" will be perfectly fine. This still hasn't been decided yet, though... Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Erwin Vervaet Sent: Sunday, June 19, 2005 8:10 AM To: spr...@li... Subject: Re: [Springframework-developer] spring modules/spring projects/spring extensions Check the following: http://article.gmane.org/gmane.comp.java.springframework.devel/8723 http://article.gmane.org/gmane.comp.java.springframework.devel/8729 http://article.gmane.org/gmane.comp.java.springframework.devel/8730 So as I understand it we'll stick with "spring-projects" for the time being. Erwin Vervaet erw...@er... ----- Original Message ----- From: Keith Donald To: spr...@li... Sent: Sunday, June 19, 2005 4:52 AM Subject: [Springframework-developer] spring modules/spring projects/spring extensions We need to reach a consensus on what to call our core spring modules repository here at sourceforge and the extension spring modules repository over at java.net. Right now were calling the core stuff spring projects but Im not sure about that usage, modules seems like such a better name However, having two spring modules is obviously confusing. What about calling the core modules spring modules and the work happening over at java.net spring extensions? That seems like an ideal situation. What do you think? Rob? Colin? Juergen? Would it be possible to rename the java.net effort or is it too late for that? Thanks, Keith -- Keith Donald Interface21 Principal Consultant http://www.springframework.com |