Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upPackages build is often broken - should we support it? #483
Comments
My preference is also for option 2 - I have no issues using the jar command, it works well, and I’ve always found it more straightforward than packages even when both worked. So consider this a strong vote in favour of loving towards a 1.0.0 without packages. |
Similar to Ian's response, I think most of my work with AUT has used jars - which has been straightforward to work with. I can't recall a significant number of users who've identified using --packages over --jars, so it makes complete sense to move forward with option 2 (+1 from me)! |
+1 for (2) sgtm |
Cool. I'll leave this open for a week, and just to make sure there isn't a solid argument to keep it from any community members. |
Marking as resolved; won't support. |
ruebot commentedJun 18, 2020
Since we've moved to a newer version of Tika, we've had on-and-off trouble (mostly on!) with
aut
working with--packages
. The current state yields this:I see two options:
I can dive back into dependency tree, and do a lot of
pom.xml
surgery again to see if I can get us to a state to run--packages
again. Last time I tried this with the two 3.0.0 previews, the results were not fruitful, and I'm highly doubtful I can get it work again.aut
can be loaded by Spark to driver and executor classpaths with--jars
.If we go with option 2 (which is my preference), I'll work on getting the documentation updated.