How to include application version number in HTML documentation genertated by Spring Rest Docs?
I would like to include application version number (version
from build.gradle
).
I see no way to pass some custom variables to ascidoc and use them in generated documentation. Is it possible?
spring-restdocs
add a comment |
I would like to include application version number (version
from build.gradle
).
I see no way to pass some custom variables to ascidoc and use them in generated documentation. Is it possible?
spring-restdocs
add a comment |
I would like to include application version number (version
from build.gradle
).
I see no way to pass some custom variables to ascidoc and use them in generated documentation. Is it possible?
spring-restdocs
I would like to include application version number (version
from build.gradle
).
I see no way to pass some custom variables to ascidoc and use them in generated documentation. Is it possible?
spring-restdocs
spring-restdocs
asked Nov 22 at 12:23
Bartosz Bilicki
6,34953869
6,34953869
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Passing custom variables from gradle can be done using
asciidoctor {
attributes "build=${build}"
}
Then defined attribute may be refered in adoc
file as {build}
Exactly, Gradle documentation: asciidoctor.org/docs/asciidoctor-gradle-plugin/… Maven documentation: asciidoctor.org/docs/asciidoctor-maven-plugin/… Some attributes likeproject.version
are even passed automatically.
– Florian Benz
Nov 22 at 14:15
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430953%2fhow-to-include-application-version-number-in-html-documentation-genertated-by-sp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Passing custom variables from gradle can be done using
asciidoctor {
attributes "build=${build}"
}
Then defined attribute may be refered in adoc
file as {build}
Exactly, Gradle documentation: asciidoctor.org/docs/asciidoctor-gradle-plugin/… Maven documentation: asciidoctor.org/docs/asciidoctor-maven-plugin/… Some attributes likeproject.version
are even passed automatically.
– Florian Benz
Nov 22 at 14:15
add a comment |
Passing custom variables from gradle can be done using
asciidoctor {
attributes "build=${build}"
}
Then defined attribute may be refered in adoc
file as {build}
Exactly, Gradle documentation: asciidoctor.org/docs/asciidoctor-gradle-plugin/… Maven documentation: asciidoctor.org/docs/asciidoctor-maven-plugin/… Some attributes likeproject.version
are even passed automatically.
– Florian Benz
Nov 22 at 14:15
add a comment |
Passing custom variables from gradle can be done using
asciidoctor {
attributes "build=${build}"
}
Then defined attribute may be refered in adoc
file as {build}
Passing custom variables from gradle can be done using
asciidoctor {
attributes "build=${build}"
}
Then defined attribute may be refered in adoc
file as {build}
answered Nov 22 at 12:46
Bartosz Bilicki
6,34953869
6,34953869
Exactly, Gradle documentation: asciidoctor.org/docs/asciidoctor-gradle-plugin/… Maven documentation: asciidoctor.org/docs/asciidoctor-maven-plugin/… Some attributes likeproject.version
are even passed automatically.
– Florian Benz
Nov 22 at 14:15
add a comment |
Exactly, Gradle documentation: asciidoctor.org/docs/asciidoctor-gradle-plugin/… Maven documentation: asciidoctor.org/docs/asciidoctor-maven-plugin/… Some attributes likeproject.version
are even passed automatically.
– Florian Benz
Nov 22 at 14:15
Exactly, Gradle documentation: asciidoctor.org/docs/asciidoctor-gradle-plugin/… Maven documentation: asciidoctor.org/docs/asciidoctor-maven-plugin/… Some attributes like
project.version
are even passed automatically.– Florian Benz
Nov 22 at 14:15
Exactly, Gradle documentation: asciidoctor.org/docs/asciidoctor-gradle-plugin/… Maven documentation: asciidoctor.org/docs/asciidoctor-maven-plugin/… Some attributes like
project.version
are even passed automatically.– Florian Benz
Nov 22 at 14:15
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430953%2fhow-to-include-application-version-number-in-html-documentation-genertated-by-sp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown