[jbosstools-issues] [JBoss JIRA] (JBIDE-23290) Move parent pom to AM2

Nick Boldt (JIRA) issues at jboss.org
Wed Oct 5 11:42:00 EDT 2016


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

Nick Boldt commented on JBIDE-23290:
------------------------------------

I believe the problem here is that I forgot to bump the version after releasing the AM1 bits. 

Solution:

https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/0ce86095c7fb8fe61ae10c287f1949cffe8162b4
https://github.com/jbosstools/jbosstools-build/commit/ace5f7a8ff4e7320eb8e983d2e748d37cd4f6616

> Move parent pom to AM2
> ----------------------
>
>                 Key: JBIDE-23290
>                 URL: https://issues.jboss.org/browse/JBIDE-23290
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: build
>    Affects Versions: 4.4.2.AM2
>            Reporter: Martin Malina
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 4.4.2.AM2
>
>
> Parent pom [1] and hence all the builds still show AM1, but we're already one week into sprint 121 = AM2. I could just create a PR for the change. But I wonder what happened. Anything went wrong? This change is supposed to be part of the release process after each sprint, no?
> [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L15



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list