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

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

build-sites and product both use the parent pom, because they inherit a ton of variables from there, including target platform definitions and URLs for upstream projects.

So... you're wrong there. (But you're right about targetplatforms-matrix - it doesn't use the parent pom.)

But as long as this new system employs a profile to fire rsync using default params, I'm *not -1* on using this new mojo approach. 

We'll just need to encode all the stuff I have in the Jenkins configs for aggregates, target platforms, discovery, browsersim-standalone, and product builds into <ugly><xml><blocks> instead of `simple shell`, but hey, that's the price of portability. :D

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