Dan, Thank you for your reply! I am still struggling with repositories.
Do I understand correctly that there are 2 possible scenarios: 1. Use Maven in off-line mode. Then only local repository will be used and if artifact is not there then build fails. 2. Regular (not off-line) mode. Then local repository can receive artifacts from internal (pre-configured) repositories as well as from central repository. If I am right then here is my problem. I would like to make sure that artifacts can be received from internal repository only (nothing comes of external sources). So on the one hand I do need to be able to use internal repositories, on the other hand I don't want to be getting anything from external sources. Is that feasible? Thanks, Gary Vernik Member of Technical Staff System Management Software Network Appliance 408-822-3120 > -----Original Message----- > From: dan tran [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 07, 2005 3:29 PM > To: Maven Users List > Subject: Re: [m2] Repository question - plz help! > > On 12/7/05, Vernik, Gary <[EMAIL PROTECTED]> wrote: > > > Dan, > > > > First of, thank you for a prompt reply! > > Second, I couldn't figure how to post my reply to the > mailing list. I > > am using this archive ( > > > http://www.mail-archive.com/[email protected]/msg30199.html) and > > it only shows "reply to Dan")... > > > > Now to your message: > > > > > - Checkin all your dependencies to SCM using maven format. > > Exactly what I was planning. > > > > >Then mirror it to a web server ( use a cron to regularly update the > > webserver). > > >Then specify the web server as one of your repo. > > This seems to be overly complicated and I am pretty sure > that it won't > > fly by the build team. They are using ant and make and probably not > > looking into making their life more complicated. > > > > Sorry, i thought you are using maven at your comp. > Understood that it is tough to move to new modernizied build > system when you have every thing in place. > > > > >And if one day, you can convince your team, maven repo is > safe to use > > ;-), > > >then you dont need the SCM for your dependencies any more. > > It is not that I don't trust you but you are > over-simplifying the problem. > > public maven repo has a tiny subset of dependencies we will > end up using. > > 1. Not all open source libraries are part of maven repo. > > 2. We will be buying 3rd party libraries and they need to be stored > > into SCM anyways. > > 3. All builds needs to be 100% reproducible from scratch at > any point > > of time (including 10 years from now). Thus we need a total control > > which can be achieved thru SCM only. > > > > 1. You can request to upload missing OS libraries maven repo. > 2. I place i all my private thirdparty libraries in my > internal maven repo. > 3. If internal maven repo is protected ( itself is a SCM for > binary artifacts), i dont see any reason, maven can not > repoduce the build. > > Sorry I am just optimistic ;-) > > My further investigation showed that I can do > > either > > <url>file://.\repo</url> > > or > > <url>file://${basedir}/repo</url> Do you see any > problems with > > that? Any other suggestions? > > > > yes, but i seems that you will have a repo for each maven project? > > > > > > > > BTW, when I am installing 3rd party's library into my local > repo with > > install:install-file, is there a way to generate md5 > checksum for it? > > > > > > I think the lastest maven-install-plugin may have that, you > now can deploy file as well using deploy:deploy-file > otherwise, open a JIRA for it. > > There is also some work at maven-scm to store and retreive > artfifacts from SCM. You may want to tune in for this project. > > > > Dan, again, I greatly appreciate your attention!! > > > > Thanks, > > *Gary Vernik* > > *Member of Technical Staff* > > *System Management Software* > > *Network Appliance* > > *408-822-3120* > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
