Bug tracker link builder : macro, attribute ?

Awesome thanks. I'll take a deeper look at the project.
I'm building using maven and tycho so Java it will be :)

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Bug-tracker-link-builder-macro-attribute-tp4755p4760.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

Jérémie is correct, you need to write an inline macro. It's the perfect case for one.

The JBoss Tools team has written a macro for linking to an issue tracker that you can build on. See:

* https://github.com/jbosstools/jbosstools-website/blob/master/_ext/asciidoctor_extensions.rb

* https://github.com/jbosstools/jbosstools-website/blob/master/_ext/asciidoctor/related_jira.rb

It would be great to pull a simplified version of this macro into the extensions lab {1} for reference.

-Dan

:1: https://github.com/asciidoctor/asciidoctor-extensions-lab

On Thu, Jun 9, 2016 at 11:56 PM, Psyko [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Awesome thanks. I'll take a deeper look at the project.
I'm building using maven and tycho so Java it will be :)

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Bug-tracker-link-builder-macro-attribute-tp4755p4760.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

--

Dan Allen | @mojavelinux | https://twitter.com/mojavelinux

Creating a generic issue Tracker macro is probably a challenge. For each tracker, you need to provide:

* An URL pattern
* A default Text pattern

The macro should be able to handle multiple trackers at the same time.

Examples:

== Bugzilla installed at the Eclipse foundation:
Issue Id is a number.

* Text: "Bug {id}"
* URL: https://bugs.eclipse.org/bugs/show_bug.cgi?id={id}

== GitHub
I think we would create one tracker for each project. Issue Id is a number.
For Asciidoctorj

* Text: "#{id}" or "asciidoctor/asciidoctorj#{id}"
* URL: https://github.com/asciidoctor/asciidoctorj/issues/{id}

And Asciidoctor.org:

* Text: "#{id}" or "asciidoctor/asciidoctor.org#{id}"
* URL: https://github.com/asciidoctor/asciidoctor.org/issues/{id}

== JIRAs
(See the JBoss Tools macro). Another example with the public Jenkins JIRA instance:
Issue Id is a String "JENKINS-35666"

* Text: "{id}"
* https://issues.jenkins-ci.org/browse/{id}

The way I see it for the moment, it would be nice to define a second parameter host or server.
issue:<id>[host, optional text]

At document level as many variables are defined as necessary (see the values above)
issue-url-eclipse
issue-text-eclipse
issue-url-jenkins
issue-text-jenkins

If no host is defined in the macro, the default variables "issue-url" or "issue-text" are used.

In the text you can write something like:

Check the related issues to this problem issue:0234[eclipse] or issue:JENKINS-35666[jenkins].
Please note that issue:ROASTER-105[jboss] is also relevant.

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Bug-tracker-link-builder-macro-attribute-tp4755p4766.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML