Page History

...

The below dependencies may no longer be needed, as it seems like we have a valid way to replace them in the future.

• dspace-tm-extractors (used by dspace-api to do text extraction of Word docs) - Can we just replace this with POI (http://poi.apache.org/), which is used for PPT text extraction (but also looks to work for Word docs)? See DS-1140
• dspace-jmockit (dependency of dspace-parent) - JMockit is now in Maven Central, as long as we can upgrade to 0.999.11 or above. So, we may no longer need this separate project.

...

• Make existing SVN READ-ONLY
• Archive the existing SVN (scm.dspace.org hosted by OSUOSL) to http://svn.duraspace.org for posterity.
• Post a notice in the archived SVN (at svn.duraspace.org) that codebase is now at GitHub

Additional Cleanup tasks

• Turn off any syncing between SVN and GitHub
  • Notify the Committers before making this change!!
• Ensure Maven 'License Header' check still works when running 'mvn install' (this is setup in 'dspace-pom')
  • Likely will need to move LICENSE_HEADER to GitHub, maybe into same project as 'dspace-pom'?
  • Also will likely require a new release of 'dspace-pom'
• Ensure Maven Release Procedure still works - likely will require a POM update or two.

Mark: I've run a few releases via sonatype and github, it might be good to run a test release or two just to verify.  We just need to update the source management section of the maven parent Pom. I have examplespf these settings in my repo.

Final Steps

• Notify community when development has moved completely to GitHub.
• Redirect old SVN URLs:
  • Redirect scm.dspace.org to svn.duraspace.org (if possible, setup this redirect so that old URLs just go directly to that SVN archive)
• Contact OSUOSL and let them know we no longer need to use the old SVN server.
• (In process/ongoing) Build some "GitHub Best Practices" documentation @ Development with Git
  • Need to also update or delete Tracking your source code with Git

...