Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346295

Summary:	Why is SLF4J in our 4.1 repository
Product:	[Eclipse Project] Platform	Reporter:	John Arthorne <john.arthorne>
Component:	Releng	Assignee:	Platform-Releng-Inbox <platform-releng-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	aniefer, pwebster, remy.suen
Version:	3.7
Target Milestone:	4.1 RC2
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description John Arthorne

2011-05-18 12:09:28 EDT

Our 4.1 repository contains the following bundles:

		org.slf4j.jcl_1.6.1.*.jar
		ch.qos.logback.slf4j_0.9.27.*.jar
		ch.qos.logback.core_0.9.27.*.jar
		ch.qos.logback.classic_0.9.27.*.jar

However if you install a 4.1 build, none of those bundles get installed. We need to figure out why they are getting putting into the build, and remove them. Since we don't have a CQ for distributing these, they need to be removed (or enter CQ's if we have a good reason to include them).

The only thing that comes to mind is that Jetty has an optional dependency on SLF4J. However we should be able to exclude it since it is optional.

Comment 1 Andrew Niefer

2011-05-18 13:30:18 EDT

For some reason the builder is mirroring org.apache.commons.beanutils from the indigo repo.  I'm not sure why this is there, I'm trying a test build without it.  This is probably the source of the extra bundles showing up in the build environment.

Comment 2 Andrew Niefer

2011-05-18 14:40:19 EDT

While the test build did not complete because of bug 342853, the repository produced there did not contain these bundles.

Comment 3 John Arthorne

2011-05-19 09:57:54 EDT

Thanks Andrew!