Comments (4)
The proper way to solve this problem is to prefix the name of every include file with an underscore (_
) or put the include files in a directory that begins with an underscore. The plugin is configured to skip all files that begin with this character.
If that solution presents a problem, I would suggest adding an include / exclude filter rather than having the sourceDocumentName accept a list of files. The sourceDocumentName is there to be used when you are building a single master and want to be able to communicate that to users of the project. If you are still hoping to be able to list the specific AsciiDoc files to process, then I would suggest introducing a mutually exclusive property sourceDocumentNames.
from asciidoctor-gradle-plugin.
My sentiments exactly. Adding Set<String> sourceDocumentNames
may serve to filter out which files should be processed instead of forcing developers to rename files with a leading _ (which or course is an option they can exercise at any time). This new property would have precendence over the single sourceDocumentName
, same as backends
has precendence over backend
. WDYT?
from asciidoctor-gradle-plugin.
@mojavelinux Thanks for the solution. But I think the idea of @aalmiray fits better to our needs, because we would then be able to specify which files to process and don't have to rename the files.
from asciidoctor-gradle-plugin.
Sounds good to me!
from asciidoctor-gradle-plugin.
Related Issues (20)
- Custom AsciidoctorTask task needs sourceDir HOT 1
- What's the way to expose "Last updated" to current time on footer tag in adoc?
- Cannot implement plugin by using task avoidance
- JavaExecSpec.main property deprecated warning and will be removed in Gradle 9.0
- Fix GEMs integration test under Windows
- Enable slides & slides-export projects
- Enable leanpub project
- Supplying closures to asciidoctorj.docExtensions causes execution issues
- Property "inProcess" is no longer available while updating to 4.0.0 HOT 3
- Can't use custom Gem (Bad file descriptor) HOT 2
- v4.0.0 compatibility issue with Java 8 HOT 8
- Invalid description in published POM HOT 5
- 4.0.x timeouts (runs out of memory?)
- Plugin includes multiple versions of the same dependency
- Unable to use 4.0 in precompiled script plugin HOT 6
- Allow null attributes to be passed through HOT 1
- Fails to require GEMs HOT 11
- Regression with missing task dependency for additional configurations
- Gems don't work with Gradle >= 8.7 HOT 8
- Collections are not allowed HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from asciidoctor-gradle-plugin.