...
- Jars contained the source of the jar so it could be easy and low risk to debug/patch
- Jars had names of the jar without the version in the name so that version control would show a history on the file
- Dev target in ant would copy jars to webapp folder so the application could be debugged without a warfile. Note, source is in jar so it can be easily debugged
- The hibernate jar was patched, not sure which others
- All versions are in the manifest of the jar. If the jar doesnt put it in there by default, it was added by grouper developer
- Grouper will check the size and version of jars on startup and warn which ones arent right
- Grouper installer will try to look for jar conflicts
Notes of call 11/3/2015 (Misagh, JJ, Jasper, Dima, Chris)
- Dima took first pass at gradle
- Converts maven to gradle
- Each project has its own gradle file
- grouper-parent will compile subprojects
- If there is a non standard structure we can specify in gradle script
- gradle branch at github in unicon
- Parent script is: https://github.com/Unicon/grouper/blob/gradle/grouper-parent/settings.gradle
- Issue with misc stuff that is not common, do we gradlize it? move to different branch?
- Get rid of grouper-parent, move stuff to parent dir
- grouperw is the wrapper to download gradle and run it
- gradle replace installer? Need to discuss this since installer has features
- need to externalize dependency versions so the gradle properties dont have repetition on log4j for example
- gradle plugin to create projects for IDE's
- can you download all jars and sources, two line script, lets get this in
- system jars, find dependency for custom jars (hibernate)
- manipulate jar manifest for implementation-version? do checksums of jars?
- offline builds? would tarballs have jars in it? might be able to
- grouper ui not in maven central. grouper ui java in different project than jsp?
- artifactory is proxy for dependencies
...