Eviware maven repo
The company I work for allows open-source to be used and shipped, but only after following very restrictive guidelines. We run our own internal Nexus maven repository and it does proxy outside repos. Upon requesting that the eviware repository be included, I was partially denied. They will allow the proxy but only for moduleIds which equal "eviware" and nothing else.
Ole asked via Twitter what could be done to change that and I responded that I'd find out. Here is what I found out.
(1) The repo should only contain their own artifacts and should proxy those they don't own.
(2) Release artifacts must never be changed.
IT also mentions that a policy should define how artifacts are added to the repo. Is there a policy feature for maven repos? I'm not entirely sure what this means.
-tim
Ole asked via Twitter what could be done to change that and I responded that I'd find out. Here is what I found out.
(1) The repo should only contain their own artifacts and should proxy those they don't own.
(2) Release artifacts must never be changed.
IT also mentions that a policy should define how artifacts are added to the repo. Is there a policy feature for maven repos? I'm not entirely sure what this means.
-tim
