Populate attributes that map to artifact coordinates about asciidoctor-gradle-plugin

[aalmiray]

Alright, does this mean documents have access to variables such as ${project-artifactId} ? What's the naming convention for variables that may have a common root (such as project)? Alternatives are

• underscore as separator, e.g, project_artifactId
• dot as separator, e.g, project.artifactId
• camel case, e.g, projectArtifactId

More over, Maven proposes names such as 'groupId' and 'artifactId' where as gradle favors 'group' and 'name'. Whichever name those build tools use internally we should have a convention within asciidoctor (maven's, gradle's or our own).

[mojavelinux]

I agree we should use something that doesn't bind it to the conventions of a build tool. I'm partial to "group", "artifact" and "version", but I'd be open to "name" instead of "artifact".

The dot separator won't work in AsciiDoc since it's not a legal attribute name character. In Asciidoctor 1.5.0 or 1.6.0 we're going to make spaces, underscores and hyphens insignificant, so you can write it in whatever style you want and it will resolve to the same name.

I think internally, it makes the most sense to use a hyphen, since that is the character used by several existing built-in attributes.

• project-artifact (or project-name)
• project-group
• project-version

wdyt?

We need to sync with the Maven plugin on this too. cc: @LightGuard

[aalmiray]

Agreed. My gut feeling says "project-name" is a much better choice 😉

[aalmiray]

I'm leanign towards

• project-name
• project-group
• project-version

Will take this issue this week.