You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by anshree123 <an...@tcs.com> on 2009/10/07 12:20:46 UTC
Getting error while configuring Maven
Hi everyone.
I am working with ServiceMix ESB and for that i need maven configured on my
system.
I work behind a proxy so i did the proxy settings in settings.xml file in
${Maven_Home}/conf/settings.xml.
But when i run the command mvn jetty:run or for that matter mvn install for
a pom.xml file, then i get the following exception:
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'jetty'.
[INFO] org.apache.maven.plugins: checking for updates from central
[WARNING] repository metadata for: 'org.apache.maven.plugins' could not be
retrieved from 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-jetty-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-jetty-plugin' does not exist or no valid
version could be found
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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 plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or
no valid version could be found
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:226)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
... 14 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 43 seconds
[INFO] Finished at: Wed Oct 07 15:28:47 IST 2009
[INFO] Final Memory: 1M/4M
[INFO]
------------------------------------------------------------------------
Do I have to do some other configurations??
Please help me out...
Thanks in advance for any help.
Regards,
Anushree
--
View this message in context: http://www.nabble.com/Getting-error-while-configuring-Maven-tp25783764p25783764.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting error while configuring Maven
Posted by anshree123 <an...@tcs.com>.
Hi Thanks again for your reply.
I think i will talk to the proxy ppl n get the issue resolved rather than
setting up an internal mirror...
Thanks again.. Your help is appreciated..
Regards
Anushree
Anders Hammar wrote:
>
> What kind of workaround are thinking about? If it's blocking, it is.
> One way of solving this could be settings up an internal mirror of
> central,
> like if you don't have an Internet connection. However, that is a VERY
> troublesome road to walk. I've tried it myself for a customer and we're
> migrating away from it. I suggest that you talk to the proxy people and
> make
> them solve the issue.
>
> /Anders
>
> On Thu, Oct 8, 2009 at 12:40, anshree123 <an...@tcs.com> wrote:
>
>>
>> Hi Thanks for the reply.
>> I tried the changes. You are right the problem is with the proxy, it is
>> blocking the download of the plugins.
>> Is there any workaround?
>>
>>
>> I did a quick check in an xml editor and it looks ok.
>> Are you able to do anything with Maven? If not, the proxy settings is
>> incorrect or something is blocking central. You could try adding a
>> different
>> repo and see if that works (it would then rule out the proxy setting as
>> incorrect). Try adding one of the central mirrors as a repository and a
>> plugin repository in your pom:
>> http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories
>> Don't add it as a mirror in your settings file. Just add one of them as a
>> normal repo and a plugin repo in your pom. When central fails it will try
>> this. We do this just to check if there is something blocking central. If
>> it
>> still doesn't work, something is most likely wrong with your proxy
>> configuration.
>>
>> /Anders
>>
>> On Thu, Oct 8, 2009 at 06:37, anshree123 <an...@tcs.com> wrote:
>>
>> >
>> > Hi thanks for the reply..
>> > Here is the entire settings.xml file.
>> >
>> > <?xml version="1.0" encoding="UTF-8"?>
>> >
>> > ...
>> --
>> View this message in context:
>> http://www.nabble.com/Getting-error-while-configuring-Maven-tp25783764p25801702.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Getting-error-while-configuring-Maven-tp25783764p25815008.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting error while configuring Maven
Posted by Anders Hammar <an...@hammar.net>.
What kind of workaround are thinking about? If it's blocking, it is.
One way of solving this could be settings up an internal mirror of central,
like if you don't have an Internet connection. However, that is a VERY
troublesome road to walk. I've tried it myself for a customer and we're
migrating away from it. I suggest that you talk to the proxy people and make
them solve the issue.
/Anders
On Thu, Oct 8, 2009 at 12:40, anshree123 <an...@tcs.com> wrote:
>
> Hi Thanks for the reply.
> I tried the changes. You are right the problem is with the proxy, it is
> blocking the download of the plugins.
> Is there any workaround?
>
>
> I did a quick check in an xml editor and it looks ok.
> Are you able to do anything with Maven? If not, the proxy settings is
> incorrect or something is blocking central. You could try adding a
> different
> repo and see if that works (it would then rule out the proxy setting as
> incorrect). Try adding one of the central mirrors as a repository and a
> plugin repository in your pom:
> http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories
> Don't add it as a mirror in your settings file. Just add one of them as a
> normal repo and a plugin repo in your pom. When central fails it will try
> this. We do this just to check if there is something blocking central. If
> it
> still doesn't work, something is most likely wrong with your proxy
> configuration.
>
> /Anders
>
> On Thu, Oct 8, 2009 at 06:37, anshree123 <an...@tcs.com> wrote:
>
> >
> > Hi thanks for the reply..
> > Here is the entire settings.xml file.
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> >
> > ...
> --
> View this message in context:
> http://www.nabble.com/Getting-error-while-configuring-Maven-tp25783764p25801702.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Getting error while configuring Maven
Posted by anshree123 <an...@tcs.com>.
Hi Thanks for the reply.
I tried the changes. You are right the problem is with the proxy, it is
blocking the download of the plugins.
Is there any workaround?
I did a quick check in an xml editor and it looks ok.
Are you able to do anything with Maven? If not, the proxy settings is
incorrect or something is blocking central. You could try adding a different
repo and see if that works (it would then rule out the proxy setting as
incorrect). Try adding one of the central mirrors as a repository and a
plugin repository in your pom:
http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories
Don't add it as a mirror in your settings file. Just add one of them as a
normal repo and a plugin repo in your pom. When central fails it will try
this. We do this just to check if there is something blocking central. If it
still doesn't work, something is most likely wrong with your proxy
configuration.
/Anders
On Thu, Oct 8, 2009 at 06:37, anshree123 <an...@tcs.com> wrote:
>
> Hi thanks for the reply..
> Here is the entire settings.xml file.
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> ...
--
View this message in context: http://www.nabble.com/Getting-error-while-configuring-Maven-tp25783764p25801702.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting error while configuring Maven
Posted by Anders Hammar <an...@hammar.net>.
I did a quick check in an xml editor and it looks ok.
Are you able to do anything with Maven? If not, the proxy settings is
incorrect or something is blocking central. You could try adding a different
repo and see if that works (it would then rule out the proxy setting as
incorrect). Try adding one of the central mirrors as a repository and a
plugin repository in your pom:
http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories
Don't add it as a mirror in your settings file. Just add one of them as a
normal repo and a plugin repo in your pom. When central fails it will try
this. We do this just to check if there is something blocking central. If it
still doesn't work, something is most likely wrong with your proxy
configuration.
/Anders
On Thu, Oct 8, 2009 at 06:37, anshree123 <an...@tcs.com> wrote:
>
> Hi thanks for the reply..
> Here is the entire settings.xml file.
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <!--
> Licensed to the Apache Software Foundation (ASF) under one
> or more contributor license agreements. See the NOTICE file
> distributed with this work for additional information
> regarding copyright ownership. The ASF licenses this file
> to you under the Apache License, Version 2.0 (the
> "License"); you may not use this file except in compliance
> with the License. You may obtain a copy of the License at
>
> http://www.apache.org/licenses/LICENSE-2.0
>
> Unless required by applicable law or agreed to in writing,
> software distributed under the License is distributed on an
> "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> KIND, either express or implied. See the License for the
> specific language governing permissions and limitations
> under the License.
> -->
>
> <!--
> | This is the configuration file for Maven. It can be specified at two
> levels:
> |
> | 1. User Level. This settings.xml file provides configuration for a
> single user,
> | and is normally provided in
> ${user.home}/.m2/settings.xml.
> |
> | NOTE: This location can be overridden with the CLI
> option:
> |
> | -s /path/to/user/settings.xml
> |
> | 2. Global Level. This settings.xml file provides configuration for all
> Maven
> | users on a machine (assuming they're all using the same
> Maven
> | installation). It's normally provided in
> | ${maven.home}/conf/settings.xml.
> |
> | NOTE: This location can be overridden with the CLI
> option:
> |
> | -gs /path/to/global/settings.xml
> |
> | The sections in this sample file are intended to give you a running
> start
> at
> | getting the most out of your Maven installation. Where appropriate, the
> default
> | values (values used when the setting is not specified) are provided.
> |
> |-->
> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
> http://maven.apache.org/xsd/settings-1.0.0.xsd">
> <!-- localRepository
> | The path to the local repository maven will use to store artifacts.
> |
> | Default: ~/.m2/repository
> <localRepository>/path/to/local/repo</localRepository>
> -->
>
> <!-- interactiveMode
> | This will determine whether maven prompts you when it needs input. If
> set to false,
> | maven will use a sensible default value, perhaps based on some other
> setting, for
> | the parameter in question.
> |
> | Default: true
> <interactiveMode>true</interactiveMode>
> -->
>
> <!-- offline
> | Determines whether maven should attempt to connect to the network when
> executing a build.
> | This will have an effect on artifact downloads, artifact deployment,
> and others.
> |
> | Default: false
> <offline>false</offline>
> -->
>
> <!-- pluginGroups
> | This is a list of additional group identifiers that will be searched
> when resolving plugins by their prefix, i.e.
> | when invoking a command line like "mvn prefix:goal". Maven will
> automatically add the group identifiers
> | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not
> already contained in the list.
> |-->
> <pluginGroups>
> <!-- pluginGroup
> | Specifies a further group identifier to use for plugin lookup.
> <pluginGroup>com.your.plugins</pluginGroup>
> -->
> </pluginGroups>
>
> <!-- 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>
> <!-- proxy
> | Specification for one proxy, to be used in connecting to the network.
> |
> <proxy>
> <id>optional</id>
> <active>true</active>
> <protocol>http</protocol>
> <username>proxyuser</username>
> <password>proxypass</password>
> <host>proxy.host.net</host>
> <port>80</port>
> <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
> </proxy>
> -->
> <proxy>
> <active>true</active>
> <protocol>http</protocol>
> <username>258150</username>
> <password>P@ssWord</password>
> <host>proxy.tcs.com</host>
> <port>80</port>
> </proxy>
> </proxies>
>
> <!-- servers
> | This is a list of authentication profiles, keyed by the server-id used
> within the system.
> | Authentication profiles can be used whenever maven must make a
> connection to a remote server.
> |-->
> <servers>
> <!-- server
> | Specifies the authentication information to use when connecting to a
> particular server, identified by
> | a unique name within the system (referred to by the 'id' attribute
> below).
> |
> | NOTE: You should either specify username/password OR
> privateKey/passphrase, since these pairings are
> | used together.
> |
> <server>
> <id>deploymentRepo</id>
> <username>repouser</username>
> <password>repopwd</password>
> </server>
> -->
>
> <!-- Another sample, using keys to authenticate.
> <server>
> <id>siteServer</id>
> <privateKey>/path/to/private/key</privateKey>
> <passphrase>optional; leave empty if not used.</passphrase>
> </server>
> -->
> </servers>
>
> <!-- mirrors
> | This is a list of mirrors to be used in downloading artifacts from
> remote repositories.
> |
> | It works like this: a POM may declare a repository to use in resolving
> certain artifacts.
> | However, this repository may have problems with heavy traffic at times,
> so people have mirrored
> | it to several places.
> |
> | That repository definition will have a unique id, so we can create a
> mirror reference for that
> | repository, to be used as an alternate download site. The mirror site
> will be the preferred
> | server for that repository.
> |-->
> <mirrors>
> <!-- mirror
> | Specifies a repository mirror site to use instead of a given
> repository. The repository that
> | this mirror serves has an ID that matches the mirrorOf element of
> this mirror. IDs are used
> | for inheritance and direct lookup purposes, and must be unique across
> the set of mirrors.
> |
> <mirror>
> <id>mirrorId</id>
> <mirrorOf>repositoryId</mirrorOf>
> <name>Human Readable Name for this Mirror.</name>
> <url>http://my.repository.com/repo/path</url>
> </mirror>
> -->
> </mirrors>
>
> <!-- profiles
> | This is a list of profiles which can be activated in a variety of ways,
> and which can modify
> | the build process. Profiles provided in the settings.xml are intended
> to provide local machine-
> | specific paths and repository locations which allow the build to work
> in the local environment.
> |
> | For example, if you have an integration testing plugin - like cactus -
> that needs to know where
> | your Tomcat instance is installed, you can provide a variable here such
> that the variable is
> | dereferenced during the build process to configure the cactus plugin.
> |
> | As noted above, profiles can be activated in a variety of ways. One way
> - the activeProfiles
> | section of this document (settings.xml) - will be discussed later.
> Another way essentially
> | relies on the detection of a system property, either matching a
> particular value for the property,
> | or merely testing its existence. Profiles can also be activated by JDK
> version prefix, where a
> | value of '1.4' might activate a profile when the build is executed on a
> JDK version of '1.4.2_07'.
> | Finally, the list of active profiles can be specified directly from the
> command line.
> |
> | NOTE: For profiles defined in the settings.xml, you are restricted to
> specifying only artifact
> | repositories, plugin repositories, and free-form properties to be
> used as configuration
> | variables for plugins in the POM.
> |
> |-->
> <profiles>
> <!-- profile
> | Specifies a set of introductions to the build process, to be
> activated using one or more of the
> | mechanisms described above. For inheritance purposes, and to activate
> profiles via <activatedProfiles/>
> | or the command line, profiles have to have an ID that is unique.
> |
> | An encouraged best practice for profile identification is to use a
> consistent naming convention
> | for profiles, such as 'env-dev', 'env-test', 'env-production',
> 'user-jdcasey', 'user-brett', etc.
> | This will make it more intuitive to understand what the set of
> introduced profiles is attempting
> | to accomplish, particularly when you only have a list of profile id's
> for debug.
> |
> | This profile example uses the JDK version to trigger activation, and
> provides a JDK-specific repo.
> <profile>
> <id>jdk-1.4</id>
>
> <activation>
> <jdk>1.4</jdk>
> </activation>
>
> <repositories>
> <repository>
> <id>jdk14</id>
> <name>Repository for JDK 1.4 builds</name>
> <url>http://www.myhost.com/maven/jdk14</url>
> <layout>default</layout>
> <snapshotPolicy>always</snapshotPolicy>
> </repository>
> </repositories>
> </profile>
> -->
>
> <!--
> | Here is another profile, activated by the system property
> 'target-env' with a value of 'dev',
> | which provides a specific path to the Tomcat instance. To use this,
> your plugin configuration
> | might hypothetically look like:
> |
> | ...
> | <plugin>
> | <groupId>org.myco.myplugins</groupId>
> | <artifactId>myplugin</artifactId>
> |
> | <configuration>
> | <tomcatLocation>${tomcatPath}</tomcatLocation>
> | </configuration>
> | </plugin>
> | ...
> |
> | NOTE: If you just wanted to inject this configuration whenever
> someone set 'target-env' to
> | anything, you could just leave off the <value/> inside the
> activation-property.
> |
> <profile>
> <id>env-dev</id>
>
> <activation>
> <property>
> <name>target-env</name>
> <value>dev</value>
> </property>
> </activation>
>
> <properties>
> <tomcatPath>/path/to/tomcat/instance</tomcatPath>
> </properties>
> </profile>
> -->
> </profiles>
>
> <!-- activeProfiles
> | List of profiles that are active for all builds.
> |
> <activeProfiles>
> <activeProfile>alwaysActiveProfile</activeProfile>
> <activeProfile>anotherAlwaysActiveProfile</activeProfile>
> </activeProfiles>
> -->
> </settings>
>
> Anders Hammar wrote:
> >
> > Could you please post your proxy configuration in your settings.xml?
> >
> > /Anders
> >
> > On Wed, Oct 7, 2009 at 12:20, anshree123 <an...@tcs.com> wrote:
> >
> >>
> >> Hi everyone.
> >> I am working with ServiceMix ESB and for that i need maven configured on
> >> my
> >> system.
> >> I work behind a proxy so i did the proxy settings in settings.xml file
> in
> >> ${Maven_Home}/conf/settings.xml.
> >> But when i run the command mvn jetty:run or for that matter mvn install
> >> for
> >> a pom.xml file, then i get the following exception:
> >>
> >> [INFO] Scanning for projects...
> >> [INFO] Searching repository for plugin with prefix: 'jetty'.
> >> [INFO] org.apache.maven.plugins: checking for updates from central
> >> [WARNING] repository metadata for: 'org.apache.maven.plugins' could not
> >> be
> >> retrieved from 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-jetty-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-jetty-plugin' does not exist or no valid
> >> version could be found
> >> at
> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >> at
> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >> at java.lang.reflect.Method.invoke(Method.java:597)
> >> 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 plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist
> >> or
> >> no valid version could be found
> >> at
> >>
> >>
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:226)
> >> at
> >>
> >>
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
> >> at
> >>
> >>
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
> >> ... 14 more
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Total time: 43 seconds
> >> [INFO] Finished at: Wed Oct 07 15:28:47 IST 2009
> >> [INFO] Final Memory: 1M/4M
> >> [INFO]
> >> ------------------------------------------------------------------------
> >>
> >> Do I have to do some other configurations??
> >> Please help me out...
> >> Thanks in advance for any help.
> >>
> >> Regards,
> >> Anushree
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Getting-error-while-configuring-Maven-tp25783764p25783764.html
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Getting-error-while-configuring-Maven-tp25783764p25798235.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Getting error while configuring Maven
Posted by anshree123 <an...@tcs.com>.
Hi thanks for the reply..
Here is the entire settings.xml file.
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
| This is the configuration file for Maven. It can be specified at two
levels:
|
| 1. User Level. This settings.xml file provides configuration for a
single user,
| and is normally provided in
${user.home}/.m2/settings.xml.
|
| NOTE: This location can be overridden with the CLI
option:
|
| -s /path/to/user/settings.xml
|
| 2. Global Level. This settings.xml file provides configuration for all
Maven
| users on a machine (assuming they're all using the same
Maven
| installation). It's normally provided in
| ${maven.home}/conf/settings.xml.
|
| NOTE: This location can be overridden with the CLI
option:
|
| -gs /path/to/global/settings.xml
|
| The sections in this sample file are intended to give you a running start
at
| getting the most out of your Maven installation. Where appropriate, the
default
| values (values used when the setting is not specified) are provided.
|
|-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
<!-- localRepository
| The path to the local repository maven will use to store artifacts.
|
| Default: ~/.m2/repository
<localRepository>/path/to/local/repo</localRepository>
-->
<!-- interactiveMode
| This will determine whether maven prompts you when it needs input. If
set to false,
| maven will use a sensible default value, perhaps based on some other
setting, for
| the parameter in question.
|
| Default: true
<interactiveMode>true</interactiveMode>
-->
<!-- offline
| Determines whether maven should attempt to connect to the network when
executing a build.
| This will have an effect on artifact downloads, artifact deployment,
and others.
|
| Default: false
<offline>false</offline>
-->
<!-- pluginGroups
| This is a list of additional group identifiers that will be searched
when resolving plugins by their prefix, i.e.
| when invoking a command line like "mvn prefix:goal". Maven will
automatically add the group identifiers
| "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not
already contained in the list.
|-->
<pluginGroups>
<!-- pluginGroup
| Specifies a further group identifier to use for plugin lookup.
<pluginGroup>com.your.plugins</pluginGroup>
-->
</pluginGroups>
<!-- 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>
<!-- proxy
| Specification for one proxy, to be used in connecting to the network.
|
<proxy>
<id>optional</id>
<active>true</active>
<protocol>http</protocol>
<username>proxyuser</username>
<password>proxypass</password>
<host>proxy.host.net</host>
<port>80</port>
<nonProxyHosts>local.net|some.host.com</nonProxyHosts>
</proxy>
-->
<proxy>
<active>true</active>
<protocol>http</protocol>
<username>258150</username>
<password>P@ssWord</password>
<host>proxy.tcs.com</host>
<port>80</port>
</proxy>
</proxies>
<!-- servers
| This is a list of authentication profiles, keyed by the server-id used
within the system.
| Authentication profiles can be used whenever maven must make a
connection to a remote server.
|-->
<servers>
<!-- server
| Specifies the authentication information to use when connecting to a
particular server, identified by
| a unique name within the system (referred to by the 'id' attribute
below).
|
| NOTE: You should either specify username/password OR
privateKey/passphrase, since these pairings are
| used together.
|
<server>
<id>deploymentRepo</id>
<username>repouser</username>
<password>repopwd</password>
</server>
-->
<!-- Another sample, using keys to authenticate.
<server>
<id>siteServer</id>
<privateKey>/path/to/private/key</privateKey>
<passphrase>optional; leave empty if not used.</passphrase>
</server>
-->
</servers>
<!-- mirrors
| This is a list of mirrors to be used in downloading artifacts from
remote repositories.
|
| It works like this: a POM may declare a repository to use in resolving
certain artifacts.
| However, this repository may have problems with heavy traffic at times,
so people have mirrored
| it to several places.
|
| That repository definition will have a unique id, so we can create a
mirror reference for that
| repository, to be used as an alternate download site. The mirror site
will be the preferred
| server for that repository.
|-->
<mirrors>
<!-- mirror
| Specifies a repository mirror site to use instead of a given
repository. The repository that
| this mirror serves has an ID that matches the mirrorOf element of
this mirror. IDs are used
| for inheritance and direct lookup purposes, and must be unique across
the set of mirrors.
|
<mirror>
<id>mirrorId</id>
<mirrorOf>repositoryId</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://my.repository.com/repo/path</url>
</mirror>
-->
</mirrors>
<!-- profiles
| This is a list of profiles which can be activated in a variety of ways,
and which can modify
| the build process. Profiles provided in the settings.xml are intended
to provide local machine-
| specific paths and repository locations which allow the build to work
in the local environment.
|
| For example, if you have an integration testing plugin - like cactus -
that needs to know where
| your Tomcat instance is installed, you can provide a variable here such
that the variable is
| dereferenced during the build process to configure the cactus plugin.
|
| As noted above, profiles can be activated in a variety of ways. One way
- the activeProfiles
| section of this document (settings.xml) - will be discussed later.
Another way essentially
| relies on the detection of a system property, either matching a
particular value for the property,
| or merely testing its existence. Profiles can also be activated by JDK
version prefix, where a
| value of '1.4' might activate a profile when the build is executed on a
JDK version of '1.4.2_07'.
| Finally, the list of active profiles can be specified directly from the
command line.
|
| NOTE: For profiles defined in the settings.xml, you are restricted to
specifying only artifact
| repositories, plugin repositories, and free-form properties to be
used as configuration
| variables for plugins in the POM.
|
|-->
<profiles>
<!-- profile
| Specifies a set of introductions to the build process, to be
activated using one or more of the
| mechanisms described above. For inheritance purposes, and to activate
profiles via <activatedProfiles/>
| or the command line, profiles have to have an ID that is unique.
|
| An encouraged best practice for profile identification is to use a
consistent naming convention
| for profiles, such as 'env-dev', 'env-test', 'env-production',
'user-jdcasey', 'user-brett', etc.
| This will make it more intuitive to understand what the set of
introduced profiles is attempting
| to accomplish, particularly when you only have a list of profile id's
for debug.
|
| This profile example uses the JDK version to trigger activation, and
provides a JDK-specific repo.
<profile>
<id>jdk-1.4</id>
<activation>
<jdk>1.4</jdk>
</activation>
<repositories>
<repository>
<id>jdk14</id>
<name>Repository for JDK 1.4 builds</name>
<url>http://www.myhost.com/maven/jdk14</url>
<layout>default</layout>
<snapshotPolicy>always</snapshotPolicy>
</repository>
</repositories>
</profile>
-->
<!--
| Here is another profile, activated by the system property
'target-env' with a value of 'dev',
| which provides a specific path to the Tomcat instance. To use this,
your plugin configuration
| might hypothetically look like:
|
| ...
| <plugin>
| <groupId>org.myco.myplugins</groupId>
| <artifactId>myplugin</artifactId>
|
| <configuration>
| <tomcatLocation>${tomcatPath}</tomcatLocation>
| </configuration>
| </plugin>
| ...
|
| NOTE: If you just wanted to inject this configuration whenever
someone set 'target-env' to
| anything, you could just leave off the <value/> inside the
activation-property.
|
<profile>
<id>env-dev</id>
<activation>
<property>
<name>target-env</name>
<value>dev</value>
</property>
</activation>
<properties>
<tomcatPath>/path/to/tomcat/instance</tomcatPath>
</properties>
</profile>
-->
</profiles>
<!-- activeProfiles
| List of profiles that are active for all builds.
|
<activeProfiles>
<activeProfile>alwaysActiveProfile</activeProfile>
<activeProfile>anotherAlwaysActiveProfile</activeProfile>
</activeProfiles>
-->
</settings>
Anders Hammar wrote:
>
> Could you please post your proxy configuration in your settings.xml?
>
> /Anders
>
> On Wed, Oct 7, 2009 at 12:20, anshree123 <an...@tcs.com> wrote:
>
>>
>> Hi everyone.
>> I am working with ServiceMix ESB and for that i need maven configured on
>> my
>> system.
>> I work behind a proxy so i did the proxy settings in settings.xml file in
>> ${Maven_Home}/conf/settings.xml.
>> But when i run the command mvn jetty:run or for that matter mvn install
>> for
>> a pom.xml file, then i get the following exception:
>>
>> [INFO] Scanning for projects...
>> [INFO] Searching repository for plugin with prefix: 'jetty'.
>> [INFO] org.apache.maven.plugins: checking for updates from central
>> [WARNING] repository metadata for: 'org.apache.maven.plugins' could not
>> be
>> retrieved from 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-jetty-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-jetty-plugin' does not exist or no valid
>> version could be found
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> 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 plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist
>> or
>> no valid version could be found
>> at
>>
>> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:226)
>> at
>>
>> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
>> at
>>
>> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
>> ... 14 more
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 43 seconds
>> [INFO] Finished at: Wed Oct 07 15:28:47 IST 2009
>> [INFO] Final Memory: 1M/4M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> Do I have to do some other configurations??
>> Please help me out...
>> Thanks in advance for any help.
>>
>> Regards,
>> Anushree
>> --
>> View this message in context:
>> http://www.nabble.com/Getting-error-while-configuring-Maven-tp25783764p25783764.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Getting-error-while-configuring-Maven-tp25783764p25798235.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting error while configuring Maven
Posted by Anders Hammar <an...@hammar.net>.
Could you please post your proxy configuration in your settings.xml?
/Anders
On Wed, Oct 7, 2009 at 12:20, anshree123 <an...@tcs.com> wrote:
>
> Hi everyone.
> I am working with ServiceMix ESB and for that i need maven configured on my
> system.
> I work behind a proxy so i did the proxy settings in settings.xml file in
> ${Maven_Home}/conf/settings.xml.
> But when i run the command mvn jetty:run or for that matter mvn install for
> a pom.xml file, then i get the following exception:
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'jetty'.
> [INFO] org.apache.maven.plugins: checking for updates from central
> [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be
> retrieved from 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-jetty-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-jetty-plugin' does not exist or no valid
> version could be found
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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 plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or
> no valid version could be found
> at
>
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:226)
> at
>
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
> at
>
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
> ... 14 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 43 seconds
> [INFO] Finished at: Wed Oct 07 15:28:47 IST 2009
> [INFO] Final Memory: 1M/4M
> [INFO]
> ------------------------------------------------------------------------
>
> Do I have to do some other configurations??
> Please help me out...
> Thanks in advance for any help.
>
> Regards,
> Anushree
> --
> View this message in context:
> http://www.nabble.com/Getting-error-while-configuring-Maven-tp25783764p25783764.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>