You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When versioning your resource packs and doing so inside a gradle multi-module project, it could be really usefull to have PackSquash gradle task that can have options like the sourceSets path (to know which files to include/exclude) and the outputDirectory for it.
Proposed solution
Having the ability to add a gradle plugin with the packSquash tool defining it in the build.gradle like this:
plugins {
id 'packsquash'
}
packSquash {
include 'src'// Maybe just take this by default
excluse 'some-file.txt'
outputDir rootProject.file('build/release')
}
Alternative solutions
Nothing I can think of right now
Additional context
No response
The text was updated successfully, but these errors were encountered:
As someone who prefers to use build tools that don't rely on a domain-specific language, I don't think I'm qualified enough to realize the usefulness of such a Gradle plugin. My use of Gradle has been limited to building existing projects and cobbling basic stuff together without researching how it really works.
That being said, I can see how this idea may have some technical merit, and I'd support the development of such a plugin by contributors.
Would you mind sharing more details about your Gradle workflow? How you envision the described Gradle plugin fitting into it? Why not use a task that runs the PackSquash CLI instead?
Related problem or need
When versioning your resource packs and doing so inside a gradle multi-module project, it could be really usefull to have PackSquash gradle task that can have options like the sourceSets path (to know which files to include/exclude) and the outputDirectory for it.
Proposed solution
Having the ability to add a gradle plugin with the packSquash tool defining it in the build.gradle like this:
Alternative solutions
Nothing I can think of right now
Additional context
No response
The text was updated successfully, but these errors were encountered: