[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Paul Gier updated JBBUILD-682: ------------------------------ Fix Version/s: Build Support 2011 This repository has been deprecated for more than one year. Is there a reason why you are unable to use the Nexus URLs? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Paul Gier commented on JBBUILD-682: ----------------------------------- Yes, I see your point. I would like to enforce that the repo not be used by jboss employees. The idea of keeping it available for internal employees was to prevent breaking old product builds. But maybe we can just password protect it for internal builds. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Paul Gier commented on JBBUILD-682: ----------------------------------- The problem is that if we leave access open, and projects like the weld achetype continue to use the deprecated artifacts, you can have build problems later on that are much more difficult to diagnose. It should be relatively easy to update the archetypes to use the correct repository URLs and correct dependencies. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Kristof Vanbecelaere edited comment on JBBUILD-682 at 6/6/11 9:38 AM: ---------------------------------------------------------------------- Mind you, it is not the archetypes that pose the problem. It is one of the transitive dependencies of the generated app. The problem is, I cannot even run "mvn dependency:tree" as long as I don't have all the dependencies in my repository. So it is already hard to diagnose as it is. Try navigating the jboss pom forest using find and grep. was (Author: kva): Mind you, it is not the archetypes that pose the problem. It is one of their dependencies. The problem is, I cannot even run "mvn dependency:tree" as long as I don't have all the dependencies in my repository. So it is already hard to diagnose as it is. Try navigating the jboss pom forest using find and grep. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Savas Ali Tokmen commented on JBBUILD-682: ------------------------------------------ Hello Even if JBoss does not want to reenable the repository, can JBoss please at least comply with usual standards and return an error 404 instead of an error 401? Thank you -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Paul Gier commented on JBBUILD-682: ----------------------------------- Can you point me to some upstream jira or attach some build log information that shows the difference you see between what happens with 404 vs. 403? From my previous testing, Maven handles 403 correctly, and it wouldn't make any difference to change the error to 404. What version of Maven are you using? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Geoffrey De Smet commented on JBBUILD-682: ------------------------------------------ Also seeing what Savas is seeing. It just kills the build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Tim Costermans edited comment on JBBUILD-682 at 11/30/11 9:42 AM: ------------------------------------------------------------------ I just ran into the same problem. I added the following dependency to my pom.xml <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-tomcat</artifactId> <version>6.1.0.Final</version> <scope>provided</scope> </dependency> Resulted in: org.jboss.jbossas:jboss-as-tomcat:jar:6.1.0.Final (provided), org.slf4j:slf4j-api:jar:1.5.6 (provided), org.slf4j:slf4j-simple:jar:1.5. 6 (test), org.jboss.slf4j:slf4j-jboss-logging:jar:1.0.2.GA (provided)]: Failed to read artifact descriptor for trove:trove:jar:2.1.1: Could not transfer artifact trove:trove:pom:2.1.1 from/to repository.jboss.org (http://repository.jboss.org/maven2/): Access denied to: http://repository.jboss.org/maven2/trove/trove/2.1.1/trove-2.1.1.pom -> [Help 1] [ERROR] Can this be fixed? BTW, this breaks the maven build. Maven 3.0.3 doesn't like the 403 that is returned. was (Author: t.costermans): I just ran into the same problem. I added the following dependency to my pom.xml <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-tomcat</artifactId> <version>6.1.0.Final</version> <scope>provided</scope> </dependency> Resulted in: org.jboss.jbossas:jboss-as-tomcat:jar:6.1.0.Final (provided), org.slf4j:slf4j-api:jar:1.5.6 (provided), org.slf4j:slf4j-simple:jar:1.5. 6 (test), org.jboss.slf4j:slf4j-jboss-logging:jar:1.0.2.GA (provided)]: Failed to read artifact descriptor for trove:trove:jar:2.1.1: Could not transfer artifact trove:trove:pom:2.1.1 from/to repository.jboss.org (http://repository.jboss.org/maven2/): Access denied to: http://repository.jboss.org/maven2/trove/trove/2.1.1/trove-2.1.1.pom -> [Help 1] [ERROR] Can this be fixed? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Trenton Taylor commented on JBBUILD-682: ---------------------------------------- As a new user to Maven, I found this work-around to this issue. Add the following to your .m2/settings.xml: <mirrors> <mirror> <id>jboss2-mirror</id> <mirrorOf>jboss.maven</mirrorOf> <url>http://repository.jboss.org/nexus/content/repositories/deprecated&... </mirror> </mirrors> This will over-ride the use of the 'jboss.maven' default URL. It may not be the best solution, but it works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] supun Malinga commented on JBBUILD-682: --------------------------------------- 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, -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Larry O'Leary commented on JBBUILD-682: --------------------------------------- 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi... ] Paul Gier closed JBBUILD-682. ----------------------------- Resolution: Won't Fix 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira