<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="https://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Re: Can't create a Java EE project - archetype not found
</h3>
<span style="margin-bottom: 10px;">
created by <a href="https://community.jboss.org/people/glsilver">Glenn Silverman</a> in <i>JBoss Tools</i> - <a href="https://community.jboss.org/message/737792#737792">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>Here is my complete settngs.xml, sans usernames and passwords:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><?xml version="1.0" encoding="UTF-8"?></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor </p><p>          license agreements. See the NOTICE file distributed with this work for additional </p><p>          information regarding copyright ownership. The ASF licenses this file to </p><p>          you under the Apache License, Version 2.0 (the "License"); you may not use </p><p>          this file except in compliance with the License. You may obtain a copy of </p><p><span>          the License at </span><a class="jive-link-external-small" href="http://www.apache.org/licenses/LICENSE-2.0" target="_blank">http://www.apache.org/licenses/LICENSE-2.0</a><span> Unless required </span></p><p>          by applicable law or agreed to in writing, software distributed under the </p><p>          License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS </p><p>          OF ANY KIND, either express or implied. See the License for the specific </p><p>          language governing permissions and limitations under the License. --></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><!-- | This is the configuration file for Maven. It can be specified at two </p><p>          levels: | | 1. User Level. This settings.xml file provides configuration </p><p>          for a single user, | and is normally provided in ${user.home}/.m2/settings.xml. </p><p>          | | NOTE: This location can be overridden with the CLI option: | | -s /path/to/user/settings.xml </p><p>          | | 2. Global Level. This settings.xml file provides configuration for all </p><p>          Maven | users on a machine (assuming they're all using the same Maven | installation). </p><p>          It's normally provided in | ${maven.home}/conf/settings.xml. | | NOTE: This </p><p>          location can be overridden with the CLI option: | | -gs /path/to/global/settings.xml </p><p>          | | The sections in this sample file are intended to give you a running start </p><p>          at | getting the most out of your Maven installation. Where appropriate, </p><p>          the default | values (values used when the setting is not specified) are </p><p>          provided. | | --></p><p><span><settings xmlns="</span><a class="jive-link-external-small" href="http://maven.apache.org/SETTINGS/1.0.0" target="_blank">http://maven.apache.org/SETTINGS/1.0.0</a><span>"</span></p><p><span>          xmlns:xsi="</span><a class="jive-link-external-small" href="http://www.w3.org/2001/XMLSchema-instance" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a><span>"</span></p><p><span>          xsi:schemaLocation="</span><a class="jive-link-external-small" href="http://maven.apache.org/SETTINGS/1.0.0" target="_blank">http://maven.apache.org/SETTINGS/1.0.0</a><span> </span><a class="jive-link-external-small" href="http://maven.apache.org/xsd/settings-1.0.0.xsd" target="_blank">http://maven.apache.org/xsd/settings-1.0.0.xsd</a><span>"></span></p><p>          <!-- localRepository | The path to the local repository maven will use to </p><p>                    store artifacts. | | Default: ~/.m2/repository <localRepository>/path/to/local/repo</localRepository> --></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>          <!-- interactiveMode | This will determine whether maven prompts you when </p><p>                    it needs input. If set to false, | maven will use a sensible default value, </p><p>                    perhaps based on some other setting, for | the parameter in question. | | </p><p>                    Default: true <interactiveMode>true</interactiveMode> --></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>          <!-- offline | Determines whether maven should attempt to connect to the </p><p>                    network when executing a build. | This will have an effect on artifact downloads, </p><p>                    artifact deployment, and others. | | Default: false <offline>false</offline> --></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>          <!-- pluginGroups | This is a list of additional group identifiers that </p><p>                    will be searched when resolving plugins by their prefix, i.e. | when invoking </p><p>                    a command line like "mvn prefix:goal". Maven will automatically add the group </p><p>                    identifiers | "org.apache.maven.plugins" and "org.codehaus.mojo" if these </p><p>                    are not already contained in the list. | --></p><p>          <pluginGroups></p><p>                    <!-- pluginGroup | Specifies a further group identifier to use for plugin </p><p>                              lookup. <pluginGroup>com.your.plugins</pluginGroup> --></p><p>          </pluginGroups></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>          <!-- proxies | This is a list of proxies which can be used on this machine </p><p>                    to connect to the network. | Unless otherwise specified (by system property </p><p>                    or command-line switch), the first proxy | specification in this list marked </p><p>                    as active will be used. | --></p><p>          <proxies></p><p>                    <!-- proxy | Specification for one proxy, to be used in connecting to the </p><p>                              network. | <proxy> <id>optional</id> <active>true</active> <protocol>http</protocol> </p><p>                              <username>proxyuser</username> <password>proxypass</password> <host>proxy.host.net</host> </p><p>                              <port>80</port> <nonProxyHosts>local.net|some.host.com</nonProxyHosts> </proxy> --></p><p>          </proxies></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>          <!-- servers | This is a list of authentication profiles, keyed by the server-id </p><p>                    used within the system. | Authentication profiles can be used whenever maven </p><p>                    must make a connection to a remote server. | --></p><p>          <servers></p><p>                    <!-- server | Specifies the authentication information to use when connecting </p><p>                              to a particular server, identified by | a unique name within the system (referred </p><p>                              to by the 'id' attribute below). | | NOTE: You should either specify username/password </p><p>                              OR privateKey/passphrase, since these pairings are | used together. | <server> </p><p>                              <id>deploymentRepo</id> <username>repouser</username> <password>repopwd</password> </p><p>                              </server> --></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>                    <!-- Another sample, using keys to authenticate. <server> <id>siteServer</id> </p><p>                              <privateKey>/path/to/private/key</privateKey> <passphrase>optional; leave </p><p>                              empty if not used.</passphrase> </server> --></p><p>  </p><p>  </p><p>  <server></p><p>    <id>snapshots</id></p><p>    <username></username></p><p>    <password></password></p><p>  </server></p><p>  </p><p>  <server></p><p>    <id>releases</id></p><p>    <username</username></p><p>    <password</password></p><p>  </server></p><p>  </p><p>  <server></p><p>      <id>tomcat</id></p><p>      <username></username></p><p>      <password></password></p><p>    </server></p><p>  </p><p>    <server></p><p>        <id>dsisource.edispense</id></p><p>        <username></username></p><p>                    <password></password></p><p>          </server></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>          </servers></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>          <!-- mirrors | This is a list of mirrors to be used in downloading artifacts </p><p>                    from remote repositories. | | It works like this: a POM may declare a repository </p><p>                    to use in resolving certain artifacts. | However, this repository may have </p><p>                    problems with heavy traffic at times, so people have mirrored | it to several </p><p>                    places. | | That repository definition will have a unique id, so we can create </p><p>                    a mirror reference for that | repository, to be used as an alternate download </p><p>                    site. The mirror site will be the preferred | server for that repository. </p><p>                    | --></p><p>          <mirrors></p><p>                    <!-- mirror | Specifies a repository mirror site to use instead of a given </p><p>                              repository. The repository that | this mirror serves has an ID that matches </p><p>                              the mirrorOf element of this mirror. IDs are used | for inheritance and direct </p><p>                              lookup purposes, and must be unique across the set of mirrors. | <mirror> </p><p>                              <id>mirrorId</id> <mirrorOf>repositoryId</mirrorOf> <name>Human Readable </p><p><span>                              Name for this Mirror.</name> <url></span><a class="jive-link-external-small" href="http://my.repository.com/repo/path" target="_blank">http://my.repository.com/repo/path</a><span></url> </span></p><p>                              </mirror> --> </p><p>  </p><p>                    <mirror></p><p>                              <!--This sends everything else to /public --></p><p>                              <id>public</id></p><p>                              <mirrorOf>*</mirrorOf></p><p><span>                              <url></span><a class="jive-link-external-small" href="http://mynexus:8081/nexus/content/groups/public" target="_blank">http://mynexus:8081/nexus/content/groups/public</a><span></url></span></p><p>                    </mirror></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>          </mirrors></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>          <!-- profiles | This is a list of profiles which can be activated in a variety </p><p>                    of ways, and which can modify | the build process. Profiles provided in the </p><p>                    settings.xml are intended to provide local machine- | specific paths and </p><p>                    repository locations which allow the build to work in the local environment. </p><p>                    | | For example, if you have an integration testing plugin - like cactus </p><p>                    - that needs to know where | your Tomcat instance is installed, you can provide </p><p>                    a variable here such that the variable is | dereferenced during the build </p><p>                    process to configure the cactus plugin. | | As noted above, profiles can </p><p>                    be activated in a variety of ways. One way - the activeProfiles | section </p><p>                    of this document (settings.xml) - will be discussed later. Another way essentially </p><p>                    | relies on the detection of a system property, either matching a particular </p><p>                    value for the property, | or merely testing its existence. Profiles can also </p><p>                    be activated by JDK version prefix, where a | value of '1.4' might activate </p><p>                    a profile when the build is executed on a JDK version of '1.4.2_07'. | Finally, </p><p>                    the list of active profiles can be specified directly from the command line. </p><p>                    | | NOTE: For profiles defined in the settings.xml, you are restricted to </p><p>                    specifying only artifact | repositories, plugin repositories, and free-form </p><p>                    properties to be used as configuration | variables for plugins in the POM. </p><p>                    | | --></p><p>          <profiles></p><p>                    <!-- profile | Specifies a set of introductions to the build process, to </p><p>                              be activated using one or more of the | mechanisms described above. For inheritance </p><p>                              purposes, and to activate profiles via <activatedProfiles/> | or the command </p><p>                              line, profiles have to have an ID that is unique. | | An encouraged best </p><p>                              practice for profile identification is to use a consistent naming convention </p><p>                              | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', </p><p>                              'user-brett', etc. | This will make it more intuitive to understand what </p><p>                              the set of introduced profiles is attempting | to accomplish, particularly </p><p>                              when you only have a list of profile id's for debug. | | This profile example </p><p>                              uses the JDK version to trigger activation, and provides a JDK-specific repo. </p><p>                              <profile> <id>jdk-1.4</id> <activation> <jdk>1.4</jdk> </activation> <repositories> </p><p><span>                              <repository> <id>jdk14</id> <name>Repository for JDK 1.4 builds</name> <url></span><a class="jive-link-external-small" href="http://www.myhost.com/maven/jdk14" target="_blank">http://www.myhost.com/maven/jdk14</a><span></url> </span></p><p>                              <layout>default</layout> <snapshotPolicy>always</snapshotPolicy> </repository> </p><p>                              </repositories> </profile> --></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>                    <!-- | Here is another profile, activated by the system property 'target-env' </p><p>                              with a value of 'dev', | which provides a specific path to the Tomcat instance. </p><p>                              To use this, your plugin configuration | might hypothetically look like: </p><p>                              | | ... | <plugin> | <groupId>org.myco.myplugins</groupId> | <artifactId>myplugin</artifactId> </p><p>                              | | <configuration> | <tomcatLocation>${tomcatPath}</tomcatLocation> | </configuration> </p><p>                              | </plugin> | ... | | NOTE: If you just wanted to inject this configuration </p><p>                              whenever someone set 'target-env' to | anything, you could just leave off </p><p>                              the <value/> inside the activation-property. | <profile> <id>env-dev</id> </p><p>                              <activation> <property> <name>target-env</name> <value>dev</value> </property> </p><p>                              </activation> <properties> <tomcatPath>/path/to/tomcat/instance</tomcatPath> </p><p>                              </properties> </profile> --></p><p>                    <profile></p><p>                              <id>nexus</id></p><p>                              <!--Enable snapshots for the built in central repo to direct --></p><p>                              <!--all requests to nexus via the mirror --></p><p>                              <repositories> </p><p>                                        <repository></p><p>                                                  <id>public</id></p><p><span>                                                  <url></span><a class="jive-link-external-small" href="http://public" target="_blank">http://public</a><span></url></span></p><p>                                                  <releases></p><p>                                                            <enabled>true</enabled></p><p>                                                  </releases></p><p>                                                  <snapshots></p><p>                                                            <enabled>true</enabled></p><p>                                                  </snapshots></p><p>                                        </repository> </p><p>                              </repositories></p><p>                              <pluginRepositories></p><p>                                        <pluginRepository></p><p>                                                  <id>public</id></p><p><span>                                                  <url></span><a class="jive-link-external-small" href="http://public" target="_blank">http://public</a><span></url></span></p><p>                                                  <releases></p><p>                                                            <enabled>true</enabled></p><p>                                                  </releases></p><p>                                                  <snapshots></p><p>                                                            <enabled>true</enabled></p><p>                                                  </snapshots></p><p>                                        </pluginRepository></p><p>                              </pluginRepositories></p><p>                    </profile></p><p>  </p><p> <profile> </p><p>   <id>scmConfig</id></p><p>   <activation></p><p>     <activeByDefault>true</activeByDefault></p><p>   </activation></p><p>   <properties></p><p>     <scm.username></scm.username></p><p>     <scm.password></scm.password></p><p>   </properties></p><p>  </profile></p><p>          </profiles></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>          <!-- activeProfiles | List of profiles that are active for all builds. | </p><p>                    <activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile> </p><p>                    </activeProfiles> --></p><p>          <activeProfiles></p><p>                    <!--make the profile active all the time --></p><p>                    <activeProfile>nexus</activeProfile></p><p>          </activeProfiles></p><p></settings></p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="https://community.jboss.org/message/737792#737792">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in JBoss Tools at <a href="https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2128">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>