Java 9 modules

Gang, Just learning Java 9 Modules, and it will impact us quite a bit I think. The outcome will be nicer, but the entire build structure should change. The good part is that I now see Java 9 as July 2017, so plenty of time. This is just a heads-up to investigate Java 9 Modularity as it will

Build failed in Jenkins: Zest(JavaEdition)-develop-java9-check #9

See Changes: [paulmerlin] Fix Envisage ... [paulmerlin] Upgrade Apache PDFBox dependency from 1.x to 2.0.3 -- [...truncated 5406 lines...]

Jenkins build is back to normal : Zest(JavaEdition)-develop-java8-check #201

See

Re: JPA?

On 19.9.2016 4:40, Niclas Hedhman wrote: I agree that there is always a schema, and I don't think that anyone really disagrees with that. It is more a matter of "rigid" or "flexible" schema. The "rigid" world requires more process overhead to create and evolve, and over time end up with 500

Re: Java 9 modules

To further spin some ideas on the Java 9 Module system, -o-o- Builds -o-o- The build system should become a lot simpler, and we should not need one subproject per produced artifact. Whether we end up with one build project or a handful is not yet clear to me. I think a lot depends on what happens

Re: JPA?

Right, but with a single JSON column you have reduced RDBMS to a KeyValue store. Can the JSON document be indexed in some intelligent way on Postgres? Isn't the SQL EntityStore already doing this in Zest? Love your; "YesSQL" Although I saw another funny meme;l NoSQL 2005 = No freaking SQL