Grouper dev and container strategy for 2.5

Developer workflow

packagingDeveloperWorkflow

Maven central jars

On each commit, snapshots will be committed

packagingSnapshot

On tag, release the jars

packagingMavenRelease

Build container

packagingContainerBuild

Maven tasks

Compile and jar will be done in maven. Jars will be housed in maven central.

Maven is not needed by anyone except the CI/CD or script that maven compiles and stores jars to maven central. devs dont need it. container doesnt need it. plugin devs need to get jars from maven. institutions running grouper dont need maven.

Task	Description	Progress
no snapshots
build versions	when certain type of tag, e.g. GROUPER_RELEASE_2_5_0 (tags can have dots right? or underscore?), it would make the real release jars e.g. grouper-2.5.0.jar automatic ci/cd based on tag format (low priority) publish to maven central automatically (low priority)
build jars	Each project should have normal classfile jar source jar (low priority) test jar (low priority) test source jar (low priority) javadoc jar? (low priority)
notification	can there be a notification if build breaks? (low priority)
what needs to change after build?	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?
maven grouperParent	should build everything in grouper, using local filesystem builds as dependencies e.g. if something in grouper is dependent on something in grouper client, and that isnt in maven yet, the build should succeed
maven grouperClient	get maven working on client jars. ant currently works for this, see build.xml 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 jars src/extMore should be compiled with src/java and src/ext on classpath, nothing else src/testSource can use all of above and jars 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)
maven grouper	get maven making the grouper jars grouper depends on client source dir and test dir, pretty simple
maven grouper ui	get maven working for ui jars ui depends on grouper (and transitively, client) source dir and test dir, pretty simple
maven grouper ws	get maven working for ws jars 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 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?
maven grouper scim	this is grouper-ws/grouper-ws-scim, get maven working for jars source and test dir, not too complicated add dependent jars to project
maven pspng	should be ready to go right?
maven box connector
maven installer	note, we should just move this to the client, right?
maven duo connector
maven activemq messaging connector
maven aws messaging connector
maven rabbitmq messaging connector
maven remedy connector
maven voot	move this into ws?

Ant tasks

Ant can be used for various minimal tasks and for packaging up tarballs. Maven is used for compile/jar

Ant task	Description	All projects or just some
checkDependencies	see if grouper, grouper client, or whatever dependencies are there	most
dev	copy jars to webapp/WEB-INF/lib	webapps
makeContainer	make the dir for	grouper api. download jars from maven central with ant-maven plugin (grouper jars and third party jars). make the uber webapp dir that contains everything. should be ready for docker container. assume everything is checked out from git.
java2wsdl	take javabeans make ws wsdl	ws

Page tree