Start with just

<settings>
 <proxies>
   <proxy>
     <id>optional</id>
     <active>true</active>
     <protocol>http</protocol>
     <host>localhost</host>
     <port>8080</port>
   </proxy>
  </proxies>
</settings>

Then see about adding in the rest of the stuff you need

BTW, you have www.google.com as a non-proxy host... why just google?


On 23 September 2008 08:55, ashleyvijay <[EMAIL PROTECTED]> wrote:

>
> Now my settings.xml looks like the following but when i try to create a
> project it still doesnt work.I have edited the settings.xml as much as I
> knw.Kindly help if Im missing something.
>
> <!--
> 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 $HOME/.m2/settings.xml.
>  |
>  |                 NOTE: This location can be overridden with the system
> property:
>  |
>  |
> -Dorg.apache.maven.user-settings=/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 system
> property:
>  |
>  |
> -Dorg.apache.maven.global-settings=/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>
>  <!-- localRepository
>   | The path to the local repository maven will use to store artifacts.
>   |
>   | Default: ~/.m2/repository
>  -->
>  <localRepository>C:\Documents and
> Settings\muthiaA\.m2\repository</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>true</offline>
>
>
>  <!-- 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>
>
>     | Specification for one proxy, to be used in connecting to the network.
>     |
>    <proxy>
>      <id>optional</id>
>      <active>true</active>
>      <protocol>http</protocol>
>
>       <host>localhost</host>
>      <port>8080</port>
>      <nonProxyHosts>www.google.com</nonProxyHosts>
>    </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>
>
>
>
>
>
> Stephen Connolly-2 wrote:
> >
> > try thinking about it
> >
> > tags that are commented out are ignored....
> >
> > have you anything else in there that you doin't want ignored?
> >
> > 2008/9/23 ashleyvijay <[EMAIL PROTECTED]>
> >
> >>
> >> Hey Thanks for the reply. Do I hve to do that for all the tags or just
> >> for
> >> the proxy one??Would appreciate ur help
> >>
> >> Stephen Connolly-2 wrote:
> >> >
> >> > You need to remove the comment start and end markers <!-- and -->
> >> >
> >> > If you look carefully you'll see you have your lovely proxies
> >> definintion
> >> > ignored inside a comment
> >> >
> >> > 2008/9/22 ashleyvijay <[EMAIL PROTECTED]>
> >> >
> >> >>
> >> >> Thanks for the reply. I didnt hve a settings.xml in .m2 directory so
> i
> >> >> copied
> >> >> the settings.xml from apache-maven-2.0.9\conf  and pasted it into .m2
> >> >> directory and changed the proxy settings a little according the link
> >> >> which
> >> >> u
> >> >> gave to me. So the proxy part in settings.xml looks like this. I
> tried
> >> to
> >> >> create the first project again but still doesnt work. Would
> apprecaite
> >> >> for
> >> >> ur help.
> >> >>
> >> >> <proxies>
> >> >>    <!-- proxy
> >> >>     | Specification for one proxy, to be used in connecting to the
> >> >> network.
> >> >>     |
> >> >>    <proxy>
> >> >>      <id>optional</id>
> >> >>      <active>true</active>
> >> >>      <protocol>http</protocol>
> >> >>
> >> >>     <host>http-proxy.zx.basf-ag.de</host>
> >> >>      <port>8080</port>
> >> >>
> >> >>    </proxy>
> >> >>    -->
> >> >>  </proxies>
> >> >>
> >> >>
> >> >> mylene wrote:
> >> >> >
> >> >> > see: http://maven.apache.org/guides/mini/guide-proxies.html
> >> >> >
> >> >> > Mylène
> >> >> >
> >> >> > On Mon, Sep 22, 2008 at 3:17 PM, ashleyvijay
> >> <[EMAIL PROTECTED]>
> >> >> > wrote:
> >> >> >
> >> >> >>
> >> >> >> Well I think so...if thats the case what should I do??
> >> >> >>
> >> >> >> mylene wrote:
> >> >> >> >
> >> >> >> > Hi,
> >> >> >> >
> >> >> >> > Do you happen to work from behind a proxy that you didn't set
> (in
> >> >> >> > settings.xml)?
> >> >> >> >
> >> >> >> > Mylène
> >> >> >> >
> >> >> >> > On Mon, Sep 22, 2008 at 2:47 PM, ashleyvijay
> >> >> <[EMAIL PROTECTED]>
> >> >> >> > wrote:
> >> >> >> >
> >> >> >> >>
> >> >> >> >> Hi all,
> >> >> >> >> Sorry if this question has been asked before. Im new to Maven
> >> and
> >> I
> >> >> >> hope
> >> >> >> >> I
> >> >> >> >> hve installed as per the instructions. When I try to create a
> >> new
> >> >> >> project
> >> >> >> >> it
> >> >> >> >> gives me this error. Can anybody please tell me how it could be
> >> >> >> resolved?
> >> >> >> >>
> >> >> >> >> C:\>mvn --version
> >> >> >> >> Maven version: 2.0.9
> >> >> >> >> Java version: 1.5.0_16
> >> >> >> >> OS name: "windows xp" version: "5.1" arch: "x86" Family:
> >> "windows"
> >> >> >> >>
> >> >> >> >> C:\>mvn archetype:create\
> >> >> >> -DarchetypeGroupId=org.apache.maven.archetypes\
> >> >> >> >> -Dgrou
> >> >> >> >> p=com.mycompany.app\ -DartifactId=my-app
> >> >> >> >> [INFO] Scanning for projects...
> >> >> >> >> [INFO] Searching repository for plugin with prefix:
> 'archetype'.
> >> >> >> >> [INFO] org.apache.maven.plugins: checking for updates from
> >> central
> >> >> >> >> [WARNING] repository metadata for: 'org.apache.maven.plugins'
> >> could
> >> >> >> not
> >> >> >> >> be
> >> >> >> >> retri
> >> >> >> >> eved 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-archetype-plugin'
> >> >> >> does
> >> >> >> >> not
> >> >> >> >> exi
> >> >> >> >> st or no valid version could be found
> >> >> >> >> [INFO]
> >> >> >> >>
> >> >> >>
> >> >>
> >> ------------------------------------------------------------------------
> >> >> >> >> [INFO] For more information, run Maven with the -e switch
> >> >> >> >> [INFO]
> >> >> >> >>
> >> >> >>
> >> >>
> >> ------------------------------------------------------------------------
> >> >> >> >> [INFO] Total time: < 1 second
> >> >> >> >> [INFO] Finished at: Mon Sep 22 14:44:02 CEST 2008
> >> >> >> >> [INFO] Final Memory: 1M/2M
> >> >> >> >> [INFO]
> >> >> >> >>
> >> >> >>
> >> >>
> >> ------------------------------------------------------------------------
> >> >> >> >>
> >> >> >> >> C:\>
> >> >> >> >> --
> >> >> >> >> View this message in context:
> >> >> >> >>
> >> >> >>
> >> >>
> >>
> http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607304.html
> >> >> >> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> >> >> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Mylene
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >> --
> >> >> >> View this message in context:
> >> >> >>
> >> >>
> >>
> http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607766.html
> >> >> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >> >> >>
> >> >> >>
> >> >> >>
> >> ---------------------------------------------------------------------
> >> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> >> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Mylene
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19608218.html
> >> >> Sent from the Maven - Users 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/Creating-first-Maven-Project-Problem-tp19607304p19622533.html
> >> Sent from the Maven - Users 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/Creating-first-Maven-Project-Problem-tp19607304p19622940.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to