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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-18772:
----------------------------------------

Progress for that was reported by error to JBIDE-13835 . The following change was applied: https://github.com/jbosstools/jbosstools-build-sites/pull/185
{quote}
PR for aggregates was merged, so we can now deploy them with "mvn deploy" (it will invoke rsync.sh under the hood). Next step is to update CI jobs for JBoss Tools.
Nick Boldt pointed that since discovery sites are currently shared between JBT and JBDS ( JBIDE-19025 ), we'll still need some extra steps to deploy central and EA snapshots.
{quote}

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