[jbosstools-issues] [JBoss JIRA] (JBIDE-17590) Verify convention before deploying parent pom

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-17590:
----------------------------------------

Here is a first change that introduces this concept of checking convention: https://github.com/jbdevstudio/jbdevstudio-ci/commit/d06f280a82cfd23155ad4dc0adba6bbb24aaec72
Suggestion of improvements are welcome (cc [~nickboldt] [~fbricon] [~dgolovin])

> Verify convention before deploying parent pom
> ---------------------------------------------
>
>                 Key: JBIDE-17590
>                 URL: https://issues.jboss.org/browse/JBIDE-17590
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>    Affects Versions: 4.2.0.Beta3
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>
> It can happen that we forget to override some necessary properties when branching parent pom. A recent example is jbosstools-site-stream that needs to be updated from master to 4.2.luna.
> We should add to the parent pom deploy job, before we deploy, some checks that guarantee we follow our own conventions:
> Examples:
> * jbosstools-site-stream
> * TARGET_PLATFORM_VERSION_*
> A simple grep should be enough.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)