RFR: 7378: Update platform to 2021-06
    Guru Hb 
    ghb at openjdk.java.net
       
    Mon Sep  6 16:47:38 UTC 2021
    
    
  
On Mon, 9 Aug 2021 22:08:14 GMT, Marcus Hirt <hirt at openjdk.org> wrote:
> ...and removing old ones.
> (Maven Artifact blablabla is not a bundle and will be ignored, automatic wrapping of such artifacts can be enabled with wrapAsBundle in target platform configuration)
This looks very interesting to solve and tycho is now capable of converting non OSGi Bundle to OSGi for maven dependency if we add ``` <pomDependencies>wrapAsBundle</pomDependencies> ``` .  Note : [https://wiki.eclipse.org/Tycho/Target_Platform#.22POM_dependencies_consider.22](https://wiki.eclipse.org/Tycho/Target_Platform#.22POM_dependencies_consider.22)  
but there is a catch .. If we use non OSGi dependency the "Bundle Symbolic name generated by tycho 2.x will be "**groupid.artifactId**"  where as the **p2-maven-plugin** (currently used for converting non OSGi to OSGi and hosting as a local p2 server convert Bundle Symbolic name to "**groupId**" (Note the missing artifactId
There are two solution i could think off and None of them are good at this point of time 
Solution 1 : Unify Core with application and remove p2-maven-plugin (+ remove releng /third-party) 
Solution 2 : Append Symbolic name with artifactId generated by p2-maven-plugin to match with the expected tycho compiler plugin (Not tested , but this might work) .
-------------
PR: https://git.openjdk.java.net/jmc/pull/301
    
    
More information about the jmc-dev
mailing list