]
Nick Boldt updated JBIDE-13408:
-------------------------------
Priority: Blocker (was: Major)
investigate using mvn deploy of non-SNAPSHOT target platforms to
JBoss Public Nexus
-----------------------------------------------------------------------------------
Key: JBIDE-13408
URL:
https://issues.jboss.org/browse/JBIDE-13408
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: target-platform
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.1.0.Alpha2
investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to
JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots.
Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I
got this error:
{quote}
{code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
(default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer
artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to
jboss-releases-repository
(
https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer
file:
https://repository.jboss.org/nexus/content/repositories/releases/org/jbos....
Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1]
{code}
{quote}
--
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: