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

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760848#comment-12760848 ] 

Max Rydahl Andersen commented on JBIDE-13408:
---------------------------------------------

A) if we are having changes to target platform every week something is very wrong :)

B) he can easily use a specific target platform locally - no need to push that into every other build.

C) we don't want to add in things that are obviously wrong to do - i.e. adding jmock and other testing libs to the target platform isn't something that should just be done within few hours; nor is removing jetty and adding a new one, nor is adding/updating zest....

That said i'm fine providing snapshots builds with changes, but just send out the email when the suggested TP changes and which changes are coming - don't move the used TPC by the build up to this immediately.


                
> 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/jboss/tools/target-platforms/jbdevstudio/multiple/4.21.3.Final/multiple-4.21.3.Final.pom. 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