Great! If "long term plan" is not in the immediate future, a nice quick change to make it easier on user customizations is to move those settings to a separate file right away, so we don't have to merge with new release files.
We need to add a few more repos to the list and customize file locations. We source control configuration files like this, and minimizing it to only our changes is wonderful when possible! :-) Thank you for releasing your product. Yours was much faster and easier to setup than "maven-proxy", which I still don't have working. BTW, to work with M1, in "ibiblioRemotePeer", I had to change value="http://www.ibiblio.org/maven2/"; to value="http://www.ibiblio.org/maven/"; I was surprised by this, as I thought they mapped to the same repo. -----Original Message----- From: Tamás Cservenák [mailto:[EMAIL PROTECTED] Sent: Thursday, May 25, 2006 5:01 PM To: Maven Users List Subject: Re: Proximity 1.0.0-alpha1 Hi, I've been looking at that too. Looks like we have to modify > web-inf/applicationContext.xml to change the repo info and then > proximity.properties to set new/change dir locations. Correct. An enhancement idea is to have this user-config info separate from internal > product config info. Yes, actually, a long term plan is to make repo config dynamic and configurable over web UI. I already have (actually announced) a solution for this from Stephan Heilner... Bye, ~t~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
