Bug 514503 - beta/RC builds cause grief in Maven
Summary: beta/RC builds cause grief in Maven
Status: NEW
Alias: None
Product: TMF
Classification: Modeling
Component: Releng (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-30 12:49 EDT by Stephan Herrmann CLA
Modified: 2017-03-30 12:49 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 2017-03-30 12:49:09 EDT 
In my 2.8.4-based DSLs, I refer to Xtext like this (in MANIFEST.MF):
 org.eclipse.xtext;bundle-version="[2.8.4,2.9.0)",
etc. 
This is done in order to prevent accidental upgrade to 2.9.0.

When I reference this DSL from a plain (non-tycho) Maven build, I was surprised to see that version range resolved to 2.9.0.rc2 or similar.

While I appreciate when rc builds are published, I don't think publishing them to Maven is a good idea. We all know, how unpredictable Maven reacts to version ranges in conjunction with various version formats.

Who expects 2.9.0.beta2 to be accepted from [2.8.4,2.9.0) ?

Internally, we have developed a habit of ranges like [2.8.4,2.8.99), but that looks much like a hack, doesn't it?


While my examples relate to artifacts preceding 2.9.0, the same can be found for more recent versions, too.