Thanks a lot Tomas. May I clarify a bit?
for 1): That means, whenever I know two repos are having chance to contain same artifact, I should put them into two separate group? for 2): I bet the new release will still enable us to access artifacts thru http://hostname/px-webapp/repsitory/artifact-group/artifcact right? Also, can I ask one related question on how Maven2 handle snapshot artifacts? Which of the following is the correct way? A) maven search thru repositories. If maven enountered a 'snapshot- enabled' repo, it will retrieve snapshot artifacts. Artifacts retrieved from 'snapshot-enabled' repo is assumed to be snapshot and will be checked for update in subsequent accesses; or B) maven search thru repositories. If maven enountered a 'snapshot- enabled' repo, it will retrieve snapshot artifacts. Repository or maven can tell this specific artifact is a snapshot , and only snapshot artifact from snapshot-enabled repo will be checked for update in subsequent accesses Which of the above case is correct? I am just thinking on whether there are ways to eliminate multiple repository proxies (no matter multiple Proximity instance or URL prefix) to serve for release and snapshot. Thanks a lot for your kind help Adrian -----Original Message----- From: Tamas Cservenak [mailto:[EMAIL PROTECTED] Sent: Monday, August 07, 2006 5:20 PM To: Maven Users List Subject: Re: Some Proximity usage questions Hi Adrian, thanx for helping improve Proximity! Here are the answers: 1) "the checksum failed" problem is because the aggregation that Proximity performs. It only happens if you have two or more reposes with same (or similar) contents (like having central and apache.snapshots) in the same repo group. IF Proximity finds two "maven-metadata.xml" on the SAME PATH, it will MERGE THEM if the repositories are in the same group. This merging is still "unfinished', since new checksum for the merged metadata is NOT calculated :( 2) this is perfectly sane thing to do. A new "RC4" targeted feature will enable Proximity to "emerge" the repo groups one level up, thus making multiple Proximity instances unneeded. The new repo URL will be " http://localhost:8080/px-webapp/repository/repogroup"; instead of current " http://localhost:8080/px-webapp/repository";. 3) Yes, DWR (direct web remoting) is included in RCx releases, but it is unused and unconfigured. Since I don't speak JavaScript, it will be removed eventually or some volunteer could set it up (and make the UI ajax capable) :) Please use forum on http://forum.abstracthorizon.org/ for support questions, thanx. Have fun, ~t~ On 8/7/06, Adrian Shum <[EMAIL PROTECTED]> wrote: > > Dear all, > > I am a newbie and just tried to use Proximity 1.0 RC3 > on Windows + Tomcat 5.0.30. > There are some issues that I cannot figure out > and wish someone can give me a helping hand: > > 1) I have setted up several remote repositories in Proximity, > including central, ibiblio and codehaus ones. I found that > sometimes I receive a CHECKSUM FAILED error in mvn, and > it will cause the artifacts failed to be downlaoded from > Proximity and mvn will eventually goes to central to download. > > After some trial-and-errors, I found that whenever there > is such CHECKSUM FAILED error on client side, > I can see in stdout of TOMCAT displaying: > INFO: Item found in total of 2 repositories, will merge them. > > Did I make something wrong which cause such problem? > The scenerio seems suggesting me to avoid having > repositories containing same artifacts but I think such > siutation should be very normal. > > 2) For snapshot and normal release repository, I think > maven handle differently, for which release artifiacts is > downloaded once and will not be downloaded again, > and artifats downloaded from snapshot repositories will > make maven check for updates. So I have setted up > two Proximity, one for non-snapshot and one for snapshot. > In my settings.xml I put two corresponding repositories, > and I enabled snapshots in the latter one. Is it the right way > to do? > > 3) I found in tomcat's log a lot of exception caused by > Proximity, for as an example: > > 2006-08-07 16:03:57 StandardContext[/proximity]Servlet /proximity threw > load() exception > javax.servlet.ServletException: Servlet.init() for servlet dwr-invoker > threw exception > at org.apache.catalina.core.StandardWrapper.loadServlet( > StandardWrapper.java:1085) > ... [deleted] > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) > ----- Root Cause ----- > javax.xml.transform.TransformerFactoryConfigurationError: Provider > org.apache.xalan.processor.TransformerFactoryImpl not found > at javax.xml.transform.TransformerFactory.newInstance(Unknown > Source) > ... [deleted] > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) > > > Proximity seems still working fine. Is these exception 'normal'? > I found Tomcat's log growing very fast because them. > > > Thanks a lot. > > > This email is confidential. If you are not the intended recipient, please > delete it from your system and notify the sender immediately. Any > unauthorized use, disclosure, dissemination or copying of this email is > prohibited. Tai Fook Securities Group, its group companies and their content > providers ("Parties") shall not be responsible for the accuracy or > completeness of this email or its attachment, if any, which could contain > virus, be corrupted, destroyed, incomplete, intercepted, lost or arrive > late. The Parites do not accept liability for any damage caused by this > email. > > >
