Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364141 - [mavenResult] Interpreting empty dependency version
Summary: [mavenResult] Interpreting empty dependency version
Status: RESOLVED FIXED
Alias: None
Product: CBI
Classification: Technology
Component: CBI p2 Repository Aggregator (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-18 07:29 EST by Dennis Huebner CLA
Modified: 2016-09-16 15:59 EDT (History)
1 user (show)

See Also:

Attachments
Patch that produces [0.0,) for empty version strings (975 bytes, patch)
2011-11-24 07:12 EST, Achim Demelt CLA 		thomas: iplog+
Details | Diff
View All 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 Dennis Huebner CLA 2011-11-18 07:29:26 EST 
I'm producing a maven repository using b3 with mavenResult = true
All works fine. Thanks for this cool tool :)

The problem that I currently have is that bundle dependency with undefined version are not interpreted properly/at all. Here is an example.

Given is a MANIFEST.MF dependency entry:
Require-Bundle: org.eclipse.emf.ecore.xmi;visibility:=reexport

This will be interpreted as:
<dependency>
      <groupId>org.eclipse.emf</groupId>
      <artifactId>org.eclipse.emf.ecore.xmi</artifactId>
 </dependency>
which is not a valid maven dependency entry (dependencyManagement not used) because of a missing version tag.

I think that something like 0.0.0 or [0.0,) will be a corresponding maven value. (0.0.0 should work as expected see http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution)
Comment 1 Achim Demelt CLA 2011-11-24 07:12:50 EST 
Created attachment 207475 [details]
Patch that produces [0.0,) for empty version strings

This patch produces a [0.0,) Maven version entry if an OSGi dependency has no version.
Comment 2 Thomas Hallgren CLA 2011-11-24 11:20:09 EST 
Fixed on master with commit http://git.eclipse.org/c/b3/b3.git/commit/?id=f105ba1ab0a18ed55b9e208a05323a69c7bf8f8f
Comment 3 David Williams CLA 2016-09-16 15:59:42 EDT 
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI.
No change to assignee for resolved and verified bugs.]