<div dir="ltr">Cool, I'll stay tune then ;)</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 26 February 2014 12:18, Karel Piwko <span dir="ltr"><<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Makes perfect sense.<br>
<br>
However, we need to agree on tag format. The hook might be useful no matter<br>
the format, for instance to check that a tag is missing in latest commit. I'll<br>
rework it next week to reflect that.<br>
<span class="HOEnZb"><font color="#888888"><br>
Karel<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Wed, 26 Feb 2014 09:51:53 +0100<br>
Corinne Krych <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>> wrote:<br>
<br>
> Hello Karel,<br>
><br>
> Yesterday, discussing with a friend who is writing his documentation using<br>
> asciidoctor:<br>
> <a href="http://beta.groovy-lang.org/docs/groovy-2.3.0-SNAPSHOT/html/documentation/" target="_blank">http://beta.groovy-lang.org/docs/groovy-2.3.0-SNAPSHOT/html/documentation/</a><br>
><br>
> Instead of using line number, he uses tag in his documentation inclusion like:<br>
><br>
> [source,groovy]<br>
> --------------------------------<br>
> include::{projectdir}/src/spec/test/DifferencesFromJavaTest.groovy[tags=innerclass_3,indent=0]<br>
> ————————————————<br>
><br>
> And in his code source he puts some tag like below:<br>
><br>
> // tag::innerclass_3[]<br>
> public class Y {<br>
> public class X {}<br>
> public X foo() {<br>
> return new X()<br>
> }<br>
> public static X createX(Y y) {<br>
> return new X(y)<br>
> }<br>
> }<br>
> // end::innerclass_3[]<br>
><br>
> I think it worth a trial. wdyt?<br>
><br>
> ++<br>
> Corinne<br>
><br>
><br>
> On 21 Feb 2014, at 11:03, Karel Piwko <<a href="mailto:kpiwko@redhat.com">kpiwko@redhat.com</a>> wrote:<br>
><br>
> > I've created following Git hook -<br>
> > <a href="https://github.com/kpiwko/asciidoc-git-hooks" target="_blank">https://github.com/kpiwko/asciidoc-git-hooks</a><br>
> ><br>
> > Let me know if you like it and we can start using it improving our<br>
> > documentation kept DRY experience.<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Karel<br>
> > _______________________________________________<br>
> > aerogear-dev mailing list<br>
> > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div>