[jbosstools-issues] [JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-18772:
----------------------------------------

[~maxandersen] Invoking the publish.sh as part of an exec-maven-plugin plugged on the "deploy" phase would be a next iteration. In order to get that, we first need to make some changes in the publish.sh script to make it simpler to use.
Similarly to TP, this artifacts should be released for milestone builds. A good versioning convention would be: if backward-compatible, increase the Alpha/Beta/CR part or the micro version if Final was released; if not backward-compatible, increase the minor version.

> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
>                 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
>            Assignee: Mickael Istria
>
> 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.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible 
>  



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