Re: FW: Using Proximity Corporate Repository doesnt download plugins/dependencies
If you use the standard configuration, the url for the central mirror should be urlhttp://somednsname:8080/px-webapp/repository/public/url instead of urlhttp://somednsname:8080/px-webapp/repository/inhouse/url Hope that helps, - Henry On 9/11/07, Wayne Fay [EMAIL PROTECTED] wrote: Perhaps Tamas will reply. I know he had a hardware failure and so the normal Proximity support channels are not available. Wayne On 9/10/07, Sonar, Nishant [EMAIL PROTECTED] wrote: Hello I am trying to setup a corporate repository through proximity. Her's what I did Installed proximity on apache by deploying the px-webap. Now I can browse to the proximity site through apache http://localhost:8080/px-webap. I will be using this site to host my repository in a way like http://somednsname:8080/px-webapp/repository/inhouse and will use it as to access repository from poms and will be making this entry in the setting.xml here's what in my setting.xml !-Settings .xml-- settings localRepositoryc:\Java\maven-2.0.6\repository/localRepository !-- proxies | This is a list of proxies which can be used on this machine to connect to the network. | Unless otherwise specified (by system property or command-line switch), the first proxy | specification in this list marked as active will be used. |-- proxies !-I Intentionally commented proxy to not hit outside world -- !--proxy activetrue/active protocolhttp/protocol hostsingle-proxy.wachovia.net/host port8080/port /proxy -- /proxies //mirrored central to corporate repo mirrors mirror idCentralMirror/id nameProxied Central REPO/name urlhttp://somednsname:8080/px-webapp/repository/inhouse/url mirrorOfcentral/mirrorOf /mirror /mirrors profiles profile idSample/id repositories repository idCorporate/id nameLocal Corporate Repo/name url http://somednsname:8080/px-webapp/repository/inhouse /url snapshots enabledtrue/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idCorporate/id nameLocal Corporate Repo/name url http:// somednsname:8080/px-webapp/repository/inhouse /url releases enabledtrue/enabled updatePolicynever/updatePolicy /releases snapshots enabledtrue/enabled /snapshots /pluginRepository /pluginRepositories /profile /profiles activeProfiles activeProfileSample/activeProfile /activeProfiles /settings I am getting following output when running build + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building simpleWebService [INFO]task-segment: [clean, install] [INFO] [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from Corporate [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from central [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-clean-plugin' does not exist or no valid version could be found [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-clean-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default LifecycleExecutor.java:1286)
RE: FW: Using Proximity Corporate Repository doesnt download plugins/dependencies
Thanks to Henry, Tamás I have figured out the problem , the reason was I need to block the internet acces by disabling any proxy setting (in settings.xml), and mirror the 'central' to http://somednsname:8080/px-webapp/repository/inhouse. Also I need to be very much clear on the maven-metadata.xml in the repository for all the plugins and dependencies. It worked!! Regards, Nishant Sonar -Original Message- From: Tamás Cservenák [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 11, 2007 12:52 PM To: Maven Users List Subject: Re: FW: Using Proximity Corporate Repository doesnt download plugins/dependencies Hello all, yes, i just wanted to correct Sonar, just as Heinrich did. So, you have to fix your settings.xml and it should work as you expected! Thanks, ~t~ On 9/11/07, Heinrich Nirschl [EMAIL PROTECTED] wrote: If you use the standard configuration, the url for the central mirror should be urlhttp://somednsname:8080/px-webapp/repository/public/url instead of urlhttp://somednsname:8080/px-webapp/repository/inhouse/url Hope that helps, - Henry On 9/11/07, Wayne Fay [EMAIL PROTECTED] wrote: Perhaps Tamas will reply. I know he had a hardware failure and so the normal Proximity support channels are not available. Wayne On 9/10/07, Sonar, Nishant [EMAIL PROTECTED] wrote: Hello I am trying to setup a corporate repository through proximity. Her's what I did Installed proximity on apache by deploying the px-webap. Now I can browse to the proximity site through apache http://localhost:8080/px-webap. I will be using this site to host my repository in a way like http://somednsname:8080/px-webapp/repository/inhouse and will use it as to access repository from poms and will be making this entry in the setting.xml here's what in my setting.xml !-Settings .xml-- settings localRepositoryc:\Java\maven-2.0.6\repository/localRepository !-- proxies | This is a list of proxies which can be used on this machine to connect to the network. | Unless otherwise specified (by system property or command-line switch), the first proxy | specification in this list marked as active will be used. |-- proxies !-I Intentionally commented proxy to not hit outside world -- !--proxy activetrue/active protocolhttp/protocol hostsingle-proxy.wachovia.net/host port8080/port /proxy -- /proxies //mirrored central to corporate repo mirrors mirror idCentralMirror/id nameProxied Central REPO/name urlhttp://somednsname:8080/px-webapp/repository/inhouse/url mirrorOfcentral/mirrorOf /mirror /mirrors profiles profile idSample/id repositories repository idCorporate/id nameLocal Corporate Repo/name url http://somednsname:8080/px-webapp/repository/inhouse /url snapshots enabledtrue/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idCorporate/id nameLocal Corporate Repo/name url http:// somednsname:8080/px-webapp/repository/inhouse /url releases enabledtrue/enabled updatePolicynever/updatePolicy /releases snapshots enabledtrue/enabled /snapshots /pluginRepository /pluginRepositories /profile /profiles activeProfiles activeProfileSample/activeProfile /activeProfiles /settings I am getting following output when running build + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building simpleWebService [INFO
Re: FW: Using Proximity Corporate Repository doesnt download plugins/dependencies
well, what is your config actually? As Heinrich said, the inhouse repo group is (in default config) not proxying the central! Did you change Proximity settings or using just the default out-of-the-box? I'm happy it works, but does it do what you think? :) ~t~ On 9/11/07, Sonar, Nishant [EMAIL PROTECTED] wrote: Thanks to Henry, Tamás I have figured out the problem , the reason was I need to block the internet acces by disabling any proxy setting (in settings.xml), and mirror the 'central' to http://somednsname:8080/px-webapp/repository/inhouse. Also I need to be very much clear on the maven-metadata.xml in the repository for all the plugins and dependencies. It worked!! Regards, Nishant Sonar
Re: FW: Using Proximity Corporate Repository doesnt download plugins/dependencies
Perhaps Tamas will reply. I know he had a hardware failure and so the normal Proximity support channels are not available. Wayne On 9/10/07, Sonar, Nishant [EMAIL PROTECTED] wrote: Hello I am trying to setup a corporate repository through proximity. Her's what I did Installed proximity on apache by deploying the px-webap. Now I can browse to the proximity site through apache http://localhost:8080/px-webap. I will be using this site to host my repository in a way like http://somednsname:8080/px-webapp/repository/inhouse and will use it as to access repository from poms and will be making this entry in the setting.xml here's what in my setting.xml !-Settings .xml-- settings localRepositoryc:\Java\maven-2.0.6\repository/localRepository !-- proxies | This is a list of proxies which can be used on this machine to connect to the network. | Unless otherwise specified (by system property or command-line switch), the first proxy | specification in this list marked as active will be used. |-- proxies !-I Intentionally commented proxy to not hit outside world -- !--proxy activetrue/active protocolhttp/protocol hostsingle-proxy.wachovia.net/host port8080/port /proxy -- /proxies //mirrored central to corporate repo mirrors mirror idCentralMirror/id nameProxied Central REPO/name urlhttp://somednsname:8080/px-webapp/repository/inhouse/url mirrorOfcentral/mirrorOf /mirror /mirrors profiles profile idSample/id repositories repository idCorporate/id nameLocal Corporate Repo/name url http://somednsname:8080/px-webapp/repository/inhouse /url snapshots enabledtrue/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idCorporate/id nameLocal Corporate Repo/name url http:// somednsname:8080/px-webapp/repository/inhouse /url releases enabledtrue/enabled updatePolicynever/updatePolicy /releases snapshots enabledtrue/enabled /snapshots /pluginRepository /pluginRepositories /profile /profiles activeProfiles activeProfileSample/activeProfile /activeProfiles /settings I am getting following output when running build + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building simpleWebService [INFO]task-segment: [clean, install] [INFO] [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from Corporate [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from central [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-clean-plugin' does not exist or no valid version could be found [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-clean-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default LifecycleExecutor.java:1286) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(De faultLifecycleExecutor.java:1522) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPack aging(DefaultLifecycleExecutor.java:1016) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa ppings(DefaultLifecycleExecutor.java:980) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:458) at
