new naming conventions: watch your step

[Ian Young]

Just a word of warning for people doing refactoring of *class names* to fit the new conventions. This is probably "well, d'uh" stuff for most of you, but it burned me recently.

If you are on a system with a case-insensitive file system (certainly Mac, probably Windows) and perform a class refactoring in Eclipse, it doesn't do everything you'd like.

For example, if you refactor SamlThing to SAMLThing and commit to subversion, it will *add* SAMLThing.java but it will not remove SamlThing.java. At some point you will find that on machines other than the one you did the refactoring operation on end up with subversion cache inconsistencies within Eclipse. This is because in the repository, both SAMLThing.java and SamlThing.java still exist.

Deleting your workspace and downloading the project again does not fix this. I found that the simplest fix was to fire up a Linux machine (with a case-sensitive file system), check the project out and manually "svn remove" the old-convention files.

	-- Ian



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5943 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/dev/attachments/20131016/df3132d7/attachment.bin