Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure spring-jcl is used in the generated Eclipse classpath instead of commons-logging [SPR-15930] #20484

Closed
spring-issuemaster opened this issue Sep 6, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

commented Sep 6, 2017

Sam Brannen opened SPR-15930 and commented

Status Quo

Changes in #16455 pushed all project dependencies to the end of the Eclipse classpath.

However, with the recent introduction of the spring-jcl module, log4j is no longer used when executing tests within the Eclipse IDE. Consequently, we see thousands of lines of unwanted log statements written to the console using STD_ERR (since JUL logs INFO messages to STD_ERR by default).

Manual Work-around

Manually move the spring-jcl classpath entry before any third-party JARs in the generated Eclipse .classpath file.

Deliverables

  • Modify the ide.gradle script so that spring-jcl comes before any third-party JAR in the generated Eclipse .classpath
    • Implemented differently

Issue Links:

  • #16455 Eclipse project dependencies override locally declared Gradle dependencies

Referenced from: commits 8acb8ae

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented Sep 7, 2017

Sam Brannen commented

Resolved by excluding commons-logging in the spring-test Gradle build in commit: 8acb8ae

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.