On 1/17/07, Luke McLean <[EMAIL PROTECTED]> wrote:
I also got the same error using 2.0.4 from the commandline for both hibernate-annotations and hibernate files. These both try to get downloaded from an https repository that isn't listed in the pom. The only way I could get mvn to continue was to download the 2 jars individually from the central repository to my local user repository. Then mvn was able to continue with building the project. If anyone know why maven defaults to https://maven2-repository.dev.java.net for these files please explain (I'd love to understand what is going on here).
The problem is java.net. They don't allow you to access any of their projects with http://. If you try, they switch you to https://. For example: http://appfuse.dev.java.net gets switched to https://appfuse.dev.java.net. The only thing we currently rely on at java.net is JTA. Changing to http://maven2.glassfishwiki.org may solve the problem for us. Matt
Luke. Hi I tried maven 2.0.5, and I don't get the same error - I get a new one! The message is: Failed to resolve artifact. and applies to these 2 artifacts: org.hibernate:hibernate-annotations:jar:3.2.1.ga and struts:struts:jar:1.2.8 Also, the mirror work around doesn't seem to work for version 2.0.5. Fyi - I can reproduce this error by removing the 3.2.1.ga from my local maven repository, setting maven to version 2.0.4, and running 'mvn integration-test' for the basic-jsf archetype. Let me know if there's something else to try. Alex -- View this message in context: http://www.nabble.com/AppFuse-2.0-tf1160699s2369.html#a8424659 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
