[ 
https://issues.apache.org/jira/browse/MYNEWT-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900427#comment-15900427
 ] 

ASF subversion and git services commented on MYNEWT-655:
--------------------------------------------------------

Commit 934b3cc1ab0e533958e5cdf0bc133798e7f2dd6d in incubator-mynewt-newt's 
branch refs/heads/1_0_0_dev from [~ccollins476]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=934b3cc 
]

MYNEWT-655 newt - Detect newt version incompat.

Correctly handle case where project imposes no newt version
restrictions.


> newt - Detect repo / newt version incompatibilities
> ---------------------------------------------------
>
>                 Key: MYNEWT-655
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-655
>             Project: Mynewt
>          Issue Type: Improvement
>            Reporter: Christopher Collins
>            Assignee: Christopher Collins
>             Fix For: v1_0_0_rel
>
>
> This is done with a separate map "repo.newt_compatibility" in the repo's 
> repository.yml file.
> Example:
> {noformat}
> repo.newt_compatibility:
>     1.0.0:
>         1.1.0: error
>         1.0.0: good
>         0.9.99: warn
>         0.9.9: error
> {noformat}
> This says that this version 1.0.0 of this repo is compatible with newt 
> versions [1.0.0, 1.1.0).  Newt versions in the range [0.9.99, 1.0.0) elicit a 
> warning message.  All other newt versions generate an error.
> A project can also indicate newt version restrictions
> Example (project.yml):
> {noformat}
> project.newt_compatibility:
>     1.1.0: error
>     1.0.0: good
>     0.9.99: warn
>     0.9.9: error
> {noformat}
> Just to be clear, the newt version numbers are *minimum* version numbers.  
> The following table:
> {noformat}
>     1.0.0: good
>     0.1.0: error
> {noformat}
> Says that newt versions >= 0.1.0 and < 1.0.0 elicit an error.  All newt 
> versions >= 1.0.0 are OK.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to