[jbosstools-issues] [JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

[Nick Boldt (JIRA)]

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

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

The same build produces identical content for JBT/JBDS Central and JBT/JBDS EA are published to two places -- once for JBT and again for JBDS. Because JBDS content has to live on a different server, even if it's the identical bits.

https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/central-site/pom.xml#L50-136

> Include publish steps in pom files
> ----------------------------------
>
>                 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)