[
http://jira.codehaus.org/browse/MEV-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215741#action_215741
]
Dennis Lundberg commented on MEV-656:
-------------------------------------
That's because they reference the java.net repository at
https://maven-repository.dev.java.net/nonav/repository
The Log4J 1.2.15 POM is busted in more ways than this though, so my
recommendation is to use 1.2.14. At least until 1.2.16 comes out, which has had
many of these problems fixed. See MEV-649.
> Log4J 1.2.15 POM references bad javax.mail POM
> ----------------------------------------------
>
> Key: MEV-656
> URL: http://jira.codehaus.org/browse/MEV-656
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid POM
> Reporter: Pete Ford
>
> Log4J 1.2.15 has a dependency on javax.mail 1.4 but may be pointing at an old
> location for it; the javamail POM in my repository after download contains
> this:
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>301 Moved Permanently</title>
> </head><body>
> <h1>Moved Permanently</h1>
> <p>The document has moved <a
> href="http://download.java.net/maven/1/javax.mail/poms/mail-1.4.pom";>here</a>.</p>
> <hr>
> <address>Apache Server at maven-repository.dev.java.net Port 443</address>
> </body></html>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
