Closed jmini closed 2 years ago
The CBI Aggregator configuration file SDK4Mvn.aggr contains some indication called "mavenMappings" describing how to go from the Bundle Symbolic name and the version to the library coordinates in Maven Central.
Example:
<mavenMappings namePattern="(org\.eclipse\.jdt)\.core\.compiler\.batch" groupId="$1" artifactId="ecj"/> <mavenMappings namePattern="(org\.eclipse\.jdt)(.*)" groupId="$1" artifactId="$1$2"/> <mavenMappings namePattern="(org\.eclipse\.pde)(.*)" groupId="$1" artifactId="$1$2"/> ...
The BOM file created by this project should also consider those mappings.
As a result of this change, bundle com.ibm.icu (version 64.2.0.v20190507-1337) should be turned to:
com.ibm.icu
64.2.0.v20190507-1337
<dependency> <groupId>com.ibm.icu</groupId> <artifactId>icu4j</artifactId> <version>64.2</version> </dependency>
See https://github.com/diffplug/goomph/issues/167 for the related work in Groomph.
The CBI Aggregator configuration file SDK4Mvn.aggr contains some indication called "mavenMappings" describing how to go from the Bundle Symbolic name and the version to the library coordinates in Maven Central.
Example:
The BOM file created by this project should also consider those mappings.
Example:
As a result of this change, bundle
com.ibm.icu
(version64.2.0.v20190507-1337
) should be turned to:See https://github.com/diffplug/goomph/issues/167 for the related work in Groomph.