Yes, Kepler M2 is coming up fast! (+0 date is 9/21)

See Bug 388140 for the gory details, but we in Orbit plan to remove some 
"old" logging bundles from _active_ builds for Kepler. This does not 
effect any previous "R-build" repositories. We call this "aggressive" 
since we normally leave the past 2 or 3 versions in Orbit's active builds, 
just in case anyone needs them (and there are several legitimate cases to 
use "old bundles"). But in this case, we'd like to have only the most 
recent versions in Orbit. 

To be explicit we are talking about removing 

these three at the 0.9.7 level

ch.qos.logback.slf4j
ch.qos.logback.classic
ch.qos.logback.core

and these 5 at the 1.6.1 level

org.slf4j.api 
org.slf4j.ext
org.slf4j.jcl
org.slf4j.jul
org.slf4j.log4j

They all have replacements at a higher level (1.0.0 or 1.0.3 for the 
former, and 1.6.4 for the latter). 

The reason for this aggressive removal, in brief, is that a) it is 
strongly encouraged not to use the older ones ... they cause complications 
in builds that are not present when using the newer ones, and b) they are 
causing problems in our orbit builds, and while we could make our Orbit 
build more complicated to accommodate them, we would prefer not to do the 
extra work unless its absolutely required. 

I checked the Kepler M1 common repository and none of these were in use 
there. I know that is not a guarantee that it won't effect an individual 
Kepler project, so do let us know if this quick and sudden change effects 
you. Please comment in bug 388140 and we can discuss alternatives, if 
needed. Either restore status quo, have you fetch from old repositories, 
or ... make our Orbit build more complicated. 

Thank you, 

_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to