-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All jbake-core dependencies are forced on you when used in another Maven project #437
Comments
Could that be the reason for binary file size difference? 2.6.0 download size is 69MB, compared to 2.5.1 having 40MB only. |
ah. honestly I wasn't aware of the optional maven dependencies while switching to gradle. so the nebula plugin seems the way to go. as for the size difference. we had a few dependency changes since 2.5.1. asciidoctorj-diagram and felxmark (as replacement for pegdown). See directory and file sizes for 2.5.1 and 2.6.0 and the dependency graph We could replace |
I'd completely forgotten about it... only noticed as I'm updating my example projects that use the plugins for a talk and forgot to include the other dependencies and thought to myself how is it even baking a site without them being declared. |
Used Nebula Optional plugin to enable optional support on dependencies.
Dependencies that provide content format support and template engine support were optional prior to 2.6.0 but are now forced on you when you include jbake-core in a project (as jbake-maven-plugin does) so you can't include just the dependencies that you require (i.e. include Freemarker but not Groovy).
Had a quick search and came across this: gradle/gradle#867
The text was updated successfully, but these errors were encountered: