[rt-pmc] [CQ 4086] logback classic Version: 0.9.18 (PB CQ3651)

[emo-ip-team@xxxxxxxxxxx]

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=4086





--- Comment #5 from Glyn Normington <gnormington@xxxxxxxxxx>  2010-05-11 13:42:18 ---
(In reply to comment #4)
> The question that comes up for me is if you are shipping the modified logback
> code as logback version X then people do not expect it to be modified.  This is
> the sort of case where we should consider putting the bundle in our namespace. 
> Not sure what to do about the packages though.
> 

The bundle symbolic name is prepended, as is the jar file name, to bring it
into our namespace, but you're right that the packages are unaffected. However,
the Virgo design ensures this doesn't matter.

Firstly, the woven behaviour does not affect the function of LogBack in a
backward incompatible manner. Essentially it just increases the function with a
slight performance impact.

Secondly, the woven bundle is installed in Virgo's kernel region and so is only
directly accessible to other bundles installed in the kernel region which is a
very limited category of Virgo platform code rather than general application
code, which runs in the user region. Then Virgo controls which packages are
exposed into the user region where general applications run. Virgo does not
expose any LogBack packages to the user region - rather it exposes just the
slf4j and commons logging APIs which are implemented using LogBack.

Hope that helps!


-- 
Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the CQ.