1 Reply Latest reply on Aug 19, 2009 2:47 PM by Jeff Sinjem

    JBoss 5.0.1.GA Native Maven2 Eclipse POM dependencies: deplo

    Jeff Sinjem Newbie

      I'm trying to build a quick and simple JBossws annotated web service that deploys in a war. Everything works great in eclipse (3.4) with JBoss Tools.

      However, as soon as I enabled Maven2 on the project and remove the JBoss Runtime java build path dependency the project will no longer deploy within eclipse. I've tried every pom dependency configuration I can think of with no luck.

      Does anyone have this working who is willing to share the dependency tags from their pom.xml with me?

      Here's what I have that is not working:

      <dependencies>
       <dependency>
       <groupId>junit</groupId>
       <artifactId>junit</artifactId>
       <version>4.6</version>
       <scope>test</scope>
       </dependency>
       <dependency>
       <groupId>org.jboss.jbossas</groupId>
       <artifactId>jboss-as-main</artifactId>
       <version>5.0.1.GA</version>
       </dependency>
       <dependency>
       <groupId>jboss.jbossws</groupId>
       <artifactId>jboss-jaxws</artifactId>
       <version>3.0.1-native-2.0.4.GA</version>
       </dependency>
       </dependencies>


      If there's a tutorial somewhere that describes this I'd appreciate that as a response too. Any help is greatly appreciated.

      -Jeff

        • 1. Re: JBoss 5.0.1.GA Native Maven2 Eclipse POM dependencies: d
          Jeff Sinjem Newbie

          So I'll respond to my own post just in case anyone else runs into a similar problem. I finally figured out the dependency that allows me to reference JBoss from within an Eclipse workspace and run my deployed web service on a local JBoss Runtime Server.

          You'll need the following dependency in your pom.xml file:

          <dependency>
           <groupId>org.jboss.jbossas</groupId>
           <artifactId>jboss-as-main</artifactId>
           <version>5.0.1.GA</version>
           <scope>provided</scope>
           </dependency>


          By adding this dependency I was able to call my mavenized JEE web service, bundled in an ear (as a war with an associated ejb.jar) all deployed to an Eclipse JBoss Runtime with nothing on my project classpath other than the JDK and Maven references.

          Hope this helps any one else who is struggling with something similar