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

Mickael Istria edited comment on JBIDE-18772 at 11/19/14 12:09 PM:
-------------------------------------------------------------------

A viable solution would be to start considering our build scripts as Maven artifacts, so it would enforce good versioning. It's just a matter of creating a pom.xml org.jboss.tools.releng:publish:4.3.0.Alpha1-SNAPSHOT in jbosstools-build-ci/publish, attach the necessary files to it.
We could already release the current ones as org.jboss.tools.releng:publish:4.2.0.Final so we know that 4.2.x could use them, make the 4.2.x jobs actually use them.

[~nickboldt] WDYT?


was (Author: mickael_istria):
A viable solution would be to start considering our build scripts as Maven artifacts, so it would enforce good versioning. It's just a matter of creating a pom.xml org.jboss.tools.releng:publish:4.3.0.Alpha1-SNAPSHOT in jbosstools-build-ci/publish, attach the necessary files to it.
We could already release the current ones as org.jboss.tools.releng:publish:4.2.0.Final so we know that 4.2.x could use them, make the 4.2.x jobs actually use them.

> 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
>
> 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)