[jbosstools-issues] [JBoss JIRA] (JBIDE-18772) move to have publish.sh as a versioned dependency instead of fetching latest/greatests

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-18772:
------------------------------------

Translated into actionable specs:

1. parent pom should declare the specific version of the publish.sh/publish-mojo/publish.py
2. parent pom should fetches the publish script as part of the initial build setup
3. jobs can then use a specific publishing tool

Currently, we do this, which is unversioned (everyone uses the latest in master):

{code}wget http://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/publish.sh -q --no-check-certificate -N
. publish.sh
{code}


> move to have publish.sh as a versioned dependency instead of fetching latest/greatests
> --------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18772
>                 URL: https://issues.jboss.org/browse/JBIDE-18772
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>            Reporter: Max Rydahl Andersen
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
>  



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)