Closed xabriel closed 5 years ago
Thanks for reporting this, @xabriel!
I'm not sure what's going on, since the Jar looks fine when built locally. I'll look into it because we want to publish that shaded Jar to make it easy to work with Spark.
I think the problem is that JitPack uses the install task and that doesn't have a dependency on the shadowJar task. We've added it to the build task instead. I'll update and tag a new release shortly.
@xabriel, can you check version 0.5.0?
Jar looks legit now:
$ pwd
/Users/xcollazo/.m2/repository/com/github/Netflix/iceberg/iceberg-runtime/0.5.0
$ jar -tf iceberg-runtime-0.5.0.jar | wc -l
18824
Thanks!
If I build myself iceberg, I get a proper iceberg-runtime jar:
Produces a fat jar for runtime:
(
jar -tf
lists the content of a jar file. )But when I pull this jar from JitPack, with, say,
mvn
, the jar is empty, only including manifest file:I can repro on 0.4.1 and 0.4.0 so it doesn't seem to be a one off.