Thank you Axel. As usual, your responses are really helpful. But I think your answer still misses my main point, which is that all a person has to do to get a clean release is to use the 201605GA release.
I think there are three sources of confusion:
Thank you for giving me the opportunity to clarify how this works. Hopefully it helps others understand our thinking. We are open to suggestions for improvements.
Your explanations are fine for a casual user that should normally not care about the low-level, technical versions. But when someone asks regarding the technical versions I will focus my answer on these, and regard the GA/EA numbers as "marketing versions".
You are right, Share and Repository do not have to match - but if you want to have the latest of both (5.1.g) you have to do it manually. And 5.1.g was mentioned as the target version by the original poster. I did not intend to discourage to use any of the releases "as-is" - I just focused on the steps necessary to get a clean, pure 5.1.g setup, which is hindered by the fact that the org.alfresco:alfresco:war:5.1.g Maven artifact contains 5.2.a repository JARs, which is confusing - and frankly incorrect - because the version number of included share-services defines the version of a Repository artifact in this case. It would all be perfectly fine if that Maven artifact was tagged as the 201606EA instead of 5.1.g.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.