wtSafeArea - siteMod best practices?
My reading of the Windchill Customization Guide guide tells me that the siteMod folder under wtSafeArea is intended for modifications to all OOTB file. Can anyone share with me a good reason why we would store all (OOTB modified files + custom new files) in this location? To me it's a mess. This folder is there for the upgrade process to read and generate the required file updates for OOTB files,
Before I launch a campaign with my team to clean this up, please let me know if there is actually a good reason, benefit to keeping your files this way. My stance otherwise is we move all non-OOTB files out of there and shift the focus to improving our GIT repo management habits.
From the Windchill Customization Guide page 102: support.ptc.com/WCMS/files/171950/en/11_0_M20_WindchillCustomizationGuide.pdf
- The following summary describes the purpose of each subdirectory:
- siteMod – contains the site version of each PTC file that you have modified and
want to run in production.
- siteMod – contains the site version of each PTC file that you have modified and
We are in the process of maturing our GIT code management practices and currently my organization is storing ALL source files under wtSafeArea/siteMod. Reasons why I don't like this:
- DRY (don't repeat yourself)
- Every *.java file is duplicated to the wt_home\src and the wt_home\wtSafeArea\siteMod\src
- The duplicate files are invariably out of sync
- Every *.java file is duplicated to the wt_home\src and the wt_home\wtSafeArea\siteMod\src
- This just feels like someone over-adopted, over-corrected the wtSafeArea, probably at a point in time prior to GIT process being fully understood, external repos with deployment scripting in place etc. Holdover from pre-GIT / externally managed repo days.
- ie. treating siteMod as a file repository
Thoughts?

