5 Replies Latest reply on Jun 28, 2013 9:45 AM by Josef Cacek

    EAP61 Maven repository inconsistency

    Jesper Skov Newbie

      The package net/jcip/jcip-annotations/1.0-redhat-3 contains a jar-file artifact.

      But the .pom file specifies it as a .zip file.

       

      This gives me problems when importing into IVY. I don't know if Maven is more forgiving when it comes to such matters.

       

      Jesper

        • 2. Re: EAP61 Maven repository inconsistency
          Jesper Skov Newbie

          Thanks.

           

          I found another problem, I think:

           

          org/picketbox/picketbox-infinispan/4.0.17.Final-redhat-1/picketbox-infinispan-4.0.17.Final-redhat-1.pom

           

          references

           

                <dependency>

                   <groupId>org.picketbox</groupId>

                   <artifactId>picketbox-spi-bare</artifactId>

                   <version>${project.version}</version>

                   <scope>compile</scope>

                </dependency>

                <dependency>

                   <groupId>org.picketbox</groupId>

                   <artifactId>jbosssx-bare</artifactId>

                   <version>${project.version}</version>

                   <scope>compile</scope>

                </dependency>

           

          But those two are not included in the repository (and given the custom redhat version, I would not expect to be able to find them elsewhere).

          • 3. Re: EAP61 Maven repository inconsistency
            Josef Cacek Newbie

            This second one shouldn't be a problem. It's only a compile dependency for Picketbox, not for the EAP, so it seems fine to me to omit it from the Maven-repo zip.

            • 4. Re: EAP61 Maven repository inconsistency
              Jesper Skov Newbie

              I don't know if these are supposed to be consistent with the repository, but they break my import, so I guess they are referenced somewhere.

               

               

              org/jboss/component/management/jboss-component-version-master/6.1.0-redhat-1/jboss-component-version-master-6.1.0-redhat-1.pom

               

              references/declares:

               

              <version.org.jboss.remoting3>3.2.15.GA-redhat-1</version.org.jboss.remoting3>

               

              while the shipped version is 3.2.16.GA-redhat-1

               

               

               

               

              org/jboss/component/management/jboss-component-version-master/6.0.1-redhat-1/jboss-component-version-master-6.0.1-redhat-1.pom

               

              references/declares:

               

              <version.org.jboss.spec.javax.servlet.jboss-servlet-api_3.0_spec>1.0.1.Final-redhat-2</version.org.jboss.spec.javax.servlet.jboss-servlet-api_3.0_spec>

               

              while the shipped version is 1.0.2.Final-redhat-1

              • 5. Re: EAP61 Maven repository inconsistency
                Josef Cacek Newbie

                The EAP 6.1.0 uses jboss-parent version 6.1.0-redhat-2, which reffers jboss-component-version-master in version 6.1.0-redhat-2. This version includes the correct versions of the components you've mentioned.