We were embedding metadata-core and jdbc in our custom bundle other option could be embed dependency inline
Regards, Vijay Kumar J -----Original Message----- From: Du Krøger, Dennis [mailto:[email protected]] Sent: Monday, October 10, 2016 4:08 PM To: [email protected] Subject: Re: Metamodel for java 1.7 Hi Vijay, Not the cleanest solution, but since you probably need to wrap the bundle to make it work in OSGi anyway, can't you overwrite the Build-Jdk? BR, Dennis ________________________________ From: Vijay Kumar Jalagari <[email protected]> Sent: Monday, October 10, 2016 12:24:25 PM To: [email protected] Subject: RE: Metamodel for java 1.7 Hi Kasper, Yes, it java 7 compatible but in OSGI environment bundle start up is failing due to Build-Jdk 1.8 Regards, Vijay Kumar J -----Original Message----- From: Kasper Sørensen [mailto:[email protected]] Sent: Saturday, October 8, 2016 8:36 AM To: [email protected] Subject: Re: Metamodel for java 1.7 Hi Vijay, The pom does in deed specify Java 1.7 as both source as target. I believe that a JDK 8 compiler will respect that also, so the output bytecode is Java 7 compatible. Have you actually tried running MM with Java 1.7 and seen it fail, because I believe it to work. Kasper 2016-10-07 4:56 GMT-07:00 Vijay Kumar Jalagari <[email protected]>: > Hi, > > According to metamodel source its compatible with java 1.7 but OOTB > jar provided by maven artifactory is java 1.8 ( Build-Jdk: 1.8.0_77 ) > > One options is build the metamodel with 1.7 and include in required > other application but is there any better approach? > > [0] - > https://github.com/apache/metamodel/blob/master/pom.xml#L169-L176 > > > Regards, > Vijay Kumar J > >
