Anders is right and that should be acceptable to people whose paranoia
is matched by their technical know-how.
If not, it would seem that doing a build with a dummy project that
included all of the dependencies that you need including the maven
plug-ins, on the machine connected to the internet would populate the repo.
Very simple POM file.
The machine could then be disconnected from the Internet and used as a
repo internally.
This could be done fairly easily if the server has 2 Ethernet ports and
you could just unplug one or the other depending on where you want to be.
Should satisfy your security guys and not piss off the Maven Central
people who can blacklist you if you try a total scrape of Central.
You may have to do the switch fairly often until you get your dependency
list settled but it should not take too long to get it right.
The maven plug-ins may change fairly often but usually you do not need
very many if you construct your projects in a sensible way and you may
not always have to use the latest version unless one of the bug fixes
applies to you.
It will be a lot more overhead than most of us would like but that is
just one of the costs of high levels of paranoia.
Do you ever watch the closing scene in American Graffiti where Kurt's
whole family and all his buddies are parked behind the airplane seeing
him off?
Ron
Post by Anders HammarWell, you shouldn't download the entire central repo. It's rude to those
that are paying for the bandwidth!
Also, there is no easy way to scrape Maven central as it tries its best to
block that bad habit. It will also make to blacklisted for future downloads.
The absolutely easiest way to solve this is to work out a solution where
your repo manager does have Internet access and will be proxying the
artifacts from Internet. For most scenarios, there should be acceptable
solutions to this that the security concerned people can accept. I have done
this for customers with similar setup that you describe. Having a
centralized point where the artifacts are "proxied" (in the repo manager),
gives you the possibility to add functionality such as procurement.
If this still doesn't work, the way to go is to manually fetch the required
artifacts (not all, just the ones you need) and upload it to your repo
manager in the closed network. You will very soon realize that this is not
what you want to spend your days doing, and the managers will also realized
that this is not what they want to spend their money on.
Please remember that fetching the artifacts is not a one time job, but
something you will be doing whenever you need a new version of some
dependency, a new dependency, or simply just a new (or a new version of a)
plugin (which happens VERY often).
/Anders
Post by GokceHi to all,
I'm actually trying to create the copy of the central repository in my
closed environment. But I don't know how to download all the repository
items to a media, which I plan to use later in my development environment.
The solutions specified in the previous replies will be helpful after that
point. After getting the whole repository I can manage it with Nexus,
Archiva or Artifactory. But I still didnt catch how can I download the whole
repository.
Thank you again.
Gokce
--
http://maven.40175.n5.nabble.com/Creating-a-Local-Repository-for-Intranet-Access-without-Internet-Connection-tp3393980p3395233.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------