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

Bug 509038

Summary:	Confusing output on console when starting Neon
Product:	[Tools] Buildship	Reporter:	Gunnar Wagenknecht <gunnar>
Component:	General	Assignee:	Project Inbox <buildship-inbox>
Status:	CLOSED MOVED	QA Contact:
Severity:	normal
Priority:	P3	CC:	csdonat, karim_ragab, st.oehme
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:
Bug Depends on:
Bug Blocks:	517319

Description Gunnar Wagenknecht

2016-12-11 11:35:46 EST

I just downloaded Eclipse Neon Committers package an ran it from the console:

[:~/Downloads/Eclipse] $ Eclipse.app/Contents/MacOS/eclipse -protect base
log4j:WARN No appenders could be found for logger (com.gradleware.tooling.toolingutils.distribution.PublishedGradleVersions).
log4j:WARN Please initialize the log4j system properly.

1) Can you clarify if the namspace com.gradleware.tooling is intentional, i.e. Buildship does not include/download code not hosted at Eclipse?

2) Is there a bug open for fixing the log4j warning?

Comment 1 Donat Csikos

2016-12-12 12:08:36 EST

Hi Gunnar,

The message comes from a library called tooling-commons. We develop this library along with Buildship and we always create a CQ for its releases.

We have no issue open for the warning message, feel free to open one. Btw, the Gradle Tooling API module also uses slf4j. If you have an advice how to hook it into Eclipse then please share it with us.

Comment 2 Stefan Oehme

2016-12-12 12:11:15 EST

Eclipse usually provides an slf4j implementation.

Comment 3 Gunnar Wagenknecht

2016-12-12 12:13:29 EST

That's interesting. The warning message is from LOG4J. I'll have to dig deeper. :)

Comment 4 karim ragab

2017-01-24 06:25:38 EST

Are there any updates on this issue?

Comment 5 Donat Csikos

2017-02-08 11:11:24 EST

We are in the process of migrating our issues to GitHub.  We've created an issue for this report: https://github.com/eclipse/buildship/issues/349 Let's continue the conversation there.