Shibboleth Developers

[Chad La Joie <>]

I agree, these things, and probably some others, need to be added to the ignore 
list.

While I didn't specifically mention this, one of the main drivers (in my mind) 
for moving to SVN is that is version directory structure.  This was important to 
me because some of the changes I'd like to make are in the structure of the 
source tree itself to make it a lot simpler to find stuff.  If I can convince 
Walter (or get it done before he gets back from vacation ;)) some of these items 
will fall out naturally.

Basically, now that we've moved to SVN prepare to see this stuff get ripped up 
as we begin Shib 2.0 development.  :)

Will Norris wrote:
> Looks good.  One small thing I never bothered with mentioning before... 
> could a few additions be made to "svn:ignore" ?
>  - custom/lib
>  - custom/web
>  - dist
>  - lib/shib-util.jar
>  - webApplication/WEB-INF/classes
>  - TEST-*.txt
>
> any reason why these shouldn't be globally ignored with regard to cvs/svn ?
>
> -will
>
>
> On Jun 21, 2006, at 11:11 AM, Chad La Joie wrote:
>
> > This migration has been completed.
> >
> > New instructions for accessing the new Subversion repositories can be 
> > found here:
> >
> > https://authdev.it.ohio-state.edu/twiki/bin/view/Shibboleth/SourceAccess
> >
> > NOTE: Only the Java Shibboleth code is currently moved.  The C++ 
> > Shibboleth as well as the Java and C++ OpenSAML 1.X code transition 
> > schedule will be posted in the future.
> >
> > Chad La Joie wrote:
> > > As some of you may know, we've been using a Subversion server to 
> > > house the new OpenSAML 2 code.  To date I'd say the developers have 
> > > been very happy with it. Our plan has been to migrate the current 
> > > Shibboleth CVS repositories to Subversion as well.  We are currently 
> > > planning on moving the *Java* IdP/WAYF code on Wednesday, June 21st.  
> > > Write access will be locked out at 7 a.m. (EDT) and I'll begin doing 
> > > the move around 1 p.m. after we have taken backups and performed 
> > > final configuration items.
> > > Information on using Subversion can be found on the Subversion 
> > > website (subversion.tigris.org) or, if you use Eclipse, you may find 
> > > these directions helpful:
> > > https://authdev.it.ohio-state.edu/twiki/bin/view/Shibboleth/OSTwoDevManJavaSetup 
> > > All history, branches, and tags will be moved over.  Our current plan 
> > > is to create three repositories.  A read-only snapshot of the current 
> > > repository, a read/write copy that will eventually contain only the 
> > > IdP code and a read/write copy that will eventually contain on the 
> > > WAYF code.  In addition, a new, empty, repository will be created for 
> > > the to-be-developed Java SP.
> > > Here are the URLs for the new repositories:
> > > SVN Root URL:
> > > https://svn.middleware.georgetown.edu/[MODULE]
> > > Web View URL:
> > > http://svn.middleware.georgetown.edu/view?root=[MODULE]
> > > Where [MODULE] is:
> > >    java-idp - For the IdP code
> > >    java-wayf - For the WAYF code
> > >    java-sp - For the Java SP code (this will be empty)
> > >    java-cvs-snapshot - For the read-only snapshot
> > > An immediate benefit individuals will see is that updates made by the 
> > > developers will be immediately available to anonymous users; no more 
> > > lag time while the read/write store is synced to the anonymous read 
> > > store.
> > > If you have any questions regarding this move please send them to the 
> > > list and I'll answer them as soon as I can (I'll be in meetings most 
> > > of Monday).  Further information will follow on the plans to move the 
> > > C++ SP and the Java and C++ OpenSAML 1.X code.
> >
> > --Chad La Joie             2052-C Harris Bldg
> > OIS-Middleware           202.687.0124