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

[Martin Malina (JIRA)]

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

Martin Malina updated JBIDE-18772:
----------------------------------
    Git Pull Request: https://github.com/jbosstools/jbosstools-build-ci/pull/116, https://github.com/jbosstools/jbosstools-build-ci/pull/117, https://github.com/jbosstools/jbosstools-build/pull/181, https://github.com/jbosstools/jbosstools-build-sites/pull/185, https://github.com/jbosstools/jbosstools-build-sites/pull/187, https://github.com/jbdevstudio/jbdevstudio-ci/commit/d4f26761495860e86e634fc28498172d48ada97f, https://github.com/jbosstools/jbosstools-integration-tests/pull/990, https://github.com/jbosstools/jbosstools-browsersim/pull/65, https://github.com/jbosstools/jbosstools-browsersim/pull/67, https://github.com/jboss-reddeer/reddeer/pull/1104  (was: https://github.com/jbosstools/jbosstools-build-ci/pull/116, https://github.com/jbosstools/jbosstools-build-ci/pull/117, https://github.com/jbosstools/jbosstools-build/pull/181, https://github.com/jbosstools/jbosstools-build-sites/pull/185, https://github.com/jbosstools/jbosstools-build-sites/pull/187, https://github.com/jbdevstudio/jbdevstudio-ci/commit/d4f26761495860e86e634fc28498172d48ada97f, https://github.com/jbosstools/jbosstools-integration-tests/pull/990, https://github.com/jbosstools/jbosstools-browsersim/pull/65, https://github.com/jbosstools/jbosstools-browsersim/pull/67)


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