[
https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-13408 at 1/31/13 3:10 PM:
-------------------------------------------------------------
OK, from what I've read there are a number of things we need to do (and a number of
possible URLs to try when deploying):
a) add license and other metadata to the target platform poms:
https://community.jboss.org/wiki/MavenProjectConfigurationRequirements - see *POM
template*
b) hope that Jenkins can push there w/o me having to hardcode my
jboss.org
username/password into the settings.xml file -
https://community.jboss.org/wiki/MavenGettingStarted-Developers - see *Deploy to JBoss
Repository*
c) add staging URL for public JBoss nexus to settings.xml used by Jenkins (per
https://community.jboss.org/wiki/MavenGettingStarted-Developers - see *Configuring Maven
to use the JBoss Repository*)
*
http://repository.jboss.org/nexus/content/groups/public/ instead of
*
https://repository.jboss.org/nexus/content/repositories/releases/
d) alternatively, can also try deploying like this (per
https://community.jboss.org/wiki/MavenDeployingARelease - see *Deploying a non Maven
Project*):
{code}
-DrepositoryId=jboss-releases-repository
-Durl=https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/
{code}
or using
https://repository.jboss.org/nexus/content/groups/staging/
was (Author: nickboldt):
OK, from what I've read there are a number of things we need to do (and a number
of possible URLs to try when deploying):
a) add license and other metadata to the target platform poms:
https://community.jboss.org/wiki/MavenProjectConfigurationRequirements - see *POM
template*
b) hope that Jenkins can push there w/o me having to hardcode my
jboss.org
username/password into the settings.xml file -
https://community.jboss.org/wiki/MavenGettingStarted-Developers - see *Deploy to JBoss
Repository*
c) add staging URL for public JBoss nexus to settings.xml used by Jenkins (per
https://community.jboss.org/wiki/MavenGettingStarted-Developers - see *Configuring Maven
to use the JBoss Repository*)
*
http://repository.jboss.org/nexus/content/groups/public/ instead of
*
https://repository.jboss.org/nexus/content/repositories/releases/
d) alternatively, can also try deploying like this:
{code}
-DrepositoryId=jboss-releases-repository
-Durl=https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/
{code}
or using
https://repository.jboss.org/nexus/content/groups/staging/
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:
http://www.atlassian.com/software/jira