[Springframework-developer] CVS pruning

[Colin S. <col...@ex...>]

As per the email below, I am going to submit a support request to SF to 
remove the following obsolete or wrongly checked in modules from 
Spring's CVS on SourceForge:
-  'Spring' (this is an empty module created with the wrong case, not to 
be confused with the main Spring source, in the 'spring' module)
- 'common-build'
- 'repository'
- 'spring-binding'
- 'spring-modules'
- 'spring-rcp' (this is the old home of Spring-rcp (which is now hosted 
in it's own sourceforge project, 'spring-rich-c')
- 'spring-webflow'
- 'spring-ide' (this is the old home of Spring-IDE, which is now hosted 
in it's own Subversion repo elsewhere, managed by Torsten and co.).

This should leave the following modules in place
- 'i21'
- 'samples'
- 'spring'
- 'spring-beandoc'

I have no idea if SF will honour such a request from any project 
developer, or it needs to be one of the leads (Rod or Juergen in our 
case). If I'm told it's the latter, I'll notify Rod and Juergen to send 
in the request themselves.

Colin


Colin Sampaleanu wrote:

> Yes. I'm just getting confirmation from Torsten/Christian that the old 
> spring-ide module in CVS can be kileld (all the Spring-IDE) source is 
> in their own Subversion repo now, then I'll publish a list of what 
> modules are staying and which are being pruned, and submit a service 
> request to SF.
>
>
> Erwin Vervaet wrote:
>
>> Okay, I've moved my Eclipse over to use the new spring-projects module.
>> So I guess we can have the SF people clean up those bogus modules?
>>
>> Erwin Vervaet
>> erw...@er...
>> ----- Original Message ----- From: "Colin Sampaleanu" 
>> <col...@ex...>
>> To: "Keith Donald" <ke...@in...>; "Erwin Vervaet" 
>> <erw...@er...>
>> Cc: <spr...@li...>
>> Sent: Friday, June 17, 2005 4:44 AM
>> Subject: Building webflow under spring-projects
>>
>>
>>> Keith/Erwin,
>>>
>>> I moved (copied really) all common-build, spring-binding, and 
>>> spring-webflow sources to live under a new spring-projects module in 
>>> CVS.
>>>
>>> Note that the build relies on the use of a nightly snapshot of ivy
>>>   ivy-20050616204129.jar
>>> which may be found in
>>>   spring-projects\repository\jayasoft\ivy\jars
>>> This should be dropped into your ant lib dir to replace the older 
>>> ivy 1.1. This If you try to use ivy 1.1 you'll get a failure when 
>>> trying to do a publish of the generated artifact.
>>

-- 
Colin Sampaleanu
Interface21 Principal Consultant
Spring Training, Consulting and Support - "From the Source"
http://www.springframework.com