|
Hi all,
I wondered why so main karaf modules depend on the karaf.main module. I found that karaf.main contains the sources for the OSGi core spec. Why do we have these sources in our code? Shouldn´t we just depend on the official package or at least only inline it during the build? If there is a good reason then I would like to document it in the architecture decisions page in the wiki. Christian -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com |
|
didn't we changed it because of the 1.4 build problem with java 7?
Kind regards, Andreas On Sun, Mar 18, 2012 at 14:52, Christian Schneider <[hidden email]> wrote: > Hi all, > > I wondered why so main karaf modules depend on the karaf.main module. I > found that karaf.main contains the sources for the OSGi core spec. > > Why do we have these sources in our code? Shouldn´t we just depend on the > official package or at least only inline it during the build? If there is a > good reason then I would like to document it in the architecture decisions > page in the wiki. > > Christian > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > |
|
I wondered this myself.
EIK actually strips out the OSGi classes from the karaf.main so it does not interfere with the running Karaf instance. I also noticed that the OSGi interfaces have to be on the boot classpath in addition to the system bundle. Stephen On Sun, Mar 18, 2012 at 10:30 AM, Andreas Pieber <[hidden email]> wrote: > didn't we changed it because of the 1.4 build problem with java 7? > > Kind regards, > Andreas > > On Sun, Mar 18, 2012 at 14:52, Christian Schneider > <[hidden email]> wrote: >> Hi all, >> >> I wondered why so main karaf modules depend on the karaf.main module. I >> found that karaf.main contains the sources for the OSGi core spec. >> >> Why do we have these sources in our code? Shouldn´t we just depend on the >> official package or at least only inline it during the build? If there is a >> good reason then I would like to document it in the architecture decisions >> page in the wiki. >> >> Christian >> >> -- >> Christian Schneider >> http://www.liquid-reality.de >> >> Open Source Architect >> Talend Application Integration Division http://www.talend.com >> -- Stephen Evanchik http://stephen.evanchik.com |
|
In reply to this post by Andreas Pieber
Yes, it's the reason why we did like this.
Regards JB On 03/18/2012 03:30 PM, Andreas Pieber wrote: > didn't we changed it because of the 1.4 build problem with java 7? > > Kind regards, > Andreas > > On Sun, Mar 18, 2012 at 14:52, Christian Schneider > <[hidden email]> wrote: >> Hi all, >> >> I wondered why so main karaf modules depend on the karaf.main module. I >> found that karaf.main contains the sources for the OSGi core spec. >> >> Why do we have these sources in our code? Shouldn´t we just depend on the >> official package or at least only inline it during the build? If there is a >> good reason then I would like to document it in the architecture decisions >> page in the wiki. >> >> Christian >> >> -- >> Christian Schneider >> http://www.liquid-reality.de >> >> Open Source Architect >> Talend Application Integration Division http://www.talend.com >> -- Jean-Baptiste Onofré [hidden email] http://blog.nanthrax.net Talend - http://www.talend.com |
|
Can you give some more details? I would like to document this and we
should also define when we should be able to remove the sources again. Christian Am 18.03.2012 17:23, schrieb Jean-Baptiste Onofré: > Yes, it's the reason why we did like this. > > Regards > JB > > On 03/18/2012 03:30 PM, Andreas Pieber wrote: >> didn't we changed it because of the 1.4 build problem with java 7? >> >> Kind regards, >> Andreas >> >> On Sun, Mar 18, 2012 at 14:52, Christian Schneider >> <[hidden email]> wrote: >>> Hi all, >>> >>> I wondered why so main karaf modules depend on the karaf.main module. I >>> found that karaf.main contains the sources for the OSGi core spec. >>> >>> Why do we have these sources in our code? Shouldn´t we just depend >>> on the >>> official package or at least only inline it during the build? If >>> there is a >>> good reason then I would like to document it in the architecture >>> decisions >>> page in the wiki. >>> >>> Christian >>> >>> -- >>> Christian Schneider >>> http://www.liquid-reality.de >>> >>> Open Source Architect >>> Talend Application Integration Division http://www.talend.com >>> > -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com |
| Powered by Nabble | Edit this page |
