-
Notifications
You must be signed in to change notification settings - Fork 15
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
Eclipse Ant provision #374
Comments
With #371 the build will be changed to maven tycho build - so CI workflow will become very easy and eclipse parts can be build completely. Or did I missunderstood your request/question ? |
Yes, you have not understood this correctly. What I had hoped for was was that you could integratethe eclipse extension Point saw that the eclipse extension point for Ant tasks, sothat asciidoctor could be called from within eclipse's Ant facility directly. |
Okay. I understand that you want to use the ANT eclipse plugin to trigger asciidoc actions. But...
So what could you want to do with the editor plugin via ant?
The asciidoctor project does already provide multiple plugins/extensions. This works in CLI and should also work in eclipse as well. Is there a real benefit to use the editor plugin for ant to render? |
That's right, but we are using ant + eclipse as a DevOps environment for model-driven operations. If we had your tooling available from ant, all the phantastic output could be rendered in our toolchains. High-quality, automatic documentation on every build, after every model-driven run. Given how many features the tool has, even a part would give us a dramatic boost! |
Could you expose some or all of your execution using ant tasks in eclipse-platform Ant Extension Points? This would allow running all the ASCIIDOCTOR beauty with none of the hassle in a CI workflow!
The text was updated successfully, but these errors were encountered: