Hi all, When doing a vendor import of the up3 release candidate, I've found several files with inconsistent newlines. While these newline issues aren't visible from an editor like Eclipse, I can see ^M characters in a *nix command line editor, and our subversion exists with inconsistent newline errors upon import.
I'm in the process of identifying these files, and I'm happy to clean them up and commit the changes back to the JA-SIG repository. However, I'm wondering if it might be helpful to provide a default configuration file for uportal configuration work. The Sakai project has distributed something like this in the past, and I think it's generally helpful to have a resource that will automatically set properties like newlines, executable file types, mime types, etc. I've put a wiki page on the subject up at http://www.ja-sig.org/wiki/display/UPC/uPortal+3+Subversion+Configurationand attached my current working uportal file. It could certainly use some work, but I'm hoping this might give us a place to start from. - Jen -- Join your friends and colleagues at JA-SIG 2008 - "Higher Education Solutions: The Community Source Way!" April 27th - 30th, 2008 in St. Paul, Minnesota USA Featuring CAS, DSpace, Fedora, Fluid, Internet2, Kuali, Sakai, uPortal, and more! Information/Registration at: http://www.ja-sig.org/conferences/08spring/index.html Subscribe to the conference blog, The Community Source Way http://jasig2008.blogspot.com, for news and updates about the event. Join the Conference networking site at http://ja-sigspring08.crowdvine.com/ You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
