[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:comment-tabpanel&focusedCommentId=13064896#comment-13064896 ] 

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

[~mickael_istria] maybe put that in separate issue instead of letting this stay open ? 

[~nickboldt] your examples still tells me that we dont have cleaned up our publishing if we need so many different steps but that is separate from this jira.

only question I got left is how can I use this publish.sh and have it work on completely different system - i.e my local running servers for testing ? which parameters shuold I set ?

> 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: Enhancement
>          Components: build
>            Reporter: Max Rydahl Andersen
>            Assignee: Mickael Istria
>            Priority: Critical
>             Fix For: 4.3.0.Beta1
>
>         Attachments: jbds-publish-to-snapshots.png
>
>
> 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.15#6346)