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

[Max Rydahl Andersen (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-18772:
----------------------------------------
    Description: 
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 

 

  was:
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.

 



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