Page History

1. when certain type of tag, e.g. GROUPER_RELEASE_2_5_0 (tags can have dots right?  or underscore?).5.8, it would make the real release jars
   1. Travis sees tag, pulls down source code
   2. Runs mvn versions command to assign version locally (in git in pom the version is 2.4-SNAPSHOT)
   3. Compile 
   4. e.g. grouper-2.5.08.jar
   5. Publish to staging branch
   6. Manually release it in maven (whoever tags to do this)
   7. Automatic automatic ci/cd based on tag format (low priority)
2. publish to maven central automatically (low priority)

1. Remove 3rd party jars from git
2. Add the git dependency command in readme
3. "ant dev" to get jars from dependency jars and copy to webapp/WEB-INF/lib

Each project should have

1. normal classfile jar
2. source jar (low priority)
3. test jar (low priority) (if there are test classes)
4. test source jar (low priority) (if there are test classes)
5. javadoc jar? (low priority)

every commit, compile everything and run tests (low priority)

can there be a notification if build breaks (to core list)? (low priority)

nothing

Instead of hard coding grouper version we would get that from manifest from jar

can we have a script to change things in git after version?  need to change poms?  something in java or resource? 
dont want to forget something, script would be nice

or... can all poms use a variable from the parent pom so we change the version in one place?

1. should build everything in grouper, using local filesystem builds as dependencies
2. e.g. if something in grouper is dependent on something in grouper client, and that isnt in maven yet, the build should succeed
3. only build from parent (assumption)

get maven working on client jars.  ant currently works for this, see build.xml

1. src/ext should be compiled with jars in lib dir ( and not the client source) src/java should be compiled with src/ext on classpath and no jarssrc/extMore should be compiled with src/java and src/ext on classpath, nothing elseno dependencies
2. src/testSource can use all of above and jars
3. low priority, see if shade can easily (not take a lot of time to get working),
   manage the "ext" source jars to be put in the same classpath (since used elsewhere)

get maven making the grouper jars

1. grouper depends on client
2. source dir and test dir, pretty simple

get maven working for ui jars

1. ui depends on grouper (and transitively, client)
2. source dir and test dir, pretty simple

get maven working for ws jars

1. classfile jar has source from: src/grouper-ws, src/grouper-ws_v2_0, ... , src/grouper-ws_v2_4 (not there yet but will be)  all the src dirs
2. test jar has source from: src/test, (low priority) grouper-ws-java-generated-client/src?, (low priority) grouper-ws-java-manaual-client/src/java-manual-client?, (low priority) grouper-ws-test/src/test?

this is grouper-ws/grouper-ws-scim, get maven working for jars

1. source and test dir, not too complicated
2. add dependent jars to project