Re:Many packages suddenly disappeared
by tomjakubowski on Saturday January 06, 2018 @03:38PM
(#16087314)
I’ve worked at places where the Java devs used Maven Central directly. I’ve also worked at a place where the Node devs use an on-premises copy of dependencies for builds and deploys.
It might not be as standard a practice in the Java world as you think.
Where did those Java devs who pulled from Maven central directly publish their artifacts?
Re:Many packages suddenly disappeared
by stephengillie on Saturday January 06, 2018 @10:23PM
(#16088939)
Possibly Sonarqube Nexus. The Java devs at my workplace use Sonarqube along with Jenkins and Maven on the same server. I believe they communicate through the shared directory on the file system.
(Pet peeve: another product named "Nexus". Please choose original names for your software.)
It's Sonatype Nexus, Sonarqube is the code quality checker.
It is at big orgs, but not small shops.
Re:Many packages suddenly disappeared
by usernam33 on Saturday January 06, 2018 @06:11PM
(#16088023)
We do it even at home. Not full dep-server but local backup.
Yes, if your company has Artifactory or similar. I think most of these outraged folks are just memeing.
i use yarn-offline-mirror and save all tarballs in the repository, works fairly well.
We use Nexus at work and have linked up NPM to it along with several Maven repos. I don't know why anyone wouldn't do this if they were a business.
Re:Many packages suddenly disappeared
by james-mcelwain on Saturday January 06, 2018 @03:53PM
(#16087394)
Yes, of course. A centralized repository for a package manager is always going to be a single point of failure.
Re:Many packages suddenly disappeared
by 8n4vidtmkvmk on Saturday January 06, 2018 @04:38PM
(#16087604)
Not "standard", but there's definitely a couple solutions for this. We tried one at my work but it seemed a bit flakey.
Yes, for those who use `yarn`. (Yarn's package caching looks a lot like Mavens)
Re:Many packages suddenly disappeared
by fcarraldo on Saturday January 06, 2018 @03:54PM
(#16087397)
yarn does local caching in developer laptops. What GP is referring to is having an on-prem private dependency server which acts as a cache and proxy to the centralized public dependency repo.
> an on-peen private dependency server
SURELY you meant on-prem, right?
This isn't a standard practice in JS world?