asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ildar Absalyamov <ildar.absalya...@gmail.com>
Subject Re: [jira] [Updated] (ASTERIXDB-1384) Inconsistent version dependencies in POMs
Date Tue, 29 Mar 2016 22:14:38 GMT
I was thinking release plugin is changing only the versions which are explicitly set in the
pom. If the variable is used instead it becomes opaque for the release plugin.
Also note the issue applies only to the versions of dependencies, there is at least one place
in pom, where the explicit version should be kept - version of the parent.

> On Mar 29, 2016, at 15:10, Ian Maxon <imaxon@uci.edu> wrote:
> 
> This might be at least partially the release plugin's doing...
> 
> On Tue, Mar 29, 2016 at 2:24 PM, Ildar Absalyamov (JIRA) <jira@apache.org>
> wrote:
> 
>> 
>>     [
>> https://issues.apache.org/jira/browse/ASTERIXDB-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>> 
>> Ildar Absalyamov updated ASTERIXDB-1384:
>> ----------------------------------------
>>    Assignee: Chris Hillery
>> 
>>> Inconsistent version dependencies in POMs
>>> -----------------------------------------
>>> 
>>>                Key: ASTERIXDB-1384
>>>                URL:
>> https://issues.apache.org/jira/browse/ASTERIXDB-1384
>>>            Project: Apache AsterixDB
>>>         Issue Type: Improvement
>>>           Reporter: Steven Jacobs
>>>           Assignee: Chris Hillery
>>>           Priority: Minor
>>> 
>>> Some of the poms use the current-version variable for their
>> dependencies, while others hard-code the version number. It should be
>> consistent one way or the other.
>> 
>> 
>> 
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
>> 

Best regards,
Ildar


Mime
View raw message