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

[Mickael Istria (JIRA)]

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

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

{quote}Re: the Take 2 solution... that looks OK but ONLY for project builds.{quote}
Ok, so we could move this to parent pom. However, there are other thing we deploy (via regular Nexus) that depend on this parent pom and that won't like this plugin. Is it possible to make the rsync.sh just "warn" when the source folder ("target/repository") doesn't exist?

{quote}Aggregate builds need TWO pushes [one into builds, one into updates]{quote}
Ok. We can add an additional invocation of the rsync.sh in the aggregate.

{quote}and the matrix job that handles webtools/central/EA must make sure it's passing in the correct paths, since the JOB_NAME doesn't include the name of the matrix config (eg., webtools-site, central-site, earlyaccess-site). {quote}
I plan to make the deploy url a property that can be overriden via CLI.
This approach makes that we'll slowly prefer avoiding JOB_NAME and other Jenkins property in favor of properties that are inside the pom directly.

> 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: Feature Request
>          Components: build
>            Reporter: Max Rydahl Andersen
>            Assignee: Mickael Istria
>             Fix For: 4.3.0.Alpha2
>
>
> 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.11#6341)