Bugzilla – Full Text Bug Listing
| Summary: | [mavenResult] Interpreting empty dependency version | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] CBI | Reporter: | Dennis Huebner <dennis.huebner> | ||||
| Component: | CBI p2 Repository Aggregator | Assignee: | Project Inbox <b3.aggregator-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | thomas | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
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.
Fixed on master with commit http://git.eclipse.org/c/b3/b3.git/commit/?id=f105ba1ab0a18ed55b9e208a05323a69c7bf8f8f [Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI. No change to assignee for resolved and verified bugs.] |
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)