1 Reply Latest reply on Mar 25, 2014 10:40 AM by gastaldi

    Forge can't build a new project with an own maven repository defined in maven settings

    bookwood

      Hi all,

      I use an own maven repository (artifactory) on my development system, to hold own Projects and as a Proxy. When I start to build a new project, forge stops with an strange error:

          _____                   
         |  ___|__  _ __ __ _  ___
         | |_ / _ \| `__/ _` |/ _ \  \\
         |  _| (_) | | | (_| |  __/  //
         |_|  \___/|_|  \__, |\___|
                         |___/     

       

      JBoss Forge, version [ 1.4.4.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ]
      [no project] tmp $ set VERBOSE true
      [no project] tmp $ new-project --named test123
      ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
      org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for org.jboss.forge.generated:generated-pom:1.0.0-SNAPSHOT
      [ERROR] Invalid artifact repository: null @

       

              at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:422)
              at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:374)
              at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:365)
              at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
              at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:141)
              at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:102)
              at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:101)
              at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:338)
              at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:394)
              at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:172)
              at org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:64)
              at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153)
              at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208)
              at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186)
              at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178)
              at org.jboss.forge.project.services.ProjectFactory.findProject(ProjectFactory.java:237)
              at org.jboss.forge.project.services.ProjectFactory.containsProject(ProjectFactory.java:216)
              at org.jboss.forge.shell.plugins.builtin.NewProjectPlugin.create(NewProjectPlugin.java:140)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:606)
              at org.jboss.forge.shell.command.Execution.perform(Execution.java:160)
              at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
              at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
              at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:796)
              at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:819)
              at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:609)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:606)
              at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
              at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
              at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:606)
              at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
              at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
              at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
              at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
              at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
              at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
              at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
              at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
              at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
              at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
              at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
              at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
              at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
              at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:186)
              at java.lang.Thread.run(Thread.java:744)
      [no project] tmp $

      I searched about a maven configuration, but found nothing. Here are my maven settings.xml:

      <?xml version="1.0" encoding="UTF-8"?>
      <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">

        <mirrors>
          <mirror>
            <id>remote-repos</id>
            <name>remote-repos</name>
            <url>http://127.0.0.1/artifactory/remote-repos</url>
            <mirrorOf>central</mirrorOf>
          </mirror>
          <mirror>
            <id>jboss-public</id>
            <name>remote-repos</name>
            <url>http://127.0.0.1/artifactory/remote-repos</url>
            <mirrorOf>jboss</mirrorOf>
          </mirror>
        </mirrors>

        <proxies>
          <proxy>
            <active>true</active>
            <protocol>http</protocol>
            <host>10.x.y.2</host>
            <port>3128</port>
                              <!-- username>proxyuser</username> <password>somepassword</password -->
            <nonProxyHosts>127.0.0.1</nonProxyHosts>
          </proxy>
        </proxies>

        <profiles>
          <profile>
            <repositories>
              <repository>
                <snapshots>
                  <enabled>false</enabled>
                </snapshots>
                <id>central</id>
                <name>libs-release</name>
                <url>http://127.0.0.1/artifactory/libs-release</url>
              </repository>
              <repository>
                <snapshots />
                <id>snapshots</id>
                <name>libs-snapshot</name>
                <url>http://127.0.0.1/artifactory/libs-snapshot</url>
              </repository>
            </repositories>

            <pluginRepositories>
              <pluginRepository>
                <snapshots>
                  <enabled>false</enabled>
                </snapshots>
                <id>central</id>
                <name>plugins-release</name>
                <url>http://127.0.0.1/artifactory/plugins-release</url>
              </pluginRepository>
              <pluginRepository>
                <snapshots />
                <id>snapshots</id>
                <name>plugins-snapshot</name>
                <url>http://127.0.0.1/artifactory/plugins-snapshot</url>
              </pluginRepository>
            </pluginRepositories>
            <id>artifactory</id>
          </profile>
        </profiles>

        <activeProfiles>
          <activeProfile>artifactory</activeProfile>
        </activeProfiles>
        <servers>
          <server>
            <id>integration.xyz.loc</id>
            <username>xyz</username>

            <password>........</password>

          </server>

        </servers>
      </settings>

       

      With an empty settings.xml everything works fine. Is there a way to tell forge to use an empty settings.xml on an other location?

       

      Thanks in advance

        • 1. Re: [forge-users] Forge can't build a new project with an own maven      repository defined in maven settings
          gastaldi

          You can add -Dorg.apache.maven.user-settings=PATH to your startup script to make Forge use another settings.xml.

           

          Best Regards,

           

          George

           

          Em 25/03/2014, às 08:42, forge-users@lists.jboss.org escreveu:

           

          Hi all,

          I use an own maven repository (artifactory) on my development system, to hold own Projects and as a Proxy. When I start to build a new project, forge stops with an strange error:

              _____                   

             |  ___|__  _ __ __ _  ___

             | |_ / _ \| `__/ _` |/ _ \ 

             |  | () | | | (_| |  __/  //

             |_|  \___/|_|  \__, |\___|

                             |___/     

           

          JBoss Forge, version - JBoss, by Red Hat, Inc. http://forge.jboss.org

          tmp $ set VERBOSE true

          tmp $ new-project --named test123

          ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)

          org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for org.jboss.forge.generated:generated-pom:1.0.0-SNAPSHOT

          Invalid artifact repository: null @

           

                  at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:422)

                  at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:374)

                  at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:365)

                  at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)

                  at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:141)

                  at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:102)

                  at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:101)

                  at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:338)

                  at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:394)

                  at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:172)

                  at org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:64)

                  at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153)

                  at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208)

                  at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186)

                  at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178)

                  at org.jboss.forge.project.services.ProjectFactory.findProject(ProjectFactory.java:237)

                  at org.jboss.forge.project.services.ProjectFactory.containsProject(ProjectFactory.java:216)

                  at org.jboss.forge.shell.plugins.builtin.NewProjectPlugin.create(NewProjectPlugin.java:140)

                  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

                  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                  at java.lang.reflect.Method.invoke(Method.java:606)

                  at org.jboss.forge.shell.command.Execution.perform(Execution.java:160)

                  at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)

                  at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)

                  at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:796)

                  at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:819)

                  at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:609)

                  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

                  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                  at java.lang.reflect.Method.invoke(Method.java:606)

                  at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)

                  at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)

                  at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)

                  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

                  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                  at java.lang.reflect.Method.invoke(Method.java:606)

                  at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)

                  at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)

                  at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)

                  at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)

                  at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)

                  at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)

                  at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)

                  at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)

                  at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)

                  at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)

                  at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)

                  at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)

                  at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)

                  at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:186)

                  at java.lang.Thread.run(Thread.java:744)

          tmp $

          I searched about a maven configuration, but found nothing. Here are my maven settings.xml:

          <?xml version="1.0" encoding="UTF-8"?>

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

            <mirrors>

              <mirror>

                <id>remote-repos</id>

                <name>remote-repos</name>

                <url>http://127.0.0.1/artifactory/remote-repos</url>

                <mirrorOf>central</mirrorOf>

              </mirror>

              <mirror>

                <id>jboss-public</id>

                <name>remote-repos</name>

                <url>http://127.0.0.1/artifactory/remote-repos</url>

                <mirrorOf>jboss</mirrorOf>

              </mirror>

            </mirrors>

            <proxies>

              <proxy>

                <active>true</active>

                <protocol>http</protocol>

                <host>10.x.y.2</host>

                <port>3128</port>

                                  <!-- username>proxyuser</username> <password>somepassword</password -->

                <nonProxyHosts>127.0.0.1</nonProxyHosts>

              </proxy>

            </proxies>

            <profiles>

              <profile>

                <repositories>

                  <repository>

                    <snapshots>

                      <enabled>false</enabled>

                    </snapshots>

                    <id>central</id>

                    <name>libs-release</name>

                    <url>http://127.0.0.1/artifactory/libs-release</url>

                  </repository>

                  <repository>

                    <snapshots />

                    <id>snapshots</id>

                    <name>libs-snapshot</name>

                    <url>http://127.0.0.1/artifactory/libs-snapshot</url>

                  </repository>

                </repositories>

                <pluginRepositories>

                  <pluginRepository>

                    <snapshots>

                      <enabled>false</enabled>

                    </snapshots>

                    <id>central</id>

                    <name>plugins-release</name>

                    <url>http://127.0.0.1/artifactory/plugins-release</url>

                  </pluginRepository>

                  <pluginRepository>

                    <snapshots />

                    <id>snapshots</id>

                    <name>plugins-snapshot</name>

                    <url>http://127.0.0.1/artifactory/plugins-snapshot</url>

                  </pluginRepository>

                </pluginRepositories>

                <id>artifactory</id>

              </profile>

            </profiles>

            <activeProfiles>

              <activeProfile>artifactory</activeProfile>

            </activeProfiles>

            <servers>

              <server>

                <id>integration.xyz.loc</id>

                <username>xyz</username>

                <password>........</password>

              </server>

            </servers>

          </settings>

           

          With an empty settings.xml everything works fine. Is there a way to tell forge to use an empty settings.xml on an other location?

           

          Thanks in advance

           

          Posted by forums

          Original post: https://community.jboss.org/message/864100#864100

           

          _______________________________________________

          forge-users mailing list

          forge-users@lists.jboss.org

          https://lists.jboss.org/mailman/listinfo/forge-users

           

          _______________________________________________

          forge-users mailing list

          forge-users@lists.jboss.org

          https://lists.jboss.org/mailman/listinfo/forge-users