[
https://issues.redhat.com/browse/WFLY-13209?page=com.atlassian.jira.plugi...
]
Lin Gao updated WFLY-13209:
---------------------------
Description:
I encountered some errors like:
{code:java}
Could not transfer artifact org.jboss.remoting:jboss-remoting:jar:4.0.18.Final from/to
central (
http://repo1.maven.org/maven2):
Error transferring file: Server returned HTTP response code: 501 for URL:
http://repo1.maven.org/maven2/org/jboss/remoting/jboss-remoting/4.0.18.Fi...
from
http://repo1.maven.org/maven2/org/jboss/remoting/jboss-remoting/4.0.18.Fi...
{code}
when playing some quickstarts, I think upgrading shrinkwrap-resolver to 2.2.7 should fix
the maven central https issue.
Upgrade shrinkwrap-resolve to 2.2.7
-----------------------------------
Key: WFLY-13209
URL:
https://issues.redhat.com/browse/WFLY-13209
Project: WildFly
Issue Type: Component Upgrade
Components: BOM
Reporter: Lin Gao
Assignee: Eduardo Martins
Priority: Major
I encountered some errors like:
{code:java}
Could not transfer artifact org.jboss.remoting:jboss-remoting:jar:4.0.18.Final from/to
central (
http://repo1.maven.org/maven2):
Error transferring file: Server returned HTTP response code: 501 for URL:
http://repo1.maven.org/maven2/org/jboss/remoting/jboss-remoting/4.0.18.Fi...
from
http://repo1.maven.org/maven2/org/jboss/remoting/jboss-remoting/4.0.18.Fi...
{code}
when playing some quickstarts, I think upgrading shrinkwrap-resolver to 2.2.7 should fix
the maven central https issue.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)