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

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

Thanks for making this change and providing feedback Martin.
I agree with all those points. About 2.2, note that in the parent pom we're also hardcoding a version (referenced via a property) https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L794 . It seems actually correct to do that. In some near future, we'll hopefully release the scripts when necessary.
However, most of those issues wouldn't exist if you were just deploying to Nexus ;).

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