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

[Nick Boldt (JIRA)]

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

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

@max:

0. the target here is Beta1, which gives us lots of time to keep it open and solve remaining questions around how to use angle brackets to publish instead of shell script. But if a new JIRA makes ya'll happ(ier) feel free to open another. How else are we going to get to JBIDE-20000 ? :D

1. This JIRA needs to be renamed. publish.sh is deprecated. You want rsync.sh: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.3.x/publish/rsync.sh See examples/screenshots above which demonstrate how to pass in a -DESTINATION that's not the default server.

2. Publishing must by definition be many steps because, for the best example of JBDS, we publish to two different servers (www.qa and devstudio.redhat). We used to have a publish.sh hardcoded to do all sorts of complicated steps in one call (simply `publish.sh -jbds`) but that was deemed *Just Bad*, so we now have one generic script (rsync.sh) which can push from anywhere to anywhere else. The only caveat is that you now must call it several times to push to multiple destinations.


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