At the moment I have no idea which tool is causing the problem. I still have
problems with artifactory 2.3.1. Just a quick question: Does artifactory 2.3.0+
supports the m3 format with both, unique and non-unique repositories? Currently
the build system is running with 2.3.1 and non-unique snaps
I could imagine the culprit could be artifactory. We were forced to update from
2.2.2 to 2.2.3, otherwise we weren't be able to deploy with maven 3.0 (metadata
issue in Artifactory 2.2.2, deploy worked only in legacy mode). In the meantime
just to be sure, we updated to 2.3.1. But were also requ
They are from snapshot artifacts. We use non-unique snapshots in artifactory.
The sources are deployed on the same time like the compiled artifacts. So the
timestamp should be equals, shouldn't it?
If not, how could I archieve it?
-Chris
-Ursprüngliche Nachricht-
Von: Stephen Connolly [m
