[Springframework-developer] =?iso-8859-1?Q?Re:[Springframework-developer]_Spring_sub-projects?=

[=?iso-8859-1?Q?<jp....@ti...>]

+1=0D=0AJean-Pierre=0D=0A=0D=0A---------- Initial Header -----------=0D=0A=
=0D=0AFrom      : spr...@li...=0D=
=0ATo          : <spr...@li...>=0D=0AC=
c          : =0D=0ADate      : Mon, 16 Feb 2004 09:58:58 +0100=0D=0ASubje=
ct : [Springframework-developer] Spring sub-projects=0D=0A=0D=0AEverybody=
,=0D=0A =0D=0AAs recently discussed in private mails, I suggest to keep s=
ub-projects that are close to the Spring core as separate modules in Spri=
ng's main CVS. The first two candidates are:=0D=0A =0D=0A- Keith Donald's=
 Spring Rich Client Platform=0D=0A- Torsten Juergeleit's Spring Eclipse P=
lugin=0D=0A =0D=0ABoth Keith and Torsten are in favor of hosting them in =
our main CVS. So if noone objects, I will create new CVS modules "spring-=
rcp" and "spring-eclipse", and accordingly give Keith and Torsten commit =
rights for the main CVS. As the module names cannot be changed easily, fe=
el free to suggest different names!=0D=0A =0D=0AThe rationale is to keep =
all projects that use "org.springframework" as package name in Spring's m=
ain CVS. Separate modules make sense to let the sub-projects evolve indep=
endently; this way, they do not have to be released in direct accordance =
with the Spring core. Of course, generic classes that emerge can still go=
 into the core.=0D=0A =0D=0AConsequently, both sub-projects should also g=
et respective sections on our main website. We should definitely clarify =
all this before 1.0 final (March 1st), as I expect quite a lot of media c=
overage at that time - we shouldn't miss that chance!=0D=0A =0D=0AJuergen=
=0D=0A=0A=0A********** PROTEGEZ VOS E-MAILS !********** =0AAvec Tiscali S=
uperMail, vos e-mails en toute s=E9curit=E9 ! =0AAnti Spam personnalisabl=
e =0AAnti Virus actualis=E9 en permanence =0Aet de nombreux bonus... =0AP=
our en savoir plus, rendez-vous sur http://www.tiscali.fr/supermail/=0A