search

flyfire / jarjar

Automatically exported from code.google.com/p/jarjar
0 stars 0 forks source link

Empty folders created in resulting archive #32

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Use a jar with folder entries
2. Run the jarjar task with a keep rule that pulls in some transitive
dependencies from the jar in step 1
3.

What is the expected output? What do you see instead?
The resulting jar is nicely created but it is polluted with empty folder
from the dependency jar. In my case, class a.b.c.D is pulled in but Jarjar
creates folder entries for a.e, a.f, a.b.g, a.b.i and so on even though
they are not needed.
I would expect these folders to not be copied since none of their content
(whether class or reasources) is required.

What version of the product are you using? On what operating system?
I'm using Ant 1.7.1 (from Maven) and Jarjar 1.0.

Please provide any additional information below.

Original issue reported on code.google.com by costin.l...@gmail.com on 25 May 2009 at 11:40

GoogleCodeExporter commented 9 years ago 
Does this issue get closed in your 1.3 release?

Original comment by kandpwel...@gmail.com on 3 May 2012 at 5:06

GoogleCodeExporter commented 9 years ago 
It looked like r133 was supposed to fix this, but I just upgraded to 1.3 and I 
am still seeing this behavior.

Original comment by kandpwel...@gmail.com on 5 May 2012 at 7:03

GoogleCodeExporter commented 9 years ago 
I still see this in version 1.4.

Original comment by ms5...@gmail.com on 6 May 2013 at 4:42

GoogleCodeExporter commented 9 years ago 
As for me, Using lib ver. 1.4 instead of 1.0 helped to solve this issue with 
empty folder

Original comment by alexklue...@gmail.com on 15 Jun 2015 at 8:05