[jbosstools-issues] [JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

[Nick Boldt (JIRA)]

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

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

Yes. For simple projects (base, server, ..., central) we can use `mvn deploy -Pdeploy-to-jboss.org`.

For everyone else we can use `mvn deploy -Pdeploy-to-jboss.org -Doverride=this -Doverride=that -Doverride=the-other ...`

We might also need a "copy-or-rename stuff after it's built before calling rsync" step. Otherwise the staging & release processes can handle renames as required (eg., when we have to strip qualifiers off JBDS artifacts so they use Beta1 instead of Beta1-v20150623-1234-B456).



> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
>                 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
>
>
> 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)