Uploaded image for project: 'JBoss Build System'
  1. JBoss Build System
  2. JBBUILD-682

http://repository.jboss.org/maven2/ serving HTTP 403 to hosts outside RedHat VPN

    Details

    • Steps to Reproduce:
      Show
      Try to download http://repository.jboss.org/maven2/trove/trove/2.1.1/trove-2.1.1.pom from outside redhat vpn.
    • Similar Issues:
      Show 10 results 

      Description

      The legacy maven repository http://repository.jboss.org/maven2/ is serving HTTP 403 to hosts outside RedHat VPN, causing lots of builds to fail.

      e.g. http://community.jboss.org/message/606819?tstart=0 with error:

      Access denied to: http://repository.jboss.org/maven2/trove/trove/2.1.1/trove-2.1.1.pom

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            t.costermans Tim Costermans added a comment -

            The information provided by Paul an Trenton work. I ended up defining a mirror in my settins.xml file.
            Adding the jboss-as-tomcat still caused problems due to missing dependencies.

            [WARNING] The POM for com.sun.istack:istack-commons-runtime:jar:1.1 is missing, no dependency information available
            [WARNING] The POM for woodstox:wstx-asl:jar:3.2.1 is missing, no dependency information available
            [WARNING] The POM for ws-commons:policy:jar:1.0 is missing, no dependency information available

            Workaround:
            <dependency>
            <groupId>org.jboss.jbossas</groupId>
            <artifactId>jboss-as-tomcat</artifactId>
            <version>6.1.0.Final</version>
            <scope>provided</scope>
            <exclusions>
            <exclusion>
            <groupId>com.sun.istack</groupId>
            <artifactId>istack-commons-runtime</artifactId>
            </exclusion>
            <exclusion>
            <groupId>woodstox</groupId>
            <artifactId>wstx-asl</artifactId>
            </exclusion>
            <exclusion>
            <groupId>ws-commons</groupId>
            <artifactId>policy</artifactId>
            </exclusion>
            </exclusions>
            </dependency>

            But this is maybe not the place to discus this issue.

            Show
            t.costermans Tim Costermans added a comment - The information provided by Paul an Trenton work. I ended up defining a mirror in my settins.xml file. Adding the jboss-as-tomcat still caused problems due to missing dependencies. [WARNING] The POM for com.sun.istack:istack-commons-runtime:jar:1.1 is missing, no dependency information available [WARNING] The POM for woodstox:wstx-asl:jar:3.2.1 is missing, no dependency information available [WARNING] The POM for ws-commons:policy:jar:1.0 is missing, no dependency information available Workaround: <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-tomcat</artifactId> <version>6.1.0.Final</version> <scope>provided</scope> <exclusions> <exclusion> <groupId>com.sun.istack</groupId> <artifactId>istack-commons-runtime</artifactId> </exclusion> <exclusion> <groupId>woodstox</groupId> <artifactId>wstx-asl</artifactId> </exclusion> <exclusion> <groupId>ws-commons</groupId> <artifactId>policy</artifactId> </exclusion> </exclusions> </dependency> But this is maybe not the place to discus this issue.
            Hide
            supunm supun Malinga added a comment -

            Hi,

            I'm also affected by the same issue. Accoeding to the discussion it seems the workaround is to add parameters to .m2/settings.xml file. But its not practical to instruct each user who is building a project to do this. Would appriciate if there is a more easier fix.

            thanks,

            Show
            supunm supun Malinga added a comment - Hi, I'm also affected by the same issue. Accoeding to the discussion it seems the workaround is to add parameters to .m2/settings.xml file. But its not practical to instruct each user who is building a project to do this. Would appriciate if there is a more easier fix. thanks,
            Hide
            alitokmen Savas Ali Tokmen added a comment -

            Hi Supun

            I would suggest you to push your comments and te groupIds you're missing into http://community.jboss.org/wiki/MavenRepositoryCentralSynchronization

            That way, these dependencies will be pushed to Maven Central ASAP; removing all dependencies to the deprecated JBoss repositories.

            Thank you

            Show
            alitokmen Savas Ali Tokmen added a comment - Hi Supun I would suggest you to push your comments and te groupIds you're missing into http://community.jboss.org/wiki/MavenRepositoryCentralSynchronization That way, these dependencies will be pushed to Maven Central ASAP; removing all dependencies to the deprecated JBoss repositories. Thank you
            Hide
            loleary Larry O'Leary added a comment -

            This issue also occurs when attempting to build JBoss ON 2.4.2 which was just released a few weeks ago. It was a maintenance release so obviously it has dependencies on legacy packages. For example, it requires jboss-packaging-maven-plugin-1.9.99.jar. However, the build fails because the artifact can not be downloaded due to the Forbidden error message received by Maven.

            I looked into using a version from Nexus however this version does not exist there.

            I am connected to the VPN but the build still failed. It was pointed out that the internal IP address of repository.jboss.org is 10.5.105.13 while the external is 209.132.182.33. In my case, I use my local DNS server for all things except for specific internal domains. repository.jboss.org was not one of them. I changed my DNS configuration to direct DNS lookups for repository.jboss.org to the RH internal DNS server and I am back up and running. Obviously this solution only works for building when connected to the RH VPN. Community users who attempt to build the upstream will continue to fail if they attempt to build these previous releases.

            Show
            loleary Larry O'Leary added a comment - This issue also occurs when attempting to build JBoss ON 2.4.2 which was just released a few weeks ago. It was a maintenance release so obviously it has dependencies on legacy packages. For example, it requires jboss-packaging-maven-plugin-1.9.99.jar. However, the build fails because the artifact can not be downloaded due to the Forbidden error message received by Maven. I looked into using a version from Nexus however this version does not exist there. I am connected to the VPN but the build still failed. It was pointed out that the internal IP address of repository.jboss.org is 10.5.105.13 while the external is 209.132.182.33. In my case, I use my local DNS server for all things except for specific internal domains. repository.jboss.org was not one of them. I changed my DNS configuration to direct DNS lookups for repository.jboss.org to the RH internal DNS server and I am back up and running. Obviously this solution only works for building when connected to the RH VPN. Community users who attempt to build the upstream will continue to fail if they attempt to build these previous releases.
            Hide
            pgier Paul Gier added a comment -

            The deprecated repository URLs should no longer be used. The correct workaround for repository poms which still refer to the old repo URL is to define a mirror setting to block the old repository and exclude the deprecated repository from the build.

            Show
            pgier Paul Gier added a comment - The deprecated repository URLs should no longer be used. The correct workaround for repository poms which still refer to the old repo URL is to define a mirror setting to block the old repository and exclude the deprecated repository from the build.

              People

              • Assignee:
                pgier Paul Gier
                Reporter:
                maschmid Marek Schmidt
              • Votes:
                11 Vote for this issue
                Watchers:
                17 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development