1 Reply Latest reply on Mar 7, 2008 2:40 PM by adrian.brock

    JBossXB dependencies

      I've upgraded to the latest version of common-core
      and excluded some of the stupid transitive dependencies it causes
      http://jira.jboss.com/jira/browse/JBXB-131

      You might also want to consider whether some of the dependencies
      are optional (the user should choose seperately whether to include them in their
      project),

      e.g. is javax.xml.steam really required to run JBossXB
      or is it only if you choose seperately to use stax parsing/marshalling?
      Same question for the dtd parser?

      [ejort@warjort jbossxb]$ mvn dependency:list -DincludeScope=compile
      [INFO] Scanning for projects...
      [INFO] Searching repository for plugin with prefix: 'dependency'.
      WAGON_VERSION: 1.0-beta-2
      [INFO] ------------------------------------------------------------------------
      [INFO] Building JBoss XML Binding
      [INFO] task-segment: [dependency:list]
      [INFO] ------------------------------------------------------------------------
      [INFO] [dependency:list]
      [INFO]
      [INFO] The following files have been resolved:
      [INFO] apache-xerces:xercesImpl:jar:2.9.1:compile
      [INFO] javax.activation:activation:jar:1.0.2:compile
      [INFO] javax.xml.bind:jaxb-api:jar:2.1:compile
      [INFO] javax.xml.stream:stax-api:jar:1.0-2:compile
      [INFO] jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile
      [INFO] org.jboss:jboss-common-core:jar:2.2.3.GA:compile
      [INFO] org.jboss:jboss-reflect:jar:2.0.0.Beta11:compile
      [INFO] wutka-dtdparser:dtdparser121:jar:1.2.1:compile
      [INFO]
      


        • 1. Re: JBossXB dependencies

          e.g. you could have this

           <dependency>
           <groupId>wutka-dtdparser</groupId>
           <artifactId>dtdparser121</artifactId>
           <version>1.2.1</version>
           <scope>compile</scope>
          
           <optional>true</optional>
          
           </dependency>