FYI The code for this is here : https://github.com/roofmonkey/jenkins/blob/master/root/archivainstall/deploy_release.sh Are we sure we DO NOT want DATE in the version ? Just confirming.
I try and put myself in the shoes of a new person from the community coming along and trying to figure out what shim to download. I think the things that need to be clear are: - Is this the component I am looking for? I think we resolve this by having both the Archiva artifact and the artifact versions include the words "glusterfs-hadoop" - How do I figure out which component is the latest one? I think we resolve this by appending an incremental version to the artifact version. i.e. "glusterfs-hadoop-0.0.1" I think this method is clean and simple. This is more about aesthetics, but I think it makes the version name (and subsequent jar file name) look too long and gorpy if it includes the date. Can we not add the publication date of the artifact version as metadata on the page that you get when you click on the artifact version?
MetaData is supported in the newer archiva releases. We will upgrade after this release and keep the ticket open . For now, we will just remove the dates.
I vote to change this to modified (external repos and jar naming fixed) , all that remains is to "bundle documentation", which is a significant undertaking (what docs, java docs? doxygen uml? README? Is packaging going to be RPM based for the docs?) . So ill create a separate ticket for that.