[jbosstools-issues] [JBoss JIRA] (JBIDE-23212) when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-23212 at 9/26/16 1:43 PM:
-------------------------------------------------------------

Given the schedule of Tycho releases to date [1] (once every 4-5 months), I'd assume that we won't have 0.27 in time for devstudio 10.2 / jbt 4.4.2, as it's likely that 0.27 will arrive in mid December.

[1] https://wiki.eclipse.org/Tycho/Release_Notes

Therefore slipping this to 4.4.x / 4.5.0 (depends on when we move to Oxygen). 

Fix should be available for the March 2017 release, whatever that becomes (4.4.3 / 10.3.0 or 4.5.0 / 11.0.0).


was (Author: nickboldt):
Given the schedule of Tycho releases to date, I'd assume that we won't have 0.27 in time for devstudio 10.2 / jbt 4.4.2, as it's likely that 0.27 will arrive in mid December.

Therefore slipping this to 4.4.x / 4.5.0 (depends on when we move to Oxygen). 

Fix should be available for the March 2017 release, whatever that becomes (4.4.3 / 10.3.0 or 4.5.0 / 11.0.0).

> when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-23212
>                 URL: https://issues.jboss.org/browse/JBIDE-23212
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.4.1.Final
>            Reporter: Jeff MAURY
>            Assignee: Nick Boldt
>              Labels: build, tycho,
>             Fix For: 4.4.x, 4.5.0.AM1
>
>
> The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar).
> I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check



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