Open johnrengelman opened 8 years ago
We're not quite ready to move that into this repository because research is still needed. I'm doing that prototype work in the following two repositories:
At the moment, the neo4j-slide-types is a bit ahead, but they are both based on the same work. This is a tough problem to solve because there's a careful exchange we have to strike between the Gradle build and the Gulp build. And there's a question of who owns which task. Until we get it sorted out, I think we don't want to avoid having the build in a third place (on the other hand, we could migrate the prototype into this repository).
Good points and I understand the difficulty. There is alternatively the asset-pipelin plugin that could be used for processing assets instead of Gulp in the Gradle build. @craigburke has also done some work in a Gradle plugin that resolves NPM and bower dependencies natively in Gradle.
Agreed, I've had both the asset-pipeline plugin and the client dependencies plugin on my list to check out. Still, this remains a tough challenge. I'm kind of disappointed with how little native JavaScript support Gradle has, but I certainly appreciate the work by plugin authors like @craigburke.
I recently evaluated the asset-pipeline for a separate project and was a bit frustrated it didn't allow me to customize the location of the inputs and outputs and that there is no way to make the output layout mirror the input layout (it flattens the structure). In this case, we can probably deal with that.
Was looking for a definitive example of using asciidoctorj and bespoke.js together in a Gradle build.