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

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

Thanks for moving this forward.
So now, we deploy p2 repositories with "mvn deploy", isn't it cool?

{quote}also fix references to obsolete jbosstools-nightly-staging-composite and instead uses upstream jbosstools-site from parent pom, so it's easier to override at build time{quote}
I believe for aggregate we do really want to reference the composite, otherwise, we aggregate against the latest aggregate site, which means that we won't see any change. But maybe this comment only applies to central and early access (in which case it's totally fine)?

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