[jbosstools-issues] [JBoss JIRA] (JBIDE-24514) org.jboss.tools.tests version not bumped in master

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-24514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt reassigned JBIDE-24514:
----------------------------------

    Assignee: Nick Boldt


> org.jboss.tools.tests version not bumped in master
> --------------------------------------------------
>
>                 Key: JBIDE-24514
>                 URL: https://issues.jboss.org/browse/JBIDE-24514
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: common, foundation
>    Affects Versions: 4.5.0.AM1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.5.0.AM1
>
>
> This has been failing for several days. Does no one every compile locally and see these failures? Or check the server for failing builds? [~jeffmaury] [~rob.stryker]
> {code}
> 08:48:11 Caused by: org.apache.maven.plugin.MojoFailureException: Only qualifier changed for (org.jboss.tools.tests/3.7.3.v20170419-0633). Expected to have bigger x.y.z than what is available in baseline (3.7.3.v20170414-0943)
> 08:48:11 	at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:178)
> 08:48:11 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> 08:48:11 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> 08:48:11 	... 20 more
> 08:48:11 Caused by: org.apache.maven.plugin.MojoFailureException: Only qualifier changed for (org.jboss.tools.tests/3.7.3.v20170419-0633). Expected to have bigger x.y.z than what is available in baseline (3.7.3.v20170414-0943)
> 08:48:11 	at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:172)
> 08:48:11 	... 22 more{code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-base_master/141/console
> Working on a PR to fix this now.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)