2011/2/21 S. Gökce Çelik <[email protected]>: > I am working in a company which has separate networks for internet and > intranet, > and a connection between those are strictly prohibited. > I have to create a development environment at the intranet side. As far as I > looked around there is no way to maintain the repository without a live > connection to the central repository.
Sure there is. You populate your internal repository manually, preferably vetting the artifacts somehow based on corporate policies, checking the signatures, etc. If there are no strict rules about the artifacts themselves and it's really only about the network separation, then I'd just do a build while connected to the outside world, zip up my local repo, transfer it to the internal repo server, and let my repository manager (Apache Archiva) fix the metadata and then merge it all into the appropriate permanent repositories. Maven is happiest when there is a "remote" repository to connect to, but there is no requirement that you have access to central. Any repo that contains the artifacts you need will do. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
