Using PlantUML and blockdiag with asciidoctor

On 13 Feb 2014, at 00:33, mojavelinux [via Asciidoctor :: Discussion] <[hidden email]> wrote:

> One thing I would change in the pull request though is to preserve the ability to import the extensions with and without auto-registration. Thus, I recommend the following structure under lib:

All done. If the pull request looks ok now would you mind doing the following repo admin changes?
- Merge the pull request
- Rename the repo to asciidoctor-diagram
- Enable the travis service hook

Pepijn

---

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

http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1454.html

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

On 13 Feb 2014, at 00:33, mojavelinux [via Asciidoctor :: Discussion] <[hidden email]> wrote:

> One thing I would change in the pull request though is to preserve the ability to import the extensions with and without auto-registration. Thus, I recommend the following structure under lib:

All done. If the pull request looks ok now would you mind doing the following repo admin changes?
- Merge the pull request
- Rename the repo to asciidoctor-diagram
- Enable the travis service hook

Pepijn

---

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

http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1454.html

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

Thanks Dan. Just published to rubygems.org. Version is 1.0.1 due to wrong homepage URL in gemspec.

Now all that's left to do is write that blog post...

mojavelinux wrote

All set! And the build is green!

---

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

http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1464.html

To unsubscribe from Using PlantUML and blockdiag with asciidoctor, click here.
NAML

Yes, asciidoctor is MIT licensed. This is essentially 'do what you want; don't blame me if it blows up your computer'.
The apache license has some additional provisions for patents, copyright assignment and such. It's a nice license because that way contributors can't stab you in the back. :)

I MIT licensed asciidoctor-diagram itself as well, but the dependencies are not. I'm using the ASLv2 version of plantuml and the LGPLv3 version of ditaa. Those are both ok; neither is 'viral' in the context we're using them. They're external dependencies, so it's not up to me to change the license.

The issue with ditaa 0.9 (and the plantuml version that supports ditaa) is that it's GPLv2 licensed. I personally don't like GPL; too intrusive. The problem here is that if you make a 'derivative work' based on a GPL project, then the derivative work must be GPL licensed too. Derivative work is interpreted very widely in GPL. As soon as you link to a library in any way (static or dynamic, doesn't matter) you've made a derivative work. Translated to Java, if you call a single method of a class that's GPL licensed, your code also needs to be GPL licensed. LGPL relaxes this a bit and allows dynamic linking. That's why I had to make the custom build of ditaa.

Pepijn

On 13-02-14 08:51, asotobu [via Asciidoctor :: Discussion] wrote:

BTW. I am not expert in licenses but I think that Asciidoctor has a really good free license (MIT) which is like APLv2. Am I right?

2014-02-13 8:47 GMT+01:00 pepijnve [via Asciidoctor :: Discussion] <[hidden email]>:

Thanks Dan. Just published to rubygems.org. Version is 1.0.1 due to wrong homepage URL in gemspec.

Now all that's left to do is write that blog post...

mojavelinux wrote

All set! And the build is green!

---

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

http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1464.html

To unsubscribe from Using PlantUML and blockdiag with asciidoctor, click here.
NAML

--
+----------------------------------------------------------+
  Alex Soto Bueno - Computer Engineer
  www.lordofthejars.com
+----------------------------------------------------------+

---

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

http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1465.html

To unsubscribe from Using PlantUML and blockdiag with asciidoctor, click here.
NAML

---

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

http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1466.html

To unsubscribe from Using PlantUML and blockdiag with asciidoctor, click here.
NAML

Examples added. They’re not very inspired, so if you have any better suggestions feel free to let me know :)

Pepijn

On 13 Feb 2014, at 23:10, mojavelinux [via Asciidoctor :: Discussion] <[hidden email]> wrote:

That's exactly what I was thinking. Asciidoctor 1.5.0 adds the -r flag for requiring additional libraries, but until then a caller script is necessary.

---

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

http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1474.html

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

Actually, I feel quite interested in what leona313 mentioned about the QR code thing. You seem to be professional, could you tell me something about qrcode.writer supoorted by java?

---

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

http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1949.html

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