Skip to content

Conversation

@fedejeanne
Copy link
Contributor

What it does

Print a warning in the trace log if the Class-Path entry in the manifest file of a third-party library includes a parent folder. This might not be forbidden but it's a dangerous practice.

Contributes to: #4797

How to test

  • Launch the Runtime Workspace, making sure that tracing is enabled like this:
image
  • Import the 2 projects in this ZIP: projects.zip
  • Restart the application

Expected

This should appear in the Console output:

| main | 2026-02-03 14:26:33.814 | org.eclipse.jdt.core | /debug | org.eclipse.jdt.internal.core.ClasspathEntry | resolvedChainedLibraries | 993 | WARN: Classpath entry ../ in manifest of jar file: \a\lib\badlib.jar references a parent folder. This may cause issues like: https://github.com/eclipse-jdt/eclipse.jdt.core/issues/4797 |

Author checklist

…ipse-jdt#4797

Print a warning in the trace log if the Class-Path entry in the manifest
file of a third-party library includes a parent folder. This might not
be forbidden but it's a dangerous practice.

Contributes to:
eclipse-jdt#4797
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant