Skip to content
New issue

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

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

Already on GitHub? # to your account

Empty "directories" remain in output jar after using zap #50

Closed
acourtneybrown opened this issue Jan 22, 2024 · 0 comments · Fixed by #54
Closed

Empty "directories" remain in output jar after using zap #50

acourtneybrown opened this issue Jan 22, 2024 · 0 comments · Fixed by #54

Comments

@acourtneybrown
Copy link

Looking for some guidance and input here. After using the zap rule to remove some unwanted packages from the output jar, I still see the directory tree above the zapped files/packages still exist in the output jar. For example, with the following rule:

"zap org.threeten.**"

I still see the following entries in the output jarfile (just directories & a properties file, but no classes):

org/threeten/
org/threeten/bp/
org/threeten/bp/TZDB.dat
org/threeten/bp/chrono/
org/threeten/bp/format/
org/threeten/bp/format/ChronologyText.properties
org/threeten/bp/jdk8/
org/threeten/bp/temporal/
org/threeten/bp/zone/

Was wondering what it would take to avoid emitting the "empty" directories in the output jar? I'm also happy to take a look if you can point me in the right direction in the code.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant