Thanks, Mike. Unfortunately, there are no logs which show any errors. The only log available is maven.velocity.log and it has no errors.
Michael Horwitz wrote: > > You should only need to deploy the artifacts to your new repository that > are > not available in the public repositories your are proxying. Most of the > time > these will be the artifacts you have developed internally, and any 3rd > party > jar files that have non-public licences (this can include some of the Sun > jar files). > > In terms of solving your problem, you can try looking in the maven-proxy > log > files for the cause of the error. Otherwise I would suggest raising a > query > on the maven-proxy mailing list (assuming there is one)? > > Mike > > On 6/7/07, nmall <[EMAIL PROTECTED]> wrote: >> >> >> After I installed the maven proxy, I tried to run maven jetty:run-war on >> a >> different machine with pom.xml referrring to the maven-proxy. It gives >> the >> following error >> >> [INFO] org.codehaus.mojo: checking for updates from central >> [WARNING] repository metadata for: 'org.codehaus.mojo' could not be >> retrieved fr >> om repository: central due to an error: Error transferring file >> [INFO] Repository 'central' will be blacklisted >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] BUILD ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does >> not >> exis >> t or no valid version could be found >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Trace >> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin >> 'org.apache.m >> aven.plugins:maven-compiler-plugin' does not exist or no valid version >> could >> be >> found >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa >> ultLifecycleExecutor.java:1286) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor >> (DefaultLifecycleExecutor.java:1469) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy >> AggregationNeeds(DefaultLifecycleExecutor.java:386) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi >> fecycleExecutor.java:138) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >> java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >> sorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:585) >> at >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >> at >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >> >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >> Caused by: >> org.apache.maven.plugin.version.PluginVersionNotFoundException: >> The p >> lugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or >> no >> vali >> d version could be found >> at >> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePl >> uginVersion(DefaultPluginVersionManager.java:228) >> at >> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePl >> uginVersion(DefaultPluginVersionManager.java:90) >> at >> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug >> inManager.java:166) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa >> >> nmall wrote: >> > >> > Hi, >> > >> > I installed maven proxy using the instructions in the link on Appfuse >> - >> > Sanjiv's blog entry titled Using maven-proxy to setup an internal maven >> > repository for more information. >> > >> > Now, I do need to install the artifacts in this repository, is that >> > right. If so, what is the best way to do it other than manually do mvn >> > deploy:deploy for each of the artifacts that my appfuse project depends >> > on. IS there any recommended maven repository manager that I can use. >> > >> > I looked at Proximity documentation but I saw a lot of problems from >> > Proximity users so was not sure about using it. Can you recommend a >> good >> > tool to install all the artifacts in the central repository. >> > >> > Thanks for your help!! >> > nmall >> > >> >> -- >> View this message in context: >> http://www.nabble.com/maven-central-repository-tf3881665s2369.html#a11002246 >> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/maven-central-repository-tf3881665s2369.html#a11008194 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
