I second this! I've used Artifactory and liked it. (I somewhat prefer Nexus, at least the last time I looked at Artifactory.)
-K On Aug 6, 2010, at 1:47 PM, Yoav Landman wrote: > You may want to take a look at the CI integration in Artifactory - > http://wiki.jfrog.org/confluence/display/RTF/Build+Integration > You can get a json object with a report of all this information captured at > build time: detailed build environment information, published artifacts and > resolved dependencies of all scopes. > Like many have commented here, re-downloading cached release artifacts if > you run your build from scratch should be done from the caches of your repo > manager. > > Yoav > > On Sat, Jul 31, 2010 at 12:07 AM, Shan Syed <shan...@gmail.com> wrote: > >> no, this isn't in regard to our own published artifacts >> >> I regret starting this thread, I apologize >> I didn't mean this question to be an affront to maven conventions - I just >> need to figure out a better way to capture a full log >> they even want a log of how the build environment was downloaded and >> installed >> >> >> On Fri, Jul 30, 2010 at 5:04 PM, Paul Benedict <pbened...@apache.org> >> wrote: >> >>> There is a maxim to follow when deploying: "do not redeploy a version >> more >>> than once". Once you deploy version X.Y.Z, it should never be updated, >> and >>> those who download it never need to download it again. So, back to the >>> original problem, are you guys doing that? >>> >>> On Fri, Jul 30, 2010 at 3:57 PM, Shan Syed <shan...@gmail.com> wrote: >>> >>>> it only applies to our final release cuts, not our day-to-day >>>> just once for this project really; I wanted to insert such this switch >>> (if >>>> existed) in our "delivery build" profile >>>> we use archiva for everything else, and actually only make use of >> public >>>> maven repositories when we up a version of our dependencies, which is >>> rare >>>> because of change control >>>> >>>> it's all weird stuff, I know, but sometimes I just don't question it >>>> >>>> On Fri, Jul 30, 2010 at 4:51 PM, Wayne Fay <wayne...@gmail.com> wrote: >>>> >>>>>>> deleting the m2 works, I was just curious to see if there was a >>> switch >>>>> in >>>>>>> maven to force all downloads again >>>>>> >>>>>> This makes absolutely no sense, doesn't change your BOM, and is >> just >>>>>> wasteful. Consumes bandwidth unnecessarily from a resource that is >>>> being >>>>>> used by the whole Maven community. >>>>> >>>>> I'd think that if you had enough developers doing this on every >>>>> machine on a consistent basis (eg every build), it might add up to >>>>> enough traffic to get you on a blacklist somewhere... You really need >>>>> to install Nexus or another MRM, this is just plain dumb. >>>>> >>>>> Wayne >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>>>> For additional commands, e-mail: users-h...@maven.apache.org >>>>> >>>>> >>>> >>> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
