13 Replies Latest reply: Jan 20, 2014 11:22 AM by Sebastian Herrmann RSS

    Can't create a Java EE project - archetype not found

    Glenn Silverman Newbie

      I just updated to the latest version of Jboss Tools - Beta 3 in Eclipse, but now, when I try to create a new Java EE Project, I get the following error:


      Could not resolve artifact org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:pom:7.1.1-Beta1-JBT


      We use a private Nexus repo browser that is set up in settings.xml for all of our artifacts. Do I need to add a new proxy repository to our Nexus system, and if so, what is the URL?

        • 1. Re: Can't create a Java EE project - archetype not found
          Max Rydahl Andersen Master

          Hmm - these should be in central - what kind of configuration do you have in your settings.xml ? Have you blocked of central completely ?

          • 2. Re: Can't create a Java EE project - archetype not found
            Glenn Silverman Newbie

            Actually, I found the archetypes in this repo:




            I added this to our Nexus installation and I'm still getting the same error.

            • 3. Re: Can't create a Java EE project - archetype not found
              Max Rydahl Andersen Master

              could you show your settings.xml setup ?


              These should not be affecting us thus curious what you have in there that we have missed in our testing.

              • 4. Re: Can't create a Java EE project - archetype not found
                Glenn Silverman Newbie

                Here is my complete settngs.xml, sans usernames and passwords:


                <?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"


                          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. | -->


                                    <!-- pluginGroup | Specifies a further group identifier to use for plugin

                                              lookup. <pluginGroup>com.your.plugins</pluginGroup> -->




                          <!-- 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. | -->


                                    <!-- 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> -->




                          <!-- 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. | -->


                                    <!-- 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> -->































                          <!-- 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.

                                    | -->


                                    <!-- 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> -->



                                              <!--This sends everything else to /public -->










                          <!-- 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.

                                    | | -->


                                    <!-- 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> -->



                                              <!--Enable snapshots for the built in central repo to direct -->

                                              <!--all requests to nexus via the mirror -->








































                          <!-- activeProfiles | List of profiles that are active for all builds. |

                                    <activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile>

                                    </activeProfiles> -->


                                    <!--make the profile active all the time -->




                • 5. Re: Can't create a Java EE project - archetype not found
                  Glenn Silverman Newbie

                  By the way. I do have access to http://repo1.maven.org/maven2/, if that is what you mean by "central". That repo does have a jboss-javaee6-webapp-ear-archetype, but the version is 7.0.2.CR2.

                  • 6. Re: Can't create a Java EE project - archetype not found
                    Fred Bricon Novice

                    Maven caches artifact resolution errors by default cached (for 24h IIRC). That might explain why the archetype is not found even if the svn repo was proxied on nexus.

                    Wiping the : jboss-javaee6-webapp-ear-archetype/7.1.1-Beta1-JBT folder out in the local repo will force maven to resolve the archetype again. You might also want to check Nexus logs to see if the proxy is actually requested for jboss-javaee6-webapp-ear-archetype/7.1.1-Beta1-JBT

                    • 7. Re: Can't create a Java EE project - archetype not found
                      Glenn Silverman Newbie

                      I've done everything I can think of, including deleting my local repo. Nothing seems to work. I still get the same error. I even tried to create the project directly from New->Maven->Maven Project, in which I added the archetype for Beta1. The Beta1-JBT version just doesn't seem to be available. But that still doesn't work. Rather than get an error message, my Eclipse crashes with either 44% or 98% completion. I'm using a clean Eclipse Indigo download, eclipse-jee-indigo-SR2-win32-x86_64.zip and installed the Jboss Tools directly from the Eclipse marketplace. That's all. Nothing special. I just can;t create either the Java EE Web Project or the Java EE Project. Somethings broken and I don't think it's local to my system. 

                      • 8. Re: Can't create a Java EE project - archetype not found
                        Max Rydahl Andersen Master

                        "something" is blocking your acces to this repository and my guess is



                                                      <!--This sends everything else to /public -->








                        is the culprit.


                        Can you try (just for fun to remove that and see how it goes ?

                        • 9. Re: Can't create a Java EE project - archetype not found
                          Fred Bricon Novice

                          We've just updated the JavaEE Web and EAR projects, so they now point to http://repository.jboss.org/nexus/content/repositories/releases/.

                          The archetypes should be synched to Maven Central in the next 24h, so I'll switch to use maven central then.

                          • 10. Re: Can't create a Java EE project - archetype not found
                            Glenn Silverman Newbie



                            Thanks for the reply. Your suggestion worked. I thought that if I proxy the repo in Nexus that all would be fine, but apparently that isn't so. Maybe it's a nexus issue. In any case, I modified my settings.xml to include my Nexus repo but not mirror it for all repository requests.

                            • 11. Re: Can't create a Java EE project - archetype not found
                              Preston Thornton Newbie

                              Helo Fred:


                              I saw this thread and wondered where in eclipse do you apply this change?

                              • 12. Re: Can't create a Java EE project - archetype not found
                                Preston Thornton Newbie

                                Never mind.  I have remember now.

                                • 13. Re: Can't create a Java EE project - archetype not found
                                  Sebastian Herrmann Newbie

                                  Sorry to dig out this thread again but I'm still encountering the same problem.




                                  My Maven in Eclipse is already configured to work offline but it somehow still tries to reach out to some remote repository? Or what is it searching for? Shouldn't those default archetypes be included in the local repositories?

                                  I also tried using a remote Maven installation (which starts fine outside of Eclipse) and I'm still getting the same error.


                                  In general I'd like to achieve an offline development environment for JBoss AS (or WildFly) applications - is that possible right now?


                                  As always thanks for any ideas and thoughts.