[jbosstools-issues] [JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-19056:
-------------------------------------

I enabled the master parent pom in my 4.2.x branch as nick suggested for testing purposes and the build did correctly fail, but I was getting a very strange error:

ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) on project org.jboss.tools.archives.scanner: Version of 'org.jboss.tools.archives.scanner/3.5.1.Alpha1-v20150129-1540) must be bigger than baseline one (3.6.0.Alpha1-v20150129-1119) -> [Help 1]


Cleaning out part of my ~/.m2 folder fixed the problem, (since I had previously mvn clean install'd my master)  but this concerns me.  If this thing is fragile enough to be confused by whats in my ~/.m2 folder, then I can already imagine I might have to clean that folder more often.  Nick thinks it won't be that fragile if added properly to the maintenance pom. I am skeptical. 

I will say, if this thing gets confused by my ~/.m2 folder, and I have to clean it more often, then I can see this being a big inconvenience. 

> A Mojo to validate a version (compared to baseline)
> ---------------------------------------------------
>
>                 Key: JBIDE-19056
>                 URL: https://issues.jboss.org/browse/JBIDE-19056
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 4.2.2.Final
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>
> We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released.
> Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...)



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)