ERRO na configuração para Maven no JBoss 7 , o que poderia ser ? [RESOLVIDO]

Jonas_backer · Abril 23, 2012, 6:58pm

[size=18][b]Boa noite, a todos

Alguém se habilita a ajudar !!!
[/b][/size]
Coloquei as libs mais compatíveis e ainda assim manteve-se essa incompatibilidade !!![size=18] [/size]

[INFO] Scanning for projects... SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Downloading: http://repo1.maven.org/maven2/org/jboss/bom/jboss-javaee-6.0-with-tools/1.0.0.M1/jboss-javaee-6.0-with-tools-1.0.0.M1.pom [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.jboss.as.quickstarts:jboss-as-kitchensink:7.1.1-SNAPSHOT (C:\Users\Marcio\Desktop\WorkSpaceJava\kitchensink\jboss-as-kitchensink\pom.xml) has 10 errors [ERROR] Non-resolvable import POM: Could not transfer artifact org.jboss.bom:jboss-javaee-6.0-with-tools:pom:1.0.0.M1 from/to central (http://repo1.maven.org/maven2): Invalid argument: getsockname to http://repo1.maven.org/maven2/org/jboss/bom/jboss-javaee-6.0-with-tools/1.0.0.M1/jboss-javaee-6.0-with-tools-1.0.0.M1.pom @ line 36, column 22 -> [Help 2] [ERROR] 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing. @ line 53, column 19 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar is missing. @ line 61, column 19 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec:jar is missing. @ line 69, column 19 [ERROR] 'dependencies.dependency.version' for org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar is missing. @ line 77, column 19 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:jar is missing. @ line 85, column 19 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.faces:jboss-jsf-api_2.0_spec:jar is missing. @ line 109, column 19 [ERROR] 'dependencies.dependency.version' for junit:junit:jar is missing. @ line 127, column 19 [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ line 136, column 19 [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.protocol:arquillian-protocol-servlet:jar is missing. @ line 142, column 19 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

rafael_jesus · Abril 23, 2012, 8:59pm

Pelo visto vc baixou um projeto pre configurado da JBoos…

Sempre que puder de um clean no projeto com o maven e install, qq coisa faça jboss-as:undeploy e depois jboss-as:deploy pelo terminal ou pelo plugin,

Mas como esta seu pom.xml?

Abrcs

Jonas_backer · Abril 23, 2012, 9:24pm

[color=brown]Eu revirei o Eclipse eu não sei se é algum jar especifico , para alguma lib mas acredito que não estou usando o Java 7 mas não acho que isso , influencie em alguma coisa para esses erros, abaixo o pom.xml , mas alguma coisa sobre as dependencies pode estar afetando algo
[/color]

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

4.0.0

org.jboss.as.quickstarts
jboss-as-kitchensink
7.1.1-SNAPSHOT
war
JBoss AS Quickstarts: kitchensink
A starter Java EE 6 webapp project for use on JBoss AS 7 / EAP 6, generated from the jboss-javaee6-webapp archetype

UTF-8 1.0.0.M1 org.jboss.bom jboss-javaee-6.0-with-tools ${javaee6.with.tools.version} pom import

  <!-- First declare the APIs we depend on and need for compilation. 
     All of them are provided by JBoss AS 7 -->

  <!-- Import the CDI API, we use provided scope as the API is included 
     in JBoss AS 7 -->
  <dependency>
     <groupId>javax.enterprise</groupId>
     <artifactId>cdi-api</artifactId>
     <scope>provided</scope>
  </dependency>

  <!-- Import the Common Annotations API (JSR-250), we use provided scope 
     as the API is included in JBoss AS 7 -->
  <dependency>
     <groupId>org.jboss.spec.javax.annotation</groupId>
     <artifactId>jboss-annotations-api_1.1_spec</artifactId>
     <scope>provided</scope>
  </dependency>

  <!-- Import the JAX-RS API, we use provided scope as the API is included 
     in JBoss AS 7 -->
  <dependency>
     <groupId>org.jboss.spec.javax.ws.rs</groupId>
     <artifactId>jboss-jaxrs-api_1.1_spec</artifactId>
     <scope>provided</scope>
  </dependency>

  <!-- Import the JPA API, we use provided scope as the API is included 
     in JBoss AS 7 -->
  <dependency>
     <groupId>org.hibernate.javax.persistence</groupId>
     <artifactId>hibernate-jpa-2.0-api</artifactId>
     <scope>provided</scope>
  </dependency>

  <!-- Import the EJB API, we use provided scope as the API is included 
     in JBoss AS 7 -->
  <dependency>
     <groupId>org.jboss.spec.javax.ejb</groupId>
     <artifactId>jboss-ejb-api_3.1_spec</artifactId>
     <scope>provided</scope>
  </dependency>

  <!-- JSR-303 (Bean Validation) Implementation -->
  <!-- Provides portable constraints such as @Email -->
  <!-- Hibernate Validator is shipped in JBoss AS 7 -->
  <dependency>
     <groupId>org.hibernate</groupId>
     <artifactId>hibernate-validator</artifactId>
     <version>4.2.0.Final</version>
     <scope>provided</scope>
     <exclusions>
        <exclusion>
           <groupId>org.slf4j</groupId>
           <artifactId>slf4j-api</artifactId>
        </exclusion>
     </exclusions>
  </dependency>

  <!-- Import the JSF API, we use provided scope as the API is included
     in JBoss AS 7 -->
  <dependency>
     <groupId>org.jboss.spec.javax.faces</groupId>
     <artifactId>jboss-jsf-api_2.0_spec</artifactId>
     <scope>provided</scope>
  </dependency>

  <!-- Now we declare any tools needed -->

  <!-- Annotation processor to generate the JPA 2.0 metamodel classes 
     for typesafe criteria queries -->
  <dependency>
     <groupId>org.hibernate</groupId>
     <artifactId>hibernate-jpamodelgen</artifactId>
     <version>1.1.1.Final</version>
     <scope>provided</scope>
  </dependency>

  <!-- Needed for running tests (you may also use TestNG) -->
  <dependency>
     <groupId>junit</groupId>
     <artifactId>junit</artifactId>
     <scope>test</scope>
  </dependency>

  <!-- Optional, but highly recommended -->
  <!-- Arquillian allows you to test enterprise code such as EJBs and 
     Transactional(JTA) JPA from JUnit/TestNG -->
  <dependency>
     <groupId>org.jboss.arquillian.junit</groupId>
     <artifactId>arquillian-junit-container</artifactId>
     <scope>test</scope>
  </dependency>
  
  <dependency>
     <groupId>org.jboss.arquillian.protocol</groupId>
     <artifactId>arquillian-protocol-servlet</artifactId>
     <scope>test</scope>               
  </dependency>

${project.artifactId} maven-compiler-plugin 2.3.1 1.6 1.6 maven-war-plugin 2.1.1 false org.jboss.as.plugins jboss-as-maven-plugin 7.1.0.Final default true maven-surefire-plugin 2.4.3 true

  <profile>
     <!-- An optional Arquillian testing profile that executes tests 
        in your JBoss AS instance -->
     <!-- This profile will start a new JBoss AS instance, and execute 
        the test, shutting it down when done -->
     <!-- Run with: mvn clean test -Parq-jbossas-managed -->
     <id>arq-jbossas-managed</id>
     <dependencies>
        <dependency>
           <groupId>org.jboss.as</groupId>
           <artifactId>jboss-as-arquillian-container-managed</artifactId>
           <scope>test</scope>
        </dependency>
     </dependencies>
  </profile>

  <profile>
     <!-- An optional Arquillian testing profile that executes tests 
        in a remote JBoss AS instance -->
     <!-- Run with: mvn clean test -Parq-jbossas-remote -->
     <id>arq-jbossas-remote</id>
     <dependencies>
        <dependency>
           <groupId>org.jboss.as</groupId>
           <artifactId>jboss-as-arquillian-container-remote</artifactId>
           <scope>test</scope>
        </dependency>
     </dependencies>
  </profile>
  <build> 
<extensions> 
  <extension> 
    <groupId>org.apache.maven.wagon</groupId> 
     <artifactId>wagon-ssh</artifactId> 
     <version>1.0-beta-7</version> 
  </extension> 
</extensions>

  <profile>
     <!-- When built in OpenShift the 'openshift' profile will be used when invoking mvn. -->
     <!-- Use this profile for any OpenShift specific customization your app will need. -->
     <!-- By default that is to put the resulting archive into the 'deployments' folder. -->
     <!-- http://maven.apache.org/guides/mini/guide-building-for-different-environments.html -->
     <id>openshift</id>
     <build>
        <plugins>
           <plugin>
              <artifactId>maven-war-plugin</artifactId>
              <version>2.1.1</version>
              <configuration>
                 <outputDirectory>deployments</outputDirectory>
                 <warName>ROOT</warName>
              </configuration>
           </plugin>
        </plugins>
     </build>
  </profile>

[/code]

system · Dezembro 30, 2015, 11:13am

ERRO na configuração para Maven no JBoss 7 , o que poderia ser ? [RESOLVIDO]

Cursos de Mobile

Cursos de Programação

Cursos de Front-end

Cursos de DevOps

Cursos de Design & UX

Cursos de Business

Cursos de Data & BI