[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=12760321#comment-12760321 ] 

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

[~mickael_istria] the problem right now is that stuff gets added to the target platform just because a single person asks for it in jira - that is not what we ever wanted.

We should only add stuff to the target platform that makes sense and does not conflict. To know that we need more than just "oh lets add XYZ to the target platform".

I would expect something like:

Request comes in with list of features/plugins to add from which site.
If a basic update of 3rd party things, build could help do the changes to the the TP (if the reporter didn't have the info/knowledge to do so), do a check to see if any dependencies are dragged in we don't know about 
Then post on mailing list if any objections to this change (with enough detail to actually make a decision/spot issues - i.e. changed/removed IU's) - maybe even point to a snapshot build that can be tried out or just a .target file to use.
If all is good - progress moves on and it can be included.

Otherwise you guys will be adding stuff and releasing TP's that has changes that was done prematurely IMO.



                
> 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