[JBoss JIRA] (JBIDE-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

Monday, 25 February 2013

    [
https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi...
] 

Max Rydahl Andersen edited comment on JBIDE-13408 at 2/25/13 11:55 AM:
-----------------------------------------------------------------------

0. Update Alpha1 to use 0.16.0.SNAPSHOT [DONE]
1. Release tycho-plugins as 0.16.0.CR1 [DONE]
2. Update jbosstools-4.0.x branch to use 0.16.0.CR1 
       - jbosstools-central
       - jbosstools-base
       - jbosstools-server
       - jbosstools-javaee
       - target platform 4.30.x (?)

3. Update master to use 0.16.0.CR1 
       - put the plugin execution and version in to parent.pom
       - define properties for the site parts/description/names for plugins to override.
       - update to use that in:
           - jbosstools-central
           - jbosstools-base
           - jbosstools-server
           - jbosstools-javaee

4. Figure out how this affects JBTIS/integration tests.

      was (Author: maxandersen):

0. Update Alpha1 to use 0.16.0.SNAPSHOT [DONE]
1. Release tycho-plugins as 0.16.0.CR1 [DONE]
2. Update jbosstools-4.0.x branch to use 0.16.0.CR1 
       - jbosstools-central
       - jbosstools-base
       - jbosstools-server
       - jbosstools-javaee
       - target platform 4.30.x (?)
3. Update master to use 0.16.0.CR1 
       - put the plugin execution and version in to parent.pom
       - define properties for the site parts/description/names for plugins to override.
       - update to use that in:
           - jbosstools-central
           - jbosstools-base
           - jbosstools-server
           - jbosstools-javaee

4. Figure out how this affects JBTIS/integration tests.

...
 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: Mickael Istria
            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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006