#orderofthebee

#alfresco is quieter than it has been, the community has done an amazing job at renovating that channel

so anyway, if you have installed honeycomb, you get voice in the irc channel, there is no restriction on being able to speak, but you get the extra status of a +v <-- is my proposal

haha, well more eyes on the build will help, everybody :)

^^ and for that we want some kind of hashing of user identity + something in the install to generate an id we can validate in order to grant +v

let me raise a ticket for 1.1

perhaps 1.2 :)

haha no it is probably easy to do, and it would be me verifying the result, so I can use it as some motivation to get back onto honeycom build again instead of all this messing about with docker and clustering

marsbard: Hmm - seems I have to install Honeycomb just for status' sake then...

marsbard: And since you asked to be corrected: "it was perfectly reasonable to compile a java 7 compatible artefact using java 8" => That assumption is precisely the cause of the issue. It is never 100% safe to attempt to build a Java 7 compatible artefact using anything above Java 7.

Java build is never just about language version compatibility - it is always also an issue of core library version compatibility. Even if you set a Java X to compiler level X-1, you'll still compile against a core library version X that is more advanced than X-1 and causes issues (missing methods / changed signatures) when artefact is run against X-1

Java (Sun / Oracle) only guarantees that a Java release is backwards compatible, i.e. you can run an artefact built against X-1 on version X - the opposite has never been true.

All of the time that someone (claimed to have) "successfully" built an artefact the way Alfresco did for 5.0.d - it was sheer and utter luck that they didn't fall on their arses.