[ 
http://issues.apache.org/jira/browse/JS2-618?page=comments#action_12457272 ] 
            
Woonsan Ko commented on JS2-618:
--------------------------------

Hi Enrique,

Probably I can answer you question on behalf of David.
Here's Ate Douma's answer to my former question:

"""
It is as simple as running something like:
   svn diff > patch-JS2-618.txt
from your jetspeed-2 root folder.
svn will recursively process every file itself for you.
Then, just upload the patch-JS2-618.txt file and I'll take care of the rest :)
"""

Actually, the 'patch' command will take care of your patch, regardless of 
David's preferences. It's very powerful!

> Migration from Spring 1.1.x to Spring 2.0
> -----------------------------------------
>
>                 Key: JS2-618
>                 URL: http://issues.apache.org/jira/browse/JS2-618
>             Project: Jetspeed 2
>          Issue Type: Improvement
>          Components: Security, Components Core, Dependencies, 
> Assembly/Configuration, Persistence and DAO
>    Affects Versions: 2.0-FINAL
>         Environment: Linux Ubuntu 6.06, Tomcat 5.5, JDK 1.5, PostgreSQL
>            Reporter: J.Enrique Ruiz
>         Assigned To: David Sean Taylor
>         Attachments: j2-spring-migration-OJBHelper-patch.zip, 
> j2-spring-migration-patch.zip
>
>
> We have download the Jetspeed2 2.0 sources and we have done some changes to 
> migrate to Spring 2.0. We have not tested it thoroughly but, the first tests 
> have worked perfectly.
> Attached, we have included a zip file containing the patches and a guide that 
> describes the steps to migrate Jetspeed2 from Spring 1.1.x to Spring 2.0

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to