Add OSIAM Shell to main distribution

[tkrille]

see osiam/shell#1.

[sschum]

I think we have the following options:

• Only add the runable jar file into the distribution.zip (where all other components are stored)
• Make a own zip-pagage for shell (then we can outsource the lib jars into a seperate folder, but we need a start-script)

[tkrille]

what about a fat- (or uber-) jar? this way you can start it just like this in a terminal:

$ ./osiam-shell.jar

given that one has installed binfmt stuff beforehand. nevertheless, we can still provide a start script too. i don't think we should distribute every single jar-packaged dependency - it just feels totally antiquated to do so.

[tpick]

+1 for uberjar

[tkrille]

i just looked at the pom and you are already create a jar with all dependencies contained via the maven-assembly-plugin. the resulting artifact is also already taken for the main artifact and will be installed and certainly deployed, too, during the normal maven lifecycle, though i have not tried to deploy it yet. maybe this can further be improved by using the maven-shade-plugin? i think it's better suited for the job.

i think we should also make a separate distribution of the shell, if we want to not only ship a runnable jar but also a start script or other supporting files.

but we should move this discussion to https://github.com/osiam/shell. i opened these 2 issues: osiam/shell#4, osiam/shell#3

[wallner]

I'm closing this issue, since discussion is taking place in osiam/shell#3