Closed msgilligan closed 6 years ago
Like I mentioned, I think we should support both a regular and uber jar.
There was one guy in 2014 that requested (and liked) the uber jar. Is there anyone else that wants it? I vote for keeping things simple. It's pretty rare that projects go through the trouble of generating JavaDoc without using a build tool.
I wish there were a general-purpose pure-Java tool that would automatically generate a classpath from Maven/POM dependencies. (I Googled a little and didn't find anything.) In the Groovy world there are:
@Grab
annotationsI really wish there was a straightforward Java-only solution to do this sort of things. I'm surprised there isn't.
@msgilligan If you have the Maven POM would the Maven Exec Plugin serve?
@reckart I don't think so because this is used as a library, not an executable. @msgilligan what do you think of my proposed shade plugin snippet?
In general, I've found that life is simplest when a build module/submodule produces a single artifact. Whenever I make shade jars I often regret the extra complexity. You end up with two Jars that must be published/distributed/distinguished.
If the shade plugin works and you really want to continue to support this use case, let's close this PR and make a new one.
Let me know what you think @msgilligan: https://github.com/asciidoctor/asciidoclet/pull/86
Closing in favor of #86 .
Should resolve Issue #70.