From sgilda at redhat.com Tue Sep 2 12:28:33 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 02 Sep 2014 12:28:33 -0400
Subject: [windup-dev] Reports looking a little odd:
In-Reply-To: <CAEp_U4EDwoU2QVXBZ_OW4OYqw2Of4gF4qiWdRVioEEO8XpfZTg@mail.gmail.com>
References: <CAEp_U4EDwoU2QVXBZ_OW4OYqw2Of4gF4qiWdRVioEEO8XpfZTg@mail.gmail.com>
Message-ID: <5405F031.6050702@redhat.com>
Hi Lincoln,
How did you generate the reports? Did you run actual applications
through Windup? Can you provide some details?
Thanks,
Sande
On 08/29/2014 04:32 PM, Lincoln Baxter, III wrote:
> See screen shots.. but good news is that we are actually generating
> information that shows up! Let's keep up the good work!
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140902/a7fc6477/attachment.html
From bdavis at redhat.com Tue Sep 2 12:40:33 2014
From: bdavis at redhat.com (Brad Davis)
Date: Tue, 2 Sep 2014 12:40:33 -0400 (EDT)
Subject: [windup-dev] Reports looking a little odd:
In-Reply-To: <CAEp_U4EDwoU2QVXBZ_OW4OYqw2Of4gF4qiWdRVioEEO8XpfZTg@mail.gmail.com>
References: <CAEp_U4EDwoU2QVXBZ_OW4OYqw2Of4gF4qiWdRVioEEO8XpfZTg@mail.gmail.com>
Message-ID: <846343038.24967905.1409676033876.JavaMail.zimbra@redhat.com>
Doesn't look like the rules are providing proper feedback on the class report that was shown, but at least it is populating and generating reports, and that is indeed good progress.
Brad Davis
Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Friday, August 29, 2014 4:32:50 PM
Subject: [windup-dev] Reports looking a little odd:
See screen shots.. but good news is that we are actually generating information that shows up! Let's keep up the good work!
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
From lincolnbaxter at gmail.com Tue Sep 2 15:30:00 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 2 Sep 2014 15:30:00 -0400
Subject: [windup-dev] Fwd: More Windup Details
In-Reply-To: <2C2D788A-DB08-4BB2-B446-38E0BA8C2235@redhat.com>
References: <2C2D788A-DB08-4BB2-B446-38E0BA8C2235@redhat.com>
Message-ID: <CAEp_U4FnaRmfnTgrYeQsyzZ+75gptdu8bcNRLUbpTNUL_UeY-A@mail.gmail.com>
Thanks Brad,
How can we identify these classes? Is there an example of this or some
documentation that you can point us to?
Thanks again!
~Lincoln
---------- Forwarded message ----------
From: Brad Davis <bdavis at redhat.com>
Date: Tue, Sep 2, 2014 at 6:15 AM
Subject: More Windup Details
To: Lincoln Baxter III <lincolnbaxter at gmail.com>
Hey. Here is another detail you should be aware of for windup.
In legacy ejb, the solution to ejb stubs were precompiled ejb classes. You
will find them in old Weblogic and websphere deployments.
So, there should be a rule too that makes a class as "generated". Otherwise
people get them in their report and again they have no control over them,
so it's just static to report on them. You can probably use them, though,
to get information on the ejb. But, I think mostly the info you will need
about the ejb is the implementation class and it's meta information, which
is a combination of the ejb XML, the ejb vendor XML, and the java class
itself.
Brad Davis
Red Hat Consulting
Email: bdavis at redhat.com | c:980.226.7865 |http://www.redhat.com
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140902/4444060a/attachment.html
From lincolnbaxter at gmail.com Tue Sep 2 16:37:19 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 2 Sep 2014 16:37:19 -0400
Subject: [windup-dev] Windup 1 vs 2 comparison - automated
In-Reply-To: <5403A5C4.7030400@redhat.com>
References: <5403A5C4.7030400@redhat.com>
Message-ID: <CAEp_U4GL9rmG_zjFUTz=GEf1UT+++e1ZCAwwV6Wkca21SEwANg@mail.gmail.com>
Hmm... I am unable to view those files. 404 (I am on the VPN) Could you
grant public access? Thanks!
On Sun, Aug 31, 2014 at 6:46 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Hi all,
>
> I've finished automation of $subj.
> In terms of speed, memory, and links to the reports and logs next to
> each other, in a matrix.
> Check the results here:
>
> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02/Results.html
> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02.zip
>
> There are some issues with Windup 2.x - namely, failing with exceptions
> inside of rules, not reacting to multiple --packages.
>
> It needs a bit of setup - the test apps need to be at given relative paths.
> Let me know if you are interested in running this for yourself.
>
> I hope you'll find this useful.
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140902/3e925a5a/attachment.html
From jsightle at redhat.com Tue Sep 2 21:10:07 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Tue, 02 Sep 2014 21:10:07 -0400
Subject: [windup-dev] Reports looking a little odd:
In-Reply-To: <846343038.24967905.1409676033876.JavaMail.zimbra@redhat.com>
References: <CAEp_U4EDwoU2QVXBZ_OW4OYqw2Of4gF4qiWdRVioEEO8XpfZTg@mail.gmail.com>
<846343038.24967905.1409676033876.JavaMail.zimbra@redhat.com>
Message-ID: <54066A6F.9010800@redhat.com>
I think the section that he showed did not have any packages that had
been marked by the rules. It shouldn't have the big empty space there,
though, obviously. :)
Lincoln, were the pie charts appearing in other parts of the report?
On 09/02/2014 12:40 PM, Brad Davis wrote:
> Doesn't look like the rules are providing proper feedback on the class report that was shown, but at least it is populating and generating reports, and that is indeed good progress.
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Friday, August 29, 2014 4:32:50 PM
> Subject: [windup-dev] Reports looking a little odd:
>
> See screen shots.. but good news is that we are actually generating information that shows up! Let's keep up the good work!
>
>
>
From ozizka at redhat.com Tue Sep 2 22:39:06 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 03 Sep 2014 04:39:06 +0200
Subject: [windup-dev] Wiki links trick for colon
Message-ID: <54067F4A.3050200@redhat.com>
Hi all,
to save you some time figuring it out:
GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
like this:
A) [blah](Foo%3A-Bar)
B) [blah](./Foo:-Bar)
C) [blah](./Foo: Bar)
D) If all fails - full URL.
HTH,
Ondra
From ozizka at redhat.com Tue Sep 2 23:11:29 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 03 Sep 2014 05:11:29 +0200
Subject: [windup-dev] Status update - Decompiler - WINDUP-235
Message-ID: <540686E1.80301@redhat.com>
Hi,
update on WINDUP-235:
Procyon's API is a bit low-level.
There's a package procyon-decompilertools, whose API is a bit weird and
tangled, and of course, without a bit of javadoc.
That package worked for .jar decompilation since that's the use case for
that package. Decompiling .class is not.
Procyon Wiki says it should be able to decompile a .class file, but it
is not - an ITypeLoader impl to get it from a filesystem is missing.
More, I think picking up from the .jar one by one would be slow.
I'm going to implement it so it would decompile files as accepted by a
filter, in one pass over given .jar.
Another approach is to move this to higher level, and when asked to
decompile "all classes in org.mycompany.*", query the graph for where
they are, and then decompile all classes from those jars, again, using a
filter.
Still, querying for all classes would be slow. So I suggest to store an
information about what jar contains which packages in the graph (if we
don't yet), WDYT?
And lastly - one idea - not sure how much time Windup spends on
comparing package prefixes, but we could build a package tree in the
graph when scanning, and when looking for classes from given package
org.foo.*, we could select with Gremlin:
PackageModel[name=org] -- contains --> PackageModel[name=foo] --
contains --> JavaClassModel .loop()
That could be faster when the numbers of classes in the projects get to
hundreds of thousands.
Ondra
From lincolnbaxter at gmail.com Tue Sep 2 23:47:24 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 2 Sep 2014 23:47:24 -0400
Subject: [windup-dev] Reports looking a little odd:
In-Reply-To: <54066A6F.9010800@redhat.com>
References: <CAEp_U4EDwoU2QVXBZ_OW4OYqw2Of4gF4qiWdRVioEEO8XpfZTg@mail.gmail.com>
<846343038.24967905.1409676033876.JavaMail.zimbra@redhat.com>
<54066A6F.9010800@redhat.com>
Message-ID: <CAEp_U4GKviP4XYZpB5HR2XaGVc7W5V8zkk_SDkNub_KuQ5EB=Q@mail.gmail.com>
Nope. No charts. I ran windup via:
https://github.com/windup/windup/wiki/Execute-Windup (obviously i built
from source first :)
On Tue, Sep 2, 2014 at 9:10 PM, Jess Sightler <jsightle at redhat.com> wrote:
> I think the section that he showed did not have any packages that had
> been marked by the rules. It shouldn't have the big empty space there,
> though, obviously. :)
>
> Lincoln, were the pie charts appearing in other parts of the report?
>
> On 09/02/2014 12:40 PM, Brad Davis wrote:
> > Doesn't look like the rules are providing proper feedback on the class
> report that was shown, but at least it is populating and generating
> reports, and that is indeed good progress.
> >
> > Brad Davis
> > Red Hat Consulting
> > Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
> >
> >
> > ----- Original Message -----
> > From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> > To: "Windup-dev List" <windup-dev at lists.jboss.org>
> > Sent: Friday, August 29, 2014 4:32:50 PM
> > Subject: [windup-dev] Reports looking a little odd:
> >
> > See screen shots.. but good news is that we are actually generating
> information that shows up! Let's keep up the good work!
> >
> >
> >
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140902/f63402b9/attachment-0001.html
From sgilda at redhat.com Wed Sep 3 07:34:53 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 03 Sep 2014 07:34:53 -0400
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <54067F4A.3050200@redhat.com>
References: <54067F4A.3050200@redhat.com>
Message-ID: <5406FCDD.8000600@redhat.com>
Hi Ondra,
Should we replace the colons in the page titles with '_' or something
else to make it easier? For example 'Foo_BarI don't mind doing that and
it shouldn't take too long.
Thanks,
Sande
On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
> Hi all,
>
> to save you some time figuring it out:
> GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
> like this:
>
> A) [blah](Foo%3A-Bar)
> B) [blah](./Foo:-Bar)
> C) [blah](./Foo: Bar)
> D) If all fails - full URL.
>
> HTH,
> Ondra
From lincolnbaxter at gmail.com Wed Sep 3 10:47:47 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 03 Sep 2014 14:47:47 +0000
Subject: [windup-dev] Invitation: Windup Jira Triage @ Thu Sep 4,
2014 10am - 11am (Lincoln Baxter, III)
Message-ID: <20cf300e55c9ca7ecc05022a5148@google.com>
You have been invited to the following event.
Title: Windup Jira Triage
When: Thu Sep 4, 2014 10am - 11am Eastern Time
Calendar: Lincoln Baxter, III
Who:
* Lincoln Baxter, III - organizer
* windup-dev at lists.jboss.org
Event details:
https://www.google.com/calendar/event?action=VIEW&eid=cDFjMmRkMjV0YW45OGU2aHJuYTNiYmttazAgd2luZHVwLWRldkBsaXN0cy5qYm9zcy5vcmc&tok=MjMjbGluY29sbmJheHRlckBnbWFpbC5jb20xOGFhZGY0Y2E1MDBmZTFjYTUyNDIyMzBiZjY3MmVkYmZhYTQ0ODVh&ctz=America/New_York&hl=en
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account
windup-dev at lists.jboss.org because you are an attendee of this event.
To stop receiving future notifications for this event, decline this event.
Alternatively you can sign up for a Google account at
https://www.google.com/calendar/ and control your notification settings for
your entire calendar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/2857756e/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 1062 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/2857756e/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 1090 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/2857756e/attachment-0001.bin
From lincolnbaxter at gmail.com Wed Sep 3 11:18:20 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 3 Sep 2014 11:18:20 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2014-09-03
Message-ID: <CAEp_U4Ff-3iWQyTnr_ievzHs3sQJ-aH8y4Liq=1KiDxNjZ7Czw@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-03-14.05.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-03-14.05.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-03-14.05.log.html
Meeting summary
---------------
* Agenda (lincolnthree, 14:05:53)
* Status Reports (lincolnthree, 14:06:01)
* Windup Overall Status and Progress (lincolnthree, 14:06:11)
* Status Reports (lincolnthree, 14:11:24)
* Working on Decompiling - Procyon single .class . WINDUP-235
(ozizka, 14:12:39)
* Done WINDUP-253 - Refactored WindupProcessor a bit (ozizka,
14:13:19)
* About to do WINDUP-250 Analyze data flow, find where and how to
prune decompiling (ozizka, 14:13:41)
* Editing the wiki with Sande, crystalyzing the structure, linking the
bits together (ozizka, 14:14:10)
* Not done - just coded, about to be reviewed and updated (ozizka,
14:14:51)
* I have been working on porting over some of the "Visitor" classes
from the earlier CDI branch (EJB and Web.xml visitors so far)
(jsightler, 14:21:29)
* I also added a non-classified file report that lists all Java and
XML files that were not classified or hinted by the report
(WINDUP-246) - though this is still pending review (jsightler,
14:22:03)
* Next, I will be working on the Spring configuration visitor
(jsightler, 14:22:20)
* Java legacy rules fully merged, however it looks like they caused
some test fails so currently working on it (mbriskar, 14:28:55)
* Xml legacy rules are in the PR, however some fixing needs to be
done. The PR has already 63 files changed, so I am a little bit
anxious about all the rebases I need to do, because they usually
break something (mbriskar, 14:30:07)
* LINK: http://keylines.com/graph-databases-data-visualization
(ozizka, 14:37:07)
* I've implemented ProgressMonitor support, as well as refactored the
decompiler-java into the java-rules, and updated the wiki with that
info (lincolnthree, 14:38:17)
* I've done a number of PR reviews (lincolnthree, 14:38:42)
* I'll be continuing to work on usability improvements, refactoring,
and reviews (lincolnthree, 14:39:10)
* LINK:
https://plus.google.com/hangouts/_/g4fe2nul4hfnzyqbvslm7ilxbma?authuser=0&hl=en
(lincolnthree, 14:40:00)
* Next Jira triage? (lincolnthree, 14:41:08)
* Jira triage at Thursday 10 AM EST (ozizka, 14:48:00)
* Big picture overview - and where do we stand with it (lincolnthree,
14:48:04)
* A docs on What rules we have, What Models we have, and how do they
interact. (ozizka, 14:50:23)
* LINK: https://github.com/windup/windup/wiki/Rules:-Tutorial
(ozizka, 14:55:17)
* How / where to put the rules - into users' github repo, then a pull
request? Or...? (lincolnthree, 14:58:10)
* If it's user's custom ruleset, then they would put it to their
github. If they want to constribute (AKA let us maintain), then we
will have a special repo for such rulesets in the future. (ozizka,
15:03:05)
* For now, just send us a PR with any new rulesets. (ozizka,
15:07:01)
* Negative queries - WINDUP-164 (lincolnthree, 15:07:51)
* Other ways to estimate effort (other than story points) - Perhaps
create some guide on quantifiyng the effort with story points? E.g.
copy&paste versus a debugging session, Spring beans porting, ...
(ozizka, 15:08:39)
* rules schema (ozizka, 15:12:00)
* The need for rules schema will be dicussed on Thu before the Jira
triage. (ozizka, 15:14:59)
Meeting ended at 15:16:18 UTC.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/60093b91/attachment.html
From lincolnbaxter at gmail.com Wed Sep 3 11:25:00 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 3 Sep 2014 11:25:00 -0400
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <5406FCDD.8000600@redhat.com>
References: <54067F4A.3050200@redhat.com>
<5406FCDD.8000600@redhat.com>
Message-ID: <CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
Speaking of Formatting, it would be nice if the Wiki pages were written in
Asciidoc instead of Markdown. It doesn't *really* matter, but it kind of
matters because Asciidoc interops with Docbook well.
On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com> wrote:
> Hi Ondra,
>
> Should we replace the colons in the page titles with '_' or something
> else to make it easier? For example 'Foo_BarI don't mind doing that and
> it shouldn't take too long.
>
> Thanks,
> Sande
>
> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
> > Hi all,
> >
> > to save you some time figuring it out:
> > GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
> > like this:
> >
> > A) [blah](Foo%3A-Bar)
> > B) [blah](./Foo:-Bar)
> > C) [blah](./Foo: Bar)
> > D) If all fails - full URL.
> >
> > HTH,
> > Ondra
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/4bd4a3f8/attachment-0001.html
From lincolnbaxter at gmail.com Wed Sep 3 11:26:35 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 3 Sep 2014 11:26:35 -0400
Subject: [windup-dev] Status update - Decompiler - WINDUP-235
In-Reply-To: <540686E1.80301@redhat.com>
References: <540686E1.80301@redhat.com>
Message-ID: <CAEp_U4F8ZYJeGsNTiv2j2rcY+S+N+Nd=UGFEq6LVWO-c58BUZQ@mail.gmail.com>
I'm not convinced that decompiling a single class would be slow without
seeing evidence. Filters is an interesting alternative (and could be used
to implement single file decompilation), is it possible for you to contact
the author of Procyon and ask how to do this (single class decompilation)?
On Tue, Sep 2, 2014 at 11:11 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Hi,
>
> update on WINDUP-235:
>
> Procyon's API is a bit low-level.
> There's a package procyon-decompilertools, whose API is a bit weird and
> tangled, and of course, without a bit of javadoc.
> That package worked for .jar decompilation since that's the use case for
> that package. Decompiling .class is not.
> Procyon Wiki says it should be able to decompile a .class file, but it
> is not - an ITypeLoader impl to get it from a filesystem is missing.
>
> More, I think picking up from the .jar one by one would be slow.
> I'm going to implement it so it would decompile files as accepted by a
> filter, in one pass over given .jar.
>
> Another approach is to move this to higher level, and when asked to
> decompile "all classes in org.mycompany.*", query the graph for where
> they are, and then decompile all classes from those jars, again, using a
> filter.
> Still, querying for all classes would be slow. So I suggest to store an
> information about what jar contains which packages in the graph (if we
> don't yet), WDYT?
>
> And lastly - one idea - not sure how much time Windup spends on
> comparing package prefixes, but we could build a package tree in the
> graph when scanning, and when looking for classes from given package
> org.foo.*, we could select with Gremlin:
> PackageModel[name=org] -- contains --> PackageModel[name=foo] --
> contains --> JavaClassModel .loop()
> That could be faster when the numbers of classes in the projects get to
> hundreds of thousands.
>
> Ondra
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/2d3dbeb3/attachment.html
From pmuir at redhat.com Wed Sep 3 11:33:01 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 3 Sep 2014 16:33:01 +0100
Subject: [windup-dev] Status update - Decompiler - WINDUP-235
In-Reply-To: <CAEp_U4F8ZYJeGsNTiv2j2rcY+S+N+Nd=UGFEq6LVWO-c58BUZQ@mail.gmail.com>
References: <540686E1.80301@redhat.com>
<CAEp_U4F8ZYJeGsNTiv2j2rcY+S+N+Nd=UGFEq6LVWO-c58BUZQ@mail.gmail.com>
Message-ID: <1063EA20-FE96-416F-9716-7F5BFBF34384@redhat.com>
Isn?t the point that picking up classes one by one from a compressed jar slow, because the jar is represented as a stream, and doesn?t support random access?
On 3 Sep 2014, at 16:26, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
> I'm not convinced that decompiling a single class would be slow without seeing evidence. Filters is an interesting alternative (and could be used to implement single file decompilation), is it possible for you to contact the author of Procyon and ask how to do this (single class decompilation)?
>
>
> On Tue, Sep 2, 2014 at 11:11 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Hi,
>
> update on WINDUP-235:
>
> Procyon's API is a bit low-level.
> There's a package procyon-decompilertools, whose API is a bit weird and
> tangled, and of course, without a bit of javadoc.
> That package worked for .jar decompilation since that's the use case for
> that package. Decompiling .class is not.
> Procyon Wiki says it should be able to decompile a .class file, but it
> is not - an ITypeLoader impl to get it from a filesystem is missing.
>
> More, I think picking up from the .jar one by one would be slow.
> I'm going to implement it so it would decompile files as accepted by a
> filter, in one pass over given .jar.
>
> Another approach is to move this to higher level, and when asked to
> decompile "all classes in org.mycompany.*", query the graph for where
> they are, and then decompile all classes from those jars, again, using a
> filter.
> Still, querying for all classes would be slow. So I suggest to store an
> information about what jar contains which packages in the graph (if we
> don't yet), WDYT?
>
> And lastly - one idea - not sure how much time Windup spends on
> comparing package prefixes, but we could build a package tree in the
> graph when scanning, and when looking for classes from given package
> org.foo.*, we could select with Gremlin:
> PackageModel[name=org] -- contains --> PackageModel[name=foo] --
> contains --> JavaClassModel .loop()
> That could be faster when the numbers of classes in the projects get to
> hundreds of thousands.
>
> Ondra
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From sgilda at redhat.com Wed Sep 3 11:41:53 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 03 Sep 2014 11:41:53 -0400
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
References: <54067F4A.3050200@redhat.com> <5406FCDD.8000600@redhat.com>
<CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
Message-ID: <540736C1.4020602@redhat.com>
Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc
converter utility? ;-)
I need to get up to speed with Asciidoc so I can convert the pages.
On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
> Speaking of Formatting, it would be nice if the Wiki pages were
> written in Asciidoc instead of Markdown. It doesn't *really* matter,
> but it kind of matters because Asciidoc interops with Docbook well.
>
>
> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com
> <mailto:sgilda at redhat.com>> wrote:
>
> Hi Ondra,
>
> Should we replace the colons in the page titles with '_' or something
> else to make it easier? For example 'Foo_BarI don't mind doing
> that and
> it shouldn't take too long.
>
> Thanks,
> Sande
>
> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
> > Hi all,
> >
> > to save you some time figuring it out:
> > GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may
> look
> > like this:
> >
> > A) [blah](Foo%3A-Bar)
> > B) [blah](./Foo:-Bar)
> > C) [blah](./Foo: Bar)
> > D) If all fails - full URL.
> >
> > HTH,
> > Ondra
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/96891f96/attachment.html
From ozizka at redhat.com Wed Sep 3 11:42:48 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 03 Sep 2014 17:42:48 +0200
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
References: <54067F4A.3050200@redhat.com> <5406FCDD.8000600@redhat.com>
<CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
Message-ID: <540736F8.303@redhat.com>
Right, Sande suggested that too.
When do you think we could switch? Probably after first GA release?
Ondra
On 3.9.2014 17:25, Lincoln Baxter, III wrote:
> Speaking of Formatting, it would be nice if the Wiki pages were
> written in Asciidoc instead of Markdown. It doesn't *really* matter,
> but it kind of matters because Asciidoc interops with Docbook well.
>
>
> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com
> <mailto:sgilda at redhat.com>> wrote:
>
> Hi Ondra,
>
> Should we replace the colons in the page titles with '_' or something
> else to make it easier? For example 'Foo_BarI don't mind doing
> that and
> it shouldn't take too long.
>
> Thanks,
> Sande
>
> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
> > Hi all,
> >
> > to save you some time figuring it out:
> > GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may
> look
> > like this:
> >
> > A) [blah](Foo%3A-Bar)
> > B) [blah](./Foo:-Bar)
> > C) [blah](./Foo: Bar)
> > D) If all fails - full URL.
> >
> > HTH,
> > Ondra
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/aab3649e/attachment.html
From pmuir at redhat.com Wed Sep 3 11:45:53 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 3 Sep 2014 16:45:53 +0100
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <540736C1.4020602@redhat.com>
References: <54067F4A.3050200@redhat.com> <5406FCDD.8000600@redhat.com>
<CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
<540736C1.4020602@redhat.com>
Message-ID: <075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com>
You can just do mv my.md my.adoc
Asciidoc can read all the standard asciidoc syntax afaik.
On 3 Sep 2014, at 16:41, Sande Gilda <sgilda at redhat.com> wrote:
> Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc converter utility? ;-)
>
> I need to get up to speed with Asciidoc so I can convert the pages.
>
> On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
>> Speaking of Formatting, it would be nice if the Wiki pages were written in Asciidoc instead of Markdown. It doesn't *really* matter, but it kind of matters because Asciidoc interops with Docbook well.
>>
>>
>> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com> wrote:
>> Hi Ondra,
>>
>> Should we replace the colons in the page titles with '_' or something
>> else to make it easier? For example 'Foo_BarI don't mind doing that and
>> it shouldn't take too long.
>>
>> Thanks,
>> Sande
>>
>> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
>> > Hi all,
>> >
>> > to save you some time figuring it out:
>> > GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
>> > like this:
>> >
>> > A) [blah](Foo%3A-Bar)
>> > B) [blah](./Foo:-Bar)
>> > C) [blah](./Foo: Bar)
>> > D) If all fails - full URL.
>> >
>> > HTH,
>> > Ondra
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>>
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Wed Sep 3 11:47:55 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 03 Sep 2014 17:47:55 +0200
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <540736F8.303@redhat.com>
References: <54067F4A.3050200@redhat.com> <5406FCDD.8000600@redhat.com>
<CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
<540736F8.303@redhat.com>
Message-ID: <5407382B.1050602@redhat.com>
Alternatively, Markdown can possibly be converted to DocBook:
http://johnmacfarlane.net/pandoc/
Ondra
On 3.9.2014 17:42, Ondrej Zizka wrote:
> Right, Sande suggested that too.
> When do you think we could switch? Probably after first GA release?
>
> Ondra
>
>
> On 3.9.2014 17:25, Lincoln Baxter, III wrote:
>> Speaking of Formatting, it would be nice if the Wiki pages were
>> written in Asciidoc instead of Markdown. It doesn't *really* matter,
>> but it kind of matters because Asciidoc interops with Docbook well.
>>
>>
>> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com
>> <mailto:sgilda at redhat.com>> wrote:
>>
>> Hi Ondra,
>>
>> Should we replace the colons in the page titles with '_' or something
>> else to make it easier? For example 'Foo_BarI don't mind doing
>> that and
>> it shouldn't take too long.
>>
>> Thanks,
>> Sande
>>
>> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
>> > Hi all,
>> >
>> > to save you some time figuring it out:
>> > GitHub wiki doesn't like : in links, so a link to "Foo: Bar"
>> may look
>> > like this:
>> >
>> > A) [blah](Foo%3A-Bar)
>> > B) [blah](./Foo:-Bar)
>> > C) [blah](./Foo: Bar)
>> > D) If all fails - full URL.
>> >
>> > HTH,
>> > Ondra
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/eaede227/attachment-0001.html
From lincolnbaxter at gmail.com Wed Sep 3 12:58:12 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 3 Sep 2014 12:58:12 -0400
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com>
References: <54067F4A.3050200@redhat.com> <5406FCDD.8000600@redhat.com>
<CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
<540736C1.4020602@redhat.com>
<075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com>
Message-ID: <CAEp_U4GAf9UZxM=TUnYM4xZEKa7q-PDW+mBaVJbqtA=pdr6TUw@mail.gmail.com>
Asciidoc can read all the standard Markdown syntax? Interesting. Figures :)
On Wed, Sep 3, 2014 at 11:45 AM, Pete Muir <pmuir at redhat.com> wrote:
> You can just do mv my.md my.adoc
>
> Asciidoc can read all the standard asciidoc syntax afaik.
>
> On 3 Sep 2014, at 16:41, Sande Gilda <sgilda at redhat.com> wrote:
>
> > Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc
> converter utility? ;-)
> >
> > I need to get up to speed with Asciidoc so I can convert the pages.
> >
> > On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
> >> Speaking of Formatting, it would be nice if the Wiki pages were written
> in Asciidoc instead of Markdown. It doesn't *really* matter, but it kind of
> matters because Asciidoc interops with Docbook well.
> >>
> >>
> >> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com> wrote:
> >> Hi Ondra,
> >>
> >> Should we replace the colons in the page titles with '_' or something
> >> else to make it easier? For example 'Foo_BarI don't mind doing that and
> >> it shouldn't take too long.
> >>
> >> Thanks,
> >> Sande
> >>
> >> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
> >> > Hi all,
> >> >
> >> > to save you some time figuring it out:
> >> > GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
> >> > like this:
> >> >
> >> > A) [blah](Foo%3A-Bar)
> >> > B) [blah](./Foo:-Bar)
> >> > C) [blah](./Foo: Bar)
> >> > D) If all fails - full URL.
> >> >
> >> > HTH,
> >> > Ondra
> >>
> >> _______________________________________________
> >> windup-dev mailing list
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> >>
> >>
> >>
> >> --
> >> Lincoln Baxter, III
> >> http://ocpsoft.org
> >> "Simpler is better."
> >>
> >>
> >> _______________________________________________
> >> windup-dev mailing list
> >>
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> >
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/35134a06/attachment.html
From lincolnbaxter at gmail.com Wed Sep 3 12:58:32 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 3 Sep 2014 12:58:32 -0400
Subject: [windup-dev] Status update - Decompiler - WINDUP-235
In-Reply-To: <1063EA20-FE96-416F-9716-7F5BFBF34384@redhat.com>
References: <540686E1.80301@redhat.com>
<CAEp_U4F8ZYJeGsNTiv2j2rcY+S+N+Nd=UGFEq6LVWO-c58BUZQ@mail.gmail.com>
<1063EA20-FE96-416F-9716-7F5BFBF34384@redhat.com>
Message-ID: <CAEp_U4GxA1sYJKurdKMw+ZPpw5B-GkkYWghW+AmGtbQ0c0=1kg@mail.gmail.com>
we unzip everything to start with, anyway.
On Wed, Sep 3, 2014 at 11:33 AM, Pete Muir <pmuir at redhat.com> wrote:
> Isn?t the point that picking up classes one by one from a compressed jar
> slow, because the jar is represented as a stream, and doesn?t support
> random access?
>
> On 3 Sep 2014, at 16:26, Lincoln Baxter, III <lincolnbaxter at gmail.com>
> wrote:
>
> > I'm not convinced that decompiling a single class would be slow without
> seeing evidence. Filters is an interesting alternative (and could be used
> to implement single file decompilation), is it possible for you to contact
> the author of Procyon and ask how to do this (single class decompilation)?
> >
> >
> > On Tue, Sep 2, 2014 at 11:11 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> > Hi,
> >
> > update on WINDUP-235:
> >
> > Procyon's API is a bit low-level.
> > There's a package procyon-decompilertools, whose API is a bit weird and
> > tangled, and of course, without a bit of javadoc.
> > That package worked for .jar decompilation since that's the use case for
> > that package. Decompiling .class is not.
> > Procyon Wiki says it should be able to decompile a .class file, but it
> > is not - an ITypeLoader impl to get it from a filesystem is missing.
> >
> > More, I think picking up from the .jar one by one would be slow.
> > I'm going to implement it so it would decompile files as accepted by a
> > filter, in one pass over given .jar.
> >
> > Another approach is to move this to higher level, and when asked to
> > decompile "all classes in org.mycompany.*", query the graph for where
> > they are, and then decompile all classes from those jars, again, using a
> > filter.
> > Still, querying for all classes would be slow. So I suggest to store an
> > information about what jar contains which packages in the graph (if we
> > don't yet), WDYT?
> >
> > And lastly - one idea - not sure how much time Windup spends on
> > comparing package prefixes, but we could build a package tree in the
> > graph when scanning, and when looking for classes from given package
> > org.foo.*, we could select with Gremlin:
> > PackageModel[name=org] -- contains --> PackageModel[name=foo] --
> > contains --> JavaClassModel .loop()
> > That could be faster when the numbers of classes in the projects get to
> > hundreds of thousands.
> >
> > Ondra
> >
> >
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
> >
> >
> >
> > --
> > Lincoln Baxter, III
> > http://ocpsoft.org
> > "Simpler is better."
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/f25bb760/attachment.html
From lincolnbaxter at gmail.com Wed Sep 3 12:59:24 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 3 Sep 2014 12:59:24 -0400
Subject: [windup-dev] Status update - Decompiler - WINDUP-235
In-Reply-To: <CAEp_U4GxA1sYJKurdKMw+ZPpw5B-GkkYWghW+AmGtbQ0c0=1kg@mail.gmail.com>
References: <540686E1.80301@redhat.com>
<CAEp_U4F8ZYJeGsNTiv2j2rcY+S+N+Nd=UGFEq6LVWO-c58BUZQ@mail.gmail.com>
<1063EA20-FE96-416F-9716-7F5BFBF34384@redhat.com>
<CAEp_U4GxA1sYJKurdKMw+ZPpw5B-GkkYWghW+AmGtbQ0c0=1kg@mail.gmail.com>
Message-ID: <CAEp_U4FFvF7csuhJJdAnqzEzE6VBnC=3_ryFdyiOopbKHJs5ew@mail.gmail.com>
See line 21: http://paste2.org/d9Wyydfc
On Wed, Sep 3, 2014 at 12:58 PM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:
> we unzip everything to start with, anyway.
>
>
> On Wed, Sep 3, 2014 at 11:33 AM, Pete Muir <pmuir at redhat.com> wrote:
>
>> Isn?t the point that picking up classes one by one from a compressed jar
>> slow, because the jar is represented as a stream, and doesn?t support
>> random access?
>>
>> On 3 Sep 2014, at 16:26, Lincoln Baxter, III <lincolnbaxter at gmail.com>
>> wrote:
>>
>> > I'm not convinced that decompiling a single class would be slow without
>> seeing evidence. Filters is an interesting alternative (and could be used
>> to implement single file decompilation), is it possible for you to contact
>> the author of Procyon and ask how to do this (single class decompilation)?
>> >
>> >
>> > On Tue, Sep 2, 2014 at 11:11 PM, Ondrej Zizka <ozizka at redhat.com>
>> wrote:
>> > Hi,
>> >
>> > update on WINDUP-235:
>> >
>> > Procyon's API is a bit low-level.
>> > There's a package procyon-decompilertools, whose API is a bit weird and
>> > tangled, and of course, without a bit of javadoc.
>> > That package worked for .jar decompilation since that's the use case for
>> > that package. Decompiling .class is not.
>> > Procyon Wiki says it should be able to decompile a .class file, but it
>> > is not - an ITypeLoader impl to get it from a filesystem is missing.
>> >
>> > More, I think picking up from the .jar one by one would be slow.
>> > I'm going to implement it so it would decompile files as accepted by a
>> > filter, in one pass over given .jar.
>> >
>> > Another approach is to move this to higher level, and when asked to
>> > decompile "all classes in org.mycompany.*", query the graph for where
>> > they are, and then decompile all classes from those jars, again, using a
>> > filter.
>> > Still, querying for all classes would be slow. So I suggest to store an
>> > information about what jar contains which packages in the graph (if we
>> > don't yet), WDYT?
>> >
>> > And lastly - one idea - not sure how much time Windup spends on
>> > comparing package prefixes, but we could build a package tree in the
>> > graph when scanning, and when looking for classes from given package
>> > org.foo.*, we could select with Gremlin:
>> > PackageModel[name=org] -- contains --> PackageModel[name=foo] --
>> > contains --> JavaClassModel .loop()
>> > That could be faster when the numbers of classes in the projects get to
>> > hundreds of thousands.
>> >
>> > Ondra
>> >
>> >
>> > _______________________________________________
>> > windup-dev mailing list
>> > windup-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/windup-dev
>> >
>> >
>> >
>> > --
>> > Lincoln Baxter, III
>> > http://ocpsoft.org
>> > "Simpler is better."
>> > _______________________________________________
>> > windup-dev mailing list
>> > windup-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140903/67b06066/attachment.html
From pmuir at redhat.com Wed Sep 3 13:04:30 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 3 Sep 2014 18:04:30 +0100
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <CAEp_U4GAf9UZxM=TUnYM4xZEKa7q-PDW+mBaVJbqtA=pdr6TUw@mail.gmail.com>
References: <54067F4A.3050200@redhat.com> <5406FCDD.8000600@redhat.com>
<CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
<540736C1.4020602@redhat.com>
<075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com>
<CAEp_U4GAf9UZxM=TUnYM4xZEKa7q-PDW+mBaVJbqtA=pdr6TUw@mail.gmail.com>
Message-ID: <9072C0F6-D827-4A87-A240-B7776D5244BF@redhat.com>
Yes, some of it is not the advised syntax for asciidoc, but it does work iirc (actually now i?m not sure if mark-down links work?)
On 3 Sep 2014, at 17:58, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
> Asciidoc can read all the standard Markdown syntax? Interesting. Figures :)
>
>
> On Wed, Sep 3, 2014 at 11:45 AM, Pete Muir <pmuir at redhat.com> wrote:
> You can just do mv my.md my.adoc
>
> Asciidoc can read all the standard asciidoc syntax afaik.
>
> On 3 Sep 2014, at 16:41, Sande Gilda <sgilda at redhat.com> wrote:
>
> > Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc converter utility? ;-)
> >
> > I need to get up to speed with Asciidoc so I can convert the pages.
> >
> > On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
> >> Speaking of Formatting, it would be nice if the Wiki pages were written in Asciidoc instead of Markdown. It doesn't *really* matter, but it kind of matters because Asciidoc interops with Docbook well.
> >>
> >>
> >> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com> wrote:
> >> Hi Ondra,
> >>
> >> Should we replace the colons in the page titles with '_' or something
> >> else to make it easier? For example 'Foo_BarI don't mind doing that and
> >> it shouldn't take too long.
> >>
> >> Thanks,
> >> Sande
> >>
> >> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
> >> > Hi all,
> >> >
> >> > to save you some time figuring it out:
> >> > GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
> >> > like this:
> >> >
> >> > A) [blah](Foo%3A-Bar)
> >> > B) [blah](./Foo:-Bar)
> >> > C) [blah](./Foo: Bar)
> >> > D) If all fails - full URL.
> >> >
> >> > HTH,
> >> > Ondra
> >>
> >> _______________________________________________
> >> windup-dev mailing list
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> >>
> >>
> >>
> >> --
> >> Lincoln Baxter, III
> >> http://ocpsoft.org
> >> "Simpler is better."
> >>
> >>
> >> _______________________________________________
> >> windup-dev mailing list
> >>
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> >
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From pmuir at redhat.com Wed Sep 3 13:04:47 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 3 Sep 2014 18:04:47 +0100
Subject: [windup-dev] Status update - Decompiler - WINDUP-235
In-Reply-To: <CAEp_U4FFvF7csuhJJdAnqzEzE6VBnC=3_ryFdyiOopbKHJs5ew@mail.gmail.com>
References: <540686E1.80301@redhat.com>
<CAEp_U4F8ZYJeGsNTiv2j2rcY+S+N+Nd=UGFEq6LVWO-c58BUZQ@mail.gmail.com>
<1063EA20-FE96-416F-9716-7F5BFBF34384@redhat.com>
<CAEp_U4GxA1sYJKurdKMw+ZPpw5B-GkkYWghW+AmGtbQ0c0=1kg@mail.gmail.com>
<CAEp_U4FFvF7csuhJJdAnqzEzE6VBnC=3_ryFdyiOopbKHJs5ew@mail.gmail.com>
Message-ID: <BDEC9B5A-E71F-441B-B132-AA8C07844194@redhat.com>
Well in that case?
On 3 Sep 2014, at 17:59, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
> See line 21: http://paste2.org/d9Wyydfc
>
>
> On Wed, Sep 3, 2014 at 12:58 PM, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
> we unzip everything to start with, anyway.
>
>
> On Wed, Sep 3, 2014 at 11:33 AM, Pete Muir <pmuir at redhat.com> wrote:
> Isn?t the point that picking up classes one by one from a compressed jar slow, because the jar is represented as a stream, and doesn?t support random access?
>
> On 3 Sep 2014, at 16:26, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
>
> > I'm not convinced that decompiling a single class would be slow without seeing evidence. Filters is an interesting alternative (and could be used to implement single file decompilation), is it possible for you to contact the author of Procyon and ask how to do this (single class decompilation)?
> >
> >
> > On Tue, Sep 2, 2014 at 11:11 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> > Hi,
> >
> > update on WINDUP-235:
> >
> > Procyon's API is a bit low-level.
> > There's a package procyon-decompilertools, whose API is a bit weird and
> > tangled, and of course, without a bit of javadoc.
> > That package worked for .jar decompilation since that's the use case for
> > that package. Decompiling .class is not.
> > Procyon Wiki says it should be able to decompile a .class file, but it
> > is not - an ITypeLoader impl to get it from a filesystem is missing.
> >
> > More, I think picking up from the .jar one by one would be slow.
> > I'm going to implement it so it would decompile files as accepted by a
> > filter, in one pass over given .jar.
> >
> > Another approach is to move this to higher level, and when asked to
> > decompile "all classes in org.mycompany.*", query the graph for where
> > they are, and then decompile all classes from those jars, again, using a
> > filter.
> > Still, querying for all classes would be slow. So I suggest to store an
> > information about what jar contains which packages in the graph (if we
> > don't yet), WDYT?
> >
> > And lastly - one idea - not sure how much time Windup spends on
> > comparing package prefixes, but we could build a package tree in the
> > graph when scanning, and when looking for classes from given package
> > org.foo.*, we could select with Gremlin:
> > PackageModel[name=org] -- contains --> PackageModel[name=foo] --
> > contains --> JavaClassModel .loop()
> > That could be faster when the numbers of classes in the projects get to
> > hundreds of thousands.
> >
> > Ondra
> >
> >
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
> >
> >
> >
> > --
> > Lincoln Baxter, III
> > http://ocpsoft.org
> > "Simpler is better."
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From sgilda at redhat.com Wed Sep 3 14:08:33 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 03 Sep 2014 14:08:33 -0400
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <9072C0F6-D827-4A87-A240-B7776D5244BF@redhat.com>
References: <54067F4A.3050200@redhat.com>
<5406FCDD.8000600@redhat.com> <CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com> <540736C1.4020602@redhat.com> <075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com> <CAEp_U4GAf9UZxM=TUnYM4xZEKa7q-PDW+mBaVJbqtA=pdr6TUw@mail.gmail.com>
<9072C0F6-D827-4A87-A240-B7776D5244BF@redhat.com>
Message-ID: <54075921.6030009@redhat.com>
Thanks Pete! This sounds like the easiest approach. I'll make the
changes in my own repo first and try to fix all the nuances first.
On 09/03/2014 01:04 PM, Pete Muir wrote:
> Yes, some of it is not the advised syntax for asciidoc, but it does work iirc (actually now i?m not sure if mark-down links work?)
>
> On 3 Sep 2014, at 17:58, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
>
>> Asciidoc can read all the standard Markdown syntax? Interesting. Figures :)
>>
>>
>> On Wed, Sep 3, 2014 at 11:45 AM, Pete Muir <pmuir at redhat.com> wrote:
>> You can just do mv my.md my.adoc
>>
>> Asciidoc can read all the standard asciidoc syntax afaik.
>>
>> On 3 Sep 2014, at 16:41, Sande Gilda <sgilda at redhat.com> wrote:
>>
>>> Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc converter utility? ;-)
>>>
>>> I need to get up to speed with Asciidoc so I can convert the pages.
>>>
>>> On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
>>>> Speaking of Formatting, it would be nice if the Wiki pages were written in Asciidoc instead of Markdown. It doesn't *really* matter, but it kind of matters because Asciidoc interops with Docbook well.
>>>>
>>>>
>>>> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com> wrote:
>>>> Hi Ondra,
>>>>
>>>> Should we replace the colons in the page titles with '_' or something
>>>> else to make it easier? For example 'Foo_BarI don't mind doing that and
>>>> it shouldn't take too long.
>>>>
>>>> Thanks,
>>>> Sande
>>>>
>>>> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
>>>>> Hi all,
>>>>>
>>>>> to save you some time figuring it out:
>>>>> GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
>>>>> like this:
>>>>>
>>>>> A) [blah](Foo%3A-Bar)
>>>>> B) [blah](./Foo:-Bar)
>>>>> C) [blah](./Foo: Bar)
>>>>> D) If all fails - full URL.
>>>>>
>>>>> HTH,
>>>>> Ondra
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>
>>>>
>>>>
>>>> --
>>>> Lincoln Baxter, III
>>>> http://ocpsoft.org
>>>> "Simpler is better."
>>>>
>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>>
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From bdavis at redhat.com Wed Sep 3 16:23:22 2014
From: bdavis at redhat.com (Brad Davis)
Date: Wed, 3 Sep 2014 16:23:22 -0400 (EDT)
Subject: [windup-dev] Status update - Decompiler - WINDUP-235
In-Reply-To: <CAEp_U4F8ZYJeGsNTiv2j2rcY+S+N+Nd=UGFEq6LVWO-c58BUZQ@mail.gmail.com>
References: <540686E1.80301@redhat.com>
<CAEp_U4F8ZYJeGsNTiv2j2rcY+S+N+Nd=UGFEq6LVWO-c58BUZQ@mail.gmail.com>
Message-ID: <1133380281.25961419.1409775802248.JavaMail.zimbra@redhat.com>
Just to clarify, decompiling is much more processor intensive than seeking a JAR file to load the bytes to decompile. So, I wouldn't worry about the cost of decompiling classes 1 by 1: that is definitely a lot lower cost than decompiling a full JAR.
Take the following scenario:
100 classes in a JAR
Only 10 classes actually have "interesting stuff"
You should really only have Windup decompiling the 10 classes that you need to inspect more closely. This was handled in Windup 1 by looking at the class imports (which are resolved anyway at compile time) and comparing them against the blacklist. In Windup 2, Lincoln builds a list of regular expressions that are "classes of interest". When you build your class graph, you should mark all classes of interest. Then, perform a graph query where you get all of the *scan package classes, and determine if they are related to any of the classes of interest. Only classes within the scan package that have relationships to classes of interest need to be decompiled, which should be a very small subset of the total number of classes in the application.
*scan package: you need to have 1 or more package structures that are provided at run time that says "hey, these are the classes that I actually can modify". In other words, if I develop an application that is deployed to Weblogic, I can only modify the code that I control. The scan package(s) represent all packages that I can control. This is important for a number of reasons, but most importantly: it probably is not legal or at least slippery slope to decompile another vendor's JEE classes. If you decompile everything, if the customer included weblogic.jar within their application, we should never be decompiling that. Secondly, the customer has no control over weblogic.jar, and can not modify its code anyway. The only code you should give hints on for modification is the customers code, since that is the only code they own/control. This is also extremely important because reporting on too much stuff (especially stuff that the customer can not control) is like fog which clouds their path to migrating their own code.
Brad Davis
Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Wednesday, September 3, 2014 11:26:35 AM
Subject: Re: [windup-dev] Status update - Decompiler - WINDUP-235
I'm not convinced that decompiling a single class would be slow without seeing evidence. Filters is an interesting alternative (and could be used to implement single file decompilation), is it possible for you to contact the author of Procyon and ask how to do this (single class decompilation)?
On Tue, Sep 2, 2014 at 11:11 PM, Ondrej Zizka < ozizka at redhat.com > wrote:
Hi,
update on WINDUP-235:
Procyon's API is a bit low-level.
There's a package procyon-decompilertools, whose API is a bit weird and
tangled, and of course, without a bit of javadoc.
That package worked for .jar decompilation since that's the use case for
that package. Decompiling .class is not.
Procyon Wiki says it should be able to decompile a .class file, but it
is not - an ITypeLoader impl to get it from a filesystem is missing.
More, I think picking up from the .jar one by one would be slow.
I'm going to implement it so it would decompile files as accepted by a
filter, in one pass over given .jar.
Another approach is to move this to higher level, and when asked to
decompile "all classes in org.mycompany.*", query the graph for where
they are, and then decompile all classes from those jars, again, using a
filter.
Still, querying for all classes would be slow. So I suggest to store an
information about what jar contains which packages in the graph (if we
don't yet), WDYT?
And lastly - one idea - not sure how much time Windup spends on
comparing package prefixes, but we could build a package tree in the
graph when scanning, and when looking for classes from given package
org.foo.*, we could select with Gremlin:
PackageModel[name=org] -- contains --> PackageModel[name=foo] --
contains --> JavaClassModel .loop()
That could be faster when the numbers of classes in the projects get to
hundreds of thousands.
Ondra
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Wed Sep 3 18:38:41 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 04 Sep 2014 00:38:41 +0200
Subject: [windup-dev] Bootstrapping in tests
Message-ID: <54079871.4000104@redhat.com>
Hi all,
I've hit a problem with bootstrapping.
The tests grab the parts of windup through CDI and that initializes them
with defaults.
For example, JavaClassTest#testIterationVariableResolving():
The context initializes at the first line.
When processor.execute() is called, the graph was somehow reused before,
but that's just because of different code in all the execute() methods.
I could simply not set the output dir to WindupProcessorConfig, but the
output is not just where graph is.
I could also check if the graph already has been initialized, but 1)
that would make it nonconfigurable, 2) it would be nonsystemic -
checking in init code if a part of application being initialized was, by
accident, initialized somewhere else.
My suggestion is that we should have kind of bootstrap API for the
graph, similar to WindupProcessor - with a config class, and initialize
it from that.
I don't know how to combine that with CDI, so the tests would have to
use that API instead of CDI.
That's something I have suggested before, and was rejected, perhaps I
didn't explain it clearly back then.
I can't think up any other solution that I would not consider overkill,
like, some CDI providers of the config.
Any suggestions?
Ondra
-------------------------------------------------------------------------------
Test set: org.jboss.windup.rules.java.JavaClassTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.678
sec <<< FAILURE! - in org.jboss.windup.rules.java.JavaClassTest
testIterationVariableResolving(org.jboss.windup.rules.java.JavaClassTest) Time
elapsed: 5.346 sec <<< ERROR!
org.jboss.windup.util.exception.WindupException_$$_javassist_9c4de665-baa6-4904-a4d3-37530e41e5a0:
Error, attempting to set graph directory to:
"/home/ondra/work/Migration/Windup/rules/app/java/target/windup_5ba22a23-c85f-49f3-b01c-39fda0eb1faa/graph",
but the graph has already been initialized (with graph folder:
"/home/ondra/work/Migration/Windup/rules/app/java/target/windupgraph_1cfccd03-8f33-43a4-a305-99fdd38bc172"!
To change this, you must first disconnect from the graph!
at
org.jboss.windup.graph.GraphContextImpl.setGraphDirectory(GraphContextImpl.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:38)
at
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
at
org.jboss.weld.proxies.GraphContext$2110577583$Proxy$_$$_WeldClientProxy.setGraphDirectory(Unknown
Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at
org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at
org.jboss.windup.graph.GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.setGraphDirectory(GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.java)
at
org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at
org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at
org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.execute(WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.java)
at
org.jboss.windup.rules.java.JavaClassTest.testIterationVariableResolving(JavaClassTest.java:118)
From sgilda at redhat.com Wed Sep 3 19:58:26 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 03 Sep 2014 19:58:26 -0400
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <9072C0F6-D827-4A87-A240-B7776D5244BF@redhat.com>
References: <54067F4A.3050200@redhat.com>
<5406FCDD.8000600@redhat.com> <CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com> <540736C1.4020602@redhat.com> <075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com> <CAEp_U4GAf9UZxM=TUnYM4xZEKa7q-PDW+mBaVJbqtA=pdr6TUw@mail.gmail.com>
<9072C0F6-D827-4A87-A240-B7776D5244BF@redhat.com>
Message-ID: <5407AB22.1090009@redhat.com>
The Windup Wiki pages are now converted to Asciidoc. I tried using the
'mv' command, but it didn't seem to convert the source correctly, so I
used Pandoc to convert the pages locally and pasted the results into the
Wiki pages. All the pages have now been converted except
'Dev:-Decompile' because Ondra was editing that one. I still need to go
through them and clean up any additional conversion issues and fix
broken links. Let me know if you see any problems.
On 09/03/2014 01:04 PM, Pete Muir wrote:
> Yes, some of it is not the advised syntax for asciidoc, but it does work iirc (actually now i?m not sure if mark-down links work?)
>
> On 3 Sep 2014, at 17:58, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
>
>> Asciidoc can read all the standard Markdown syntax? Interesting. Figures :)
>>
>>
>> On Wed, Sep 3, 2014 at 11:45 AM, Pete Muir <pmuir at redhat.com> wrote:
>> You can just do mv my.md my.adoc
>>
>> Asciidoc can read all the standard asciidoc syntax afaik.
>>
>> On 3 Sep 2014, at 16:41, Sande Gilda <sgilda at redhat.com> wrote:
>>
>>> Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc converter utility? ;-)
>>>
>>> I need to get up to speed with Asciidoc so I can convert the pages.
>>>
>>> On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
>>>> Speaking of Formatting, it would be nice if the Wiki pages were written in Asciidoc instead of Markdown. It doesn't *really* matter, but it kind of matters because Asciidoc interops with Docbook well.
>>>>
>>>>
>>>> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com> wrote:
>>>> Hi Ondra,
>>>>
>>>> Should we replace the colons in the page titles with '_' or something
>>>> else to make it easier? For example 'Foo_BarI don't mind doing that and
>>>> it shouldn't take too long.
>>>>
>>>> Thanks,
>>>> Sande
>>>>
>>>> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
>>>>> Hi all,
>>>>>
>>>>> to save you some time figuring it out:
>>>>> GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
>>>>> like this:
>>>>>
>>>>> A) [blah](Foo%3A-Bar)
>>>>> B) [blah](./Foo:-Bar)
>>>>> C) [blah](./Foo: Bar)
>>>>> D) If all fails - full URL.
>>>>>
>>>>> HTH,
>>>>> Ondra
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>
>>>>
>>>>
>>>> --
>>>> Lincoln Baxter, III
>>>> http://ocpsoft.org
>>>> "Simpler is better."
>>>>
>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>>
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From sgilda at redhat.com Wed Sep 3 20:09:35 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 3 Sep 2014 20:09:35 -0400 (EDT)
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <5407AB22.1090009@redhat.com>
References: <54067F4A.3050200@redhat.com> <5406FCDD.8000600@redhat.com>
<CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
<540736C1.4020602@redhat.com>
<075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com>
<CAEp_U4GAf9UZxM=TUnYM4xZEKa7q-PDW+mBaVJbqtA=pdr6TUw@mail.gmail.com>
<9072C0F6-D827-4A87-A240-B7776D5244BF@redhat.com>
<5407AB22.1090009@redhat.com>
Message-ID: <765465901.16343766.1409789375770.JavaMail.zimbra@redhat.com>
Also, is there a way to make the Wiki 'New Page' button default to a file type of Asciidoc instead of Markdown?
----- Original Message -----
> From: "Sande Gilda" <sgilda at redhat.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Wednesday, September 3, 2014 7:58:26 PM
> Subject: Re: [windup-dev] Wiki links trick for colon
>
> The Windup Wiki pages are now converted to Asciidoc. I tried using the
> 'mv' command, but it didn't seem to convert the source correctly, so I
> used Pandoc to convert the pages locally and pasted the results into the
> Wiki pages. All the pages have now been converted except
> 'Dev:-Decompile' because Ondra was editing that one. I still need to go
> through them and clean up any additional conversion issues and fix
> broken links. Let me know if you see any problems.
>
> On 09/03/2014 01:04 PM, Pete Muir wrote:
> > Yes, some of it is not the advised syntax for asciidoc, but it does work
> > iirc (actually now i?m not sure if mark-down links work?)
> >
> > On 3 Sep 2014, at 17:58, Lincoln Baxter, III <lincolnbaxter at gmail.com>
> > wrote:
> >
> >> Asciidoc can read all the standard Markdown syntax? Interesting. Figures
> >> :)
> >>
> >>
> >> On Wed, Sep 3, 2014 at 11:45 AM, Pete Muir <pmuir at redhat.com> wrote:
> >> You can just do mv my.md my.adoc
> >>
> >> Asciidoc can read all the standard asciidoc syntax afaik.
> >>
> >> On 3 Sep 2014, at 16:41, Sande Gilda <sgilda at redhat.com> wrote:
> >>
> >>> Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc
> >>> converter utility? ;-)
> >>>
> >>> I need to get up to speed with Asciidoc so I can convert the pages.
> >>>
> >>> On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
> >>>> Speaking of Formatting, it would be nice if the Wiki pages were written
> >>>> in Asciidoc instead of Markdown. It doesn't *really* matter, but it
> >>>> kind of matters because Asciidoc interops with Docbook well.
> >>>>
> >>>>
> >>>> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com> wrote:
> >>>> Hi Ondra,
> >>>>
> >>>> Should we replace the colons in the page titles with '_' or something
> >>>> else to make it easier? For example 'Foo_BarI don't mind doing that and
> >>>> it shouldn't take too long.
> >>>>
> >>>> Thanks,
> >>>> Sande
> >>>>
> >>>> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
> >>>>> Hi all,
> >>>>>
> >>>>> to save you some time figuring it out:
> >>>>> GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
> >>>>> like this:
> >>>>>
> >>>>> A) [blah](Foo%3A-Bar)
> >>>>> B) [blah](./Foo:-Bar)
> >>>>> C) [blah](./Foo: Bar)
> >>>>> D) If all fails - full URL.
> >>>>>
> >>>>> HTH,
> >>>>> Ondra
> >>>> _______________________________________________
> >>>> windup-dev mailing list
> >>>> windup-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/windup-dev
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Lincoln Baxter, III
> >>>> http://ocpsoft.org
> >>>> "Simpler is better."
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> windup-dev mailing list
> >>>>
> >>>> windup-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/windup-dev
> >>> _______________________________________________
> >>> windup-dev mailing list
> >>> windup-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/windup-dev
> >>
> >> _______________________________________________
> >> windup-dev mailing list
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> >>
> >>
> >>
> >> --
> >> Lincoln Baxter, III
> >> http://ocpsoft.org
> >> "Simpler is better."
> >> _______________________________________________
> >> windup-dev mailing list
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> >
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
From pmuir at redhat.com Thu Sep 4 04:31:54 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 4 Sep 2014 09:31:54 +0100
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <765465901.16343766.1409789375770.JavaMail.zimbra@redhat.com>
References: <54067F4A.3050200@redhat.com> <5406FCDD.8000600@redhat.com>
<CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com>
<540736C1.4020602@redhat.com>
<075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com>
<CAEp_U4GAf9UZxM=TUnYM4xZEKa7q-PDW+mBaVJbqtA=pdr6TUw@mail.gmail.com>
<9072C0F6-D827-4A87-A240-B7776D5244BF@redhat.com>
<5407AB22.1090009@redhat.com>
<765465901.16343766.1409789375770.JavaMail.zimbra@redhat.com>
Message-ID: <A5C22CA8-F3A4-4709-80C1-9D9D22013DDF@redhat.com>
I can?t see one https://help.github.com/articles/adding-wiki-pages-via-the-online-interface
On 4 Sep 2014, at 01:09, Sande Gilda <sgilda at redhat.com> wrote:
>
> Also, is there a way to make the Wiki 'New Page' button default to a file type of Asciidoc instead of Markdown?
>
> ----- Original Message -----
>> From: "Sande Gilda" <sgilda at redhat.com>
>> To: "Windup-dev List" <windup-dev at lists.jboss.org>
>> Sent: Wednesday, September 3, 2014 7:58:26 PM
>> Subject: Re: [windup-dev] Wiki links trick for colon
>>
>> The Windup Wiki pages are now converted to Asciidoc. I tried using the
>> 'mv' command, but it didn't seem to convert the source correctly, so I
>> used Pandoc to convert the pages locally and pasted the results into the
>> Wiki pages. All the pages have now been converted except
>> 'Dev:-Decompile' because Ondra was editing that one. I still need to go
>> through them and clean up any additional conversion issues and fix
>> broken links. Let me know if you see any problems.
>>
>> On 09/03/2014 01:04 PM, Pete Muir wrote:
>>> Yes, some of it is not the advised syntax for asciidoc, but it does work
>>> iirc (actually now i?m not sure if mark-down links work?)
>>>
>>> On 3 Sep 2014, at 17:58, Lincoln Baxter, III <lincolnbaxter at gmail.com>
>>> wrote:
>>>
>>>> Asciidoc can read all the standard Markdown syntax? Interesting. Figures
>>>> :)
>>>>
>>>>
>>>> On Wed, Sep 3, 2014 at 11:45 AM, Pete Muir <pmuir at redhat.com> wrote:
>>>> You can just do mv my.md my.adoc
>>>>
>>>> Asciidoc can read all the standard asciidoc syntax afaik.
>>>>
>>>> On 3 Sep 2014, at 16:41, Sande Gilda <sgilda at redhat.com> wrote:
>>>>
>>>>> Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc
>>>>> converter utility? ;-)
>>>>>
>>>>> I need to get up to speed with Asciidoc so I can convert the pages.
>>>>>
>>>>> On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
>>>>>> Speaking of Formatting, it would be nice if the Wiki pages were written
>>>>>> in Asciidoc instead of Markdown. It doesn't *really* matter, but it
>>>>>> kind of matters because Asciidoc interops with Docbook well.
>>>>>>
>>>>>>
>>>>>> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com> wrote:
>>>>>> Hi Ondra,
>>>>>>
>>>>>> Should we replace the colons in the page titles with '_' or something
>>>>>> else to make it easier? For example 'Foo_BarI don't mind doing that and
>>>>>> it shouldn't take too long.
>>>>>>
>>>>>> Thanks,
>>>>>> Sande
>>>>>>
>>>>>> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> to save you some time figuring it out:
>>>>>>> GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
>>>>>>> like this:
>>>>>>>
>>>>>>> A) [blah](Foo%3A-Bar)
>>>>>>> B) [blah](./Foo:-Bar)
>>>>>>> C) [blah](./Foo: Bar)
>>>>>>> D) If all fails - full URL.
>>>>>>>
>>>>>>> HTH,
>>>>>>> Ondra
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Lincoln Baxter, III
>>>>>> http://ocpsoft.org
>>>>>> "Simpler is better."
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>>
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>
>>>>
>>>>
>>>> --
>>>> Lincoln Baxter, III
>>>> http://ocpsoft.org
>>>> "Simpler is better."
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From pmuir at redhat.com Thu Sep 4 05:27:02 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 4 Sep 2014 10:27:02 +0100
Subject: [windup-dev] Bootstrapping in tests
In-Reply-To: <54079871.4000104@redhat.com>
References: <54079871.4000104@redhat.com>
Message-ID: <F81C67E0-1F81-4FA8-A8F2-21D6413A5523@redhat.com>
Create a class for each bootstrap phase you want. Create an ordered list of the phase classes. Iterate over the list. Emit a CDI event for each phase, and have anything that needs to execute in that phase observe that event and start. Observe the built in @Initialized ApplicationContext event to kick off your bootstrap class.
On 3 Sep 2014, at 23:38, Ondrej Zizka <ozizka at redhat.com> wrote:
> Hi all,
>
> I've hit a problem with bootstrapping.
> The tests grab the parts of windup through CDI and that initializes them
> with defaults.
>
> For example, JavaClassTest#testIterationVariableResolving():
>
> The context initializes at the first line.
> When processor.execute() is called, the graph was somehow reused before,
> but that's just because of different code in all the execute() methods.
>
> I could simply not set the output dir to WindupProcessorConfig, but the
> output is not just where graph is.
> I could also check if the graph already has been initialized, but 1)
> that would make it nonconfigurable, 2) it would be nonsystemic -
> checking in init code if a part of application being initialized was, by
> accident, initialized somewhere else.
>
> My suggestion is that we should have kind of bootstrap API for the
> graph, similar to WindupProcessor - with a config class, and initialize
> it from that.
> I don't know how to combine that with CDI, so the tests would have to
> use that API instead of CDI.
> That's something I have suggested before, and was rejected, perhaps I
> didn't explain it clearly back then.
>
> I can't think up any other solution that I would not consider overkill,
> like, some CDI providers of the config.
> Any suggestions?
>
> Ondra
>
> -------------------------------------------------------------------------------
> Test set: org.jboss.windup.rules.java.JavaClassTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.678
> sec <<< FAILURE! - in org.jboss.windup.rules.java.JavaClassTest
> testIterationVariableResolving(org.jboss.windup.rules.java.JavaClassTest) Time
> elapsed: 5.346 sec <<< ERROR!
> org.jboss.windup.util.exception.WindupException_$$_javassist_9c4de665-baa6-4904-a4d3-37530e41e5a0:
> Error, attempting to set graph directory to:
> "/home/ondra/work/Migration/Windup/rules/app/java/target/windup_5ba22a23-c85f-49f3-b01c-39fda0eb1faa/graph",
> but the graph has already been initialized (with graph folder:
> "/home/ondra/work/Migration/Windup/rules/app/java/target/windupgraph_1cfccd03-8f33-43a4-a305-99fdd38bc172"!
> To change this, you must first disconnect from the graph!
> at
> org.jboss.windup.graph.GraphContextImpl.setGraphDirectory(GraphContextImpl.java:101)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:38)
> at
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
> at
> org.jboss.weld.proxies.GraphContext$2110577583$Proxy$_$$_WeldClientProxy.setGraphDirectory(Unknown
> Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at
> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at
> org.jboss.windup.graph.GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.setGraphDirectory(GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.java)
> at
> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at
> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at
> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.execute(WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.java)
> at
> org.jboss.windup.rules.java.JavaClassTest.testIterationVariableResolving(JavaClassTest.java:118)
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From sgilda at redhat.com Thu Sep 4 08:12:27 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 04 Sep 2014 08:12:27 -0400
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <A5C22CA8-F3A4-4709-80C1-9D9D22013DDF@redhat.com>
References: <54067F4A.3050200@redhat.com>
<5406FCDD.8000600@redhat.com> <CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com> <540736C1.4020602@redhat.com> <075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com> <CAEp_U4GAf9UZxM=TUnYM4xZEKa7q-PDW+mBaVJbqtA=pdr6TUw@mail.gmail.com> <9072C0F6-D827-4A87-A240-B7776D5244BF@redhat.com> <5407AB22.1090009@redhat.com> <765465901.16343766.1409789375770.JavaMail.zimbra@redhat.com>
<A5C22CA8-F3A4-4709-80C1-9D9D22013DDF@redhat.com>
Message-ID: <5408572B.5010301@redhat.com>
Thanks Pete. I guess we all need to be sure to change the selection when
we create new pages.
For those not familiar with AsciiDoc, I found a really helpful
'cheatsheet' here:
http://powerman.name/doc/asciidoc
Also, Joshua Wolf pinged me with these links related to new efforts to
standardize Markdown last night:
http://www.2ality.com/2014/09/standard-markdown.html
http://blog.codinghorror.com/standard-flavored-markdown/
On 09/04/2014 04:31 AM, Pete Muir wrote:
> I can?t see one https://help.github.com/articles/adding-wiki-pages-via-the-online-interface
>
> On 4 Sep 2014, at 01:09, Sande Gilda <sgilda at redhat.com> wrote:
>
>> Also, is there a way to make the Wiki 'New Page' button default to a file type of Asciidoc instead of Markdown?
>>
>> ----- Original Message -----
>>> From: "Sande Gilda" <sgilda at redhat.com>
>>> To: "Windup-dev List" <windup-dev at lists.jboss.org>
>>> Sent: Wednesday, September 3, 2014 7:58:26 PM
>>> Subject: Re: [windup-dev] Wiki links trick for colon
>>>
>>> The Windup Wiki pages are now converted to Asciidoc. I tried using the
>>> 'mv' command, but it didn't seem to convert the source correctly, so I
>>> used Pandoc to convert the pages locally and pasted the results into the
>>> Wiki pages. All the pages have now been converted except
>>> 'Dev:-Decompile' because Ondra was editing that one. I still need to go
>>> through them and clean up any additional conversion issues and fix
>>> broken links. Let me know if you see any problems.
>>>
>>> On 09/03/2014 01:04 PM, Pete Muir wrote:
>>>> Yes, some of it is not the advised syntax for asciidoc, but it does work
>>>> iirc (actually now i?m not sure if mark-down links work?)
>>>>
>>>> On 3 Sep 2014, at 17:58, Lincoln Baxter, III <lincolnbaxter at gmail.com>
>>>> wrote:
>>>>
>>>>> Asciidoc can read all the standard Markdown syntax? Interesting. Figures
>>>>> :)
>>>>>
>>>>>
>>>>> On Wed, Sep 3, 2014 at 11:45 AM, Pete Muir <pmuir at redhat.com> wrote:
>>>>> You can just do mv my.md my.adoc
>>>>>
>>>>> Asciidoc can read all the standard asciidoc syntax afaik.
>>>>>
>>>>> On 3 Sep 2014, at 16:41, Sande Gilda <sgilda at redhat.com> wrote:
>>>>>
>>>>>> Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc
>>>>>> converter utility? ;-)
>>>>>>
>>>>>> I need to get up to speed with Asciidoc so I can convert the pages.
>>>>>>
>>>>>> On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
>>>>>>> Speaking of Formatting, it would be nice if the Wiki pages were written
>>>>>>> in Asciidoc instead of Markdown. It doesn't *really* matter, but it
>>>>>>> kind of matters because Asciidoc interops with Docbook well.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda <sgilda at redhat.com> wrote:
>>>>>>> Hi Ondra,
>>>>>>>
>>>>>>> Should we replace the colons in the page titles with '_' or something
>>>>>>> else to make it easier? For example 'Foo_BarI don't mind doing that and
>>>>>>> it shouldn't take too long.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sande
>>>>>>>
>>>>>>> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> to save you some time figuring it out:
>>>>>>>> GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
>>>>>>>> like this:
>>>>>>>>
>>>>>>>> A) [blah](Foo%3A-Bar)
>>>>>>>> B) [blah](./Foo:-Bar)
>>>>>>>> C) [blah](./Foo: Bar)
>>>>>>>> D) If all fails - full URL.
>>>>>>>>
>>>>>>>> HTH,
>>>>>>>> Ondra
>>>>>>> _______________________________________________
>>>>>>> windup-dev mailing list
>>>>>>> windup-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Lincoln Baxter, III
>>>>>>> http://ocpsoft.org
>>>>>>> "Simpler is better."
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> windup-dev mailing list
>>>>>>>
>>>>>>> windup-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lincoln Baxter, III
>>>>> http://ocpsoft.org
>>>>> "Simpler is better."
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140904/24acd7fe/attachment.html
From pmuir at redhat.com Thu Sep 4 08:23:42 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 4 Sep 2014 13:23:42 +0100
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <5408572B.5010301@redhat.com>
References: <54067F4A.3050200@redhat.com>
<5406FCDD.8000600@redhat.com> <CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com> <540736C1.4020602@redhat.com> <075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com> <CAEp_U4GAf9UZxM=TUnYM4xZEKa7q-PDW+mBaVJbqtA=pdr6TUw@mail.gmail.com> <9072C0F6-D827-4A87-A240-B7776D5244BF@redhat.com> <5407AB22.1090009@redhat.com> <765465901.16343766.1409789375770.JavaMail.zimbra@redhat.com>
<A5C22CA8-F3A4-4709-80C1-9D9D22013DDF@redhat.com>
<5408572B.5010301@redhat.com>
Message-ID: <8843127B-D21C-400E-A071-C51DB8DAB649@redhat.com>
Also check out http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/
On 4 Sep 2014, at 13:12, Sande Gilda <sgilda at redhat.com> wrote:
> Thanks Pete. I guess we all need to be sure to change the selection when we create new pages.
>
> For those not familiar with AsciiDoc, I found a really helpful 'cheatsheet' here:
> http://powerman.name/doc/asciidoc
> Also, Joshua Wolf pinged me with these links related to new efforts to standardize Markdown last night:
> http://www.2ality.com/2014/09/standard-markdown.html
> http://blog.codinghorror.com/standard-flavored-markdown/
>
> On 09/04/2014 04:31 AM, Pete Muir wrote:
>> I can?t see one https://help.github.com/articles/adding-wiki-pages-via-the-online-interface
>>
>>
>> On 4 Sep 2014, at 01:09, Sande Gilda
>> <sgilda at redhat.com>
>> wrote:
>>
>>
>>> Also, is there a way to make the Wiki 'New Page' button default to a file type of Asciidoc instead of Markdown?
>>>
>>> ----- Original Message -----
>>>
>>>> From: "Sande Gilda" <sgilda at redhat.com>
>>>>
>>>> To: "Windup-dev List"
>>>> <windup-dev at lists.jboss.org>
>>>>
>>>> Sent: Wednesday, September 3, 2014 7:58:26 PM
>>>> Subject: Re: [windup-dev] Wiki links trick for colon
>>>>
>>>> The Windup Wiki pages are now converted to Asciidoc. I tried using the
>>>> 'mv' command, but it didn't seem to convert the source correctly, so I
>>>> used Pandoc to convert the pages locally and pasted the results into the
>>>> Wiki pages. All the pages have now been converted except
>>>> 'Dev:-Decompile' because Ondra was editing that one. I still need to go
>>>> through them and clean up any additional conversion issues and fix
>>>> broken links. Let me know if you see any problems.
>>>>
>>>> On 09/03/2014 01:04 PM, Pete Muir wrote:
>>>>
>>>>> Yes, some of it is not the advised syntax for asciidoc, but it does work
>>>>> iirc (actually now i?m not sure if mark-down links work?)
>>>>>
>>>>> On 3 Sep 2014, at 17:58, Lincoln Baxter, III
>>>>> <lincolnbaxter at gmail.com>
>>>>>
>>>>> wrote:
>>>>>
>>>>>
>>>>>> Asciidoc can read all the standard Markdown syntax? Interesting. Figures
>>>>>> :)
>>>>>>
>>>>>>
>>>>>> On Wed, Sep 3, 2014 at 11:45 AM, Pete Muir
>>>>>> <pmuir at redhat.com>
>>>>>> wrote:
>>>>>> You can just do mv my.md my.adoc
>>>>>>
>>>>>> Asciidoc can read all the standard asciidoc syntax afaik.
>>>>>>
>>>>>> On 3 Sep 2014, at 16:41, Sande Gilda
>>>>>> <sgilda at redhat.com>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>> Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc
>>>>>>> converter utility? ;-)
>>>>>>>
>>>>>>> I need to get up to speed with Asciidoc so I can convert the pages.
>>>>>>>
>>>>>>> On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
>>>>>>>
>>>>>>>> Speaking of Formatting, it would be nice if the Wiki pages were written
>>>>>>>> in Asciidoc instead of Markdown. It doesn't *really* matter, but it
>>>>>>>> kind of matters because Asciidoc interops with Docbook well.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda
>>>>>>>> <sgilda at redhat.com>
>>>>>>>> wrote:
>>>>>>>> Hi Ondra,
>>>>>>>>
>>>>>>>> Should we replace the colons in the page titles with '_' or something
>>>>>>>> else to make it easier? For example 'Foo_BarI don't mind doing that and
>>>>>>>> it shouldn't take too long.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sande
>>>>>>>>
>>>>>>>> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> to save you some time figuring it out:
>>>>>>>>> GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
>>>>>>>>> like this:
>>>>>>>>>
>>>>>>>>> A) [blah](Foo%3A-Bar)
>>>>>>>>> B) [blah](./Foo:-Bar)
>>>>>>>>> C) [blah](./Foo: Bar)
>>>>>>>>> D) If all fails - full URL.
>>>>>>>>>
>>>>>>>>> HTH,
>>>>>>>>> Ondra
>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> windup-dev mailing list
>>>>>>>>
>>>>>>>> windup-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Lincoln Baxter, III
>>>>>>>>
>>>>>>>> http://ocpsoft.org
>>>>>>>>
>>>>>>>> "Simpler is better."
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> windup-dev mailing list
>>>>>>>>
>>>>>>>>
>>>>>>>> windup-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>> _______________________________________________
>>>>>>> windup-dev mailing list
>>>>>>>
>>>>>>> windup-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>>
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Lincoln Baxter, III
>>>>>>
>>>>>> http://ocpsoft.org
>>>>>>
>>>>>> "Simpler is better."
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>>
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>>
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>>
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>>
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Thu Sep 4 09:13:27 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 04 Sep 2014 15:13:27 +0200
Subject: [windup-dev] Windup 1 vs 2 comparison - automated
In-Reply-To: <CAEp_U4GL9rmG_zjFUTz=GEf1UT+++e1ZCAwwV6Wkca21SEwANg@mail.gmail.com>
References: <5403A5C4.7030400@redhat.com>
<CAEp_U4GL9rmG_zjFUTz=GEf1UT+++e1ZCAwwV6Wkca21SEwANg@mail.gmail.com>
Message-ID: <54086577.1090403@redhat.com>
It should be accessible, IDK why you get 404, can you see something at
http://www.qa.jboss.com/~ozizka/ ?
Ondra
On 2.9.2014 22:37, Lincoln Baxter, III wrote:
> Hmm... I am unable to view those files. 404 (I am on the VPN) Could
> you grant public access? Thanks!
>
>
> On Sun, Aug 31, 2014 at 6:46 PM, Ondrej Zizka <ozizka at redhat.com
> <mailto:ozizka at redhat.com>> wrote:
>
> Hi all,
>
> I've finished automation of $subj.
> In terms of speed, memory, and links to the reports and logs next to
> each other, in a matrix.
> Check the results here:
> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02/Results.html
> <http://www.qa.jboss.com/%7Eozizka/Windup/compar/WindupComparison02/Results.html>
> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02.zip
> <http://www.qa.jboss.com/%7Eozizka/Windup/compar/WindupComparison02.zip>
>
> There are some issues with Windup 2.x - namely, failing with
> exceptions
> inside of rules, not reacting to multiple --packages.
>
> It needs a bit of setup - the test apps need to be at given
> relative paths.
> Let me know if you are interested in running this for yourself.
>
> I hope you'll find this useful.
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140904/9b3f46e4/attachment.html
From pmuir at redhat.com Thu Sep 4 09:17:21 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 4 Sep 2014 14:17:21 +0100
Subject: [windup-dev] Windup 1 vs 2 comparison - automated
In-Reply-To: <54086577.1090403@redhat.com>
References: <5403A5C4.7030400@redhat.com>
<CAEp_U4GL9rmG_zjFUTz=GEf1UT+++e1ZCAwwV6Wkca21SEwANg@mail.gmail.com>
<54086577.1090403@redhat.com>
Message-ID: <7E0FB107-5D53-41E9-A9A5-C4382D76F051@redhat.com>
Those old jboss.com internal URLs have semi-broken DNS.
If you are on mac or ubuntu you need to put the IP in your hosts file.
On 4 Sep 2014, at 14:13, Ondrej Zizka <ozizka at redhat.com> wrote:
> It should be accessible, IDK why you get 404, can you see something at
> http://www.qa.jboss.com/~ozizka/ ?
>
> Ondra
>
> On 2.9.2014 22:37, Lincoln Baxter, III wrote:
>> Hmm... I am unable to view those files. 404 (I am on the VPN) Could you grant public access? Thanks!
>>
>>
>> On Sun, Aug 31, 2014 at 6:46 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
>> Hi all,
>>
>> I've finished automation of $subj.
>> In terms of speed, memory, and links to the reports and logs next to
>> each other, in a matrix.
>> Check the results here:
>> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02/Results.html
>> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02.zip
>>
>> There are some issues with Windup 2.x - namely, failing with exceptions
>> inside of rules, not reacting to multiple --packages.
>>
>> It needs a bit of setup - the test apps need to be at given relative paths.
>> Let me know if you are interested in running this for yourself.
>>
>> I hope you'll find this useful.
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>>
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Thu Sep 4 09:19:22 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 04 Sep 2014 15:19:22 +0200
Subject: [windup-dev] Bootstrapping in tests
In-Reply-To: <F81C67E0-1F81-4FA8-A8F2-21D6413A5523@redhat.com>
References: <54079871.4000104@redhat.com>
<F81C67E0-1F81-4FA8-A8F2-21D6413A5523@redhat.com>
Message-ID: <540866DA.7030301@redhat.com>
I think I will need more explanation on this.
I still don't know how could I test WindupProcessor, which should
initialize the graph, while having the graph already initialized.
Is that what the description below would solve?
Ondra
On 4.9.2014 11:27, Pete Muir wrote:
> Create a class for each bootstrap phase you want. Create an ordered list of the phase classes. Iterate over the list. Emit a CDI event for each phase, and have anything that needs to execute in that phase observe that event and start. Observe the built in @Initialized ApplicationContext event to kick off your bootstrap class.
>
> On 3 Sep 2014, at 23:38, Ondrej Zizka <ozizka at redhat.com> wrote:
>
>> Hi all,
>>
>> I've hit a problem with bootstrapping.
>> The tests grab the parts of windup through CDI and that initializes them
>> with defaults.
>>
>> For example, JavaClassTest#testIterationVariableResolving():
>>
>> The context initializes at the first line.
>> When processor.execute() is called, the graph was somehow reused before,
>> but that's just because of different code in all the execute() methods.
>>
>> I could simply not set the output dir to WindupProcessorConfig, but the
>> output is not just where graph is.
>> I could also check if the graph already has been initialized, but 1)
>> that would make it nonconfigurable, 2) it would be nonsystemic -
>> checking in init code if a part of application being initialized was, by
>> accident, initialized somewhere else.
>>
>> My suggestion is that we should have kind of bootstrap API for the
>> graph, similar to WindupProcessor - with a config class, and initialize
>> it from that.
>> I don't know how to combine that with CDI, so the tests would have to
>> use that API instead of CDI.
>> That's something I have suggested before, and was rejected, perhaps I
>> didn't explain it clearly back then.
>>
>> I can't think up any other solution that I would not consider overkill,
>> like, some CDI providers of the config.
>> Any suggestions?
>>
>> Ondra
>>
>> -------------------------------------------------------------------------------
>> Test set: org.jboss.windup.rules.java.JavaClassTest
>> -------------------------------------------------------------------------------
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.678
>> sec <<< FAILURE! - in org.jboss.windup.rules.java.JavaClassTest
>> testIterationVariableResolving(org.jboss.windup.rules.java.JavaClassTest) Time
>> elapsed: 5.346 sec <<< ERROR!
>> org.jboss.windup.util.exception.WindupException_$$_javassist_9c4de665-baa6-4904-a4d3-37530e41e5a0:
>> Error, attempting to set graph directory to:
>> "/home/ondra/work/Migration/Windup/rules/app/java/target/windup_5ba22a23-c85f-49f3-b01c-39fda0eb1faa/graph",
>> but the graph has already been initialized (with graph folder:
>> "/home/ondra/work/Migration/Windup/rules/app/java/target/windupgraph_1cfccd03-8f33-43a4-a305-99fdd38bc172"!
>> To change this, you must first disconnect from the graph!
>> at
>> org.jboss.windup.graph.GraphContextImpl.setGraphDirectory(GraphContextImpl.java:101)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:38)
>> at
>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
>> at
>> org.jboss.weld.proxies.GraphContext$2110577583$Proxy$_$$_WeldClientProxy.setGraphDirectory(Unknown
>> Source)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>> at
>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>> at
>> org.jboss.windup.graph.GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.setGraphDirectory(GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.java)
>> at
>> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:35)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>> at
>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>> at
>> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.execute(WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.java)
>> at
>> org.jboss.windup.rules.java.JavaClassTest.testIterationVariableResolving(JavaClassTest.java:118)
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From pmuir at redhat.com Thu Sep 4 09:21:28 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 4 Sep 2014 14:21:28 +0100
Subject: [windup-dev] Bootstrapping in tests
In-Reply-To: <540866DA.7030301@redhat.com>
References: <54079871.4000104@redhat.com>
<F81C67E0-1F81-4FA8-A8F2-21D6413A5523@redhat.com>
<540866DA.7030301@redhat.com>
Message-ID: <BAE06FDC-A492-465A-BE5C-61F77FF6447E@redhat.com>
What are you actually trying to test?
On 4 Sep 2014, at 14:19, Ondrej Zizka <ozizka at redhat.com> wrote:
> I think I will need more explanation on this.
> I still don't know how could I test WindupProcessor, which should
> initialize the graph, while having the graph already initialized.
> Is that what the description below would solve?
>
> Ondra
>
>
> On 4.9.2014 11:27, Pete Muir wrote:
>> Create a class for each bootstrap phase you want. Create an ordered list of the phase classes. Iterate over the list. Emit a CDI event for each phase, and have anything that needs to execute in that phase observe that event and start. Observe the built in @Initialized ApplicationContext event to kick off your bootstrap class.
>>
>> On 3 Sep 2014, at 23:38, Ondrej Zizka <ozizka at redhat.com> wrote:
>>
>>> Hi all,
>>>
>>> I've hit a problem with bootstrapping.
>>> The tests grab the parts of windup through CDI and that initializes them
>>> with defaults.
>>>
>>> For example, JavaClassTest#testIterationVariableResolving():
>>>
>>> The context initializes at the first line.
>>> When processor.execute() is called, the graph was somehow reused before,
>>> but that's just because of different code in all the execute() methods.
>>>
>>> I could simply not set the output dir to WindupProcessorConfig, but the
>>> output is not just where graph is.
>>> I could also check if the graph already has been initialized, but 1)
>>> that would make it nonconfigurable, 2) it would be nonsystemic -
>>> checking in init code if a part of application being initialized was, by
>>> accident, initialized somewhere else.
>>>
>>> My suggestion is that we should have kind of bootstrap API for the
>>> graph, similar to WindupProcessor - with a config class, and initialize
>>> it from that.
>>> I don't know how to combine that with CDI, so the tests would have to
>>> use that API instead of CDI.
>>> That's something I have suggested before, and was rejected, perhaps I
>>> didn't explain it clearly back then.
>>>
>>> I can't think up any other solution that I would not consider overkill,
>>> like, some CDI providers of the config.
>>> Any suggestions?
>>>
>>> Ondra
>>>
>>> -------------------------------------------------------------------------------
>>> Test set: org.jboss.windup.rules.java.JavaClassTest
>>> -------------------------------------------------------------------------------
>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.678
>>> sec <<< FAILURE! - in org.jboss.windup.rules.java.JavaClassTest
>>> testIterationVariableResolving(org.jboss.windup.rules.java.JavaClassTest) Time
>>> elapsed: 5.346 sec <<< ERROR!
>>> org.jboss.windup.util.exception.WindupException_$$_javassist_9c4de665-baa6-4904-a4d3-37530e41e5a0:
>>> Error, attempting to set graph directory to:
>>> "/home/ondra/work/Migration/Windup/rules/app/java/target/windup_5ba22a23-c85f-49f3-b01c-39fda0eb1faa/graph",
>>> but the graph has already been initialized (with graph folder:
>>> "/home/ondra/work/Migration/Windup/rules/app/java/target/windupgraph_1cfccd03-8f33-43a4-a305-99fdd38bc172"!
>>> To change this, you must first disconnect from the graph!
>>> at
>>> org.jboss.windup.graph.GraphContextImpl.setGraphDirectory(GraphContextImpl.java:101)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at
>>> org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:38)
>>> at
>>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
>>> at
>>> org.jboss.weld.proxies.GraphContext$2110577583$Proxy$_$$_WeldClientProxy.setGraphDirectory(Unknown
>>> Source)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at
>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>>> at
>>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
>>> at
>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>>> at
>>> org.jboss.windup.graph.GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.setGraphDirectory(GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.java)
>>> at
>>> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:35)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at
>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>>> at
>>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
>>> at
>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>>> at
>>> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.execute(WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.java)
>>> at
>>> org.jboss.windup.rules.java.JavaClassTest.testIterationVariableResolving(JavaClassTest.java:118)
>>>
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From pmuir at redhat.com Thu Sep 4 09:24:11 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 4 Sep 2014 14:24:11 +0100
Subject: [windup-dev] Bootstrapping in tests
In-Reply-To: <BAE06FDC-A492-465A-BE5C-61F77FF6447E@redhat.com>
References: <54079871.4000104@redhat.com>
<F81C67E0-1F81-4FA8-A8F2-21D6413A5523@redhat.com>
<540866DA.7030301@redhat.com>
<BAE06FDC-A492-465A-BE5C-61F77FF6447E@redhat.com>
Message-ID: <EF7DE6E5-917D-4160-81A8-78C62AF66FF3@redhat.com>
For example, if you are trying to insert some config into the bootstrap you could have an event like:
public void postConfig(@Observes PostConfiguration evt) {
evt.getBoostrap().setConfig(myCustomConfig);
}
On 4 Sep 2014, at 14:21, Pete Muir <pmuir at redhat.com> wrote:
> What are you actually trying to test?
>
> On 4 Sep 2014, at 14:19, Ondrej Zizka <ozizka at redhat.com> wrote:
>
>> I think I will need more explanation on this.
>> I still don't know how could I test WindupProcessor, which should
>> initialize the graph, while having the graph already initialized.
>> Is that what the description below would solve?
>>
>> Ondra
>>
>>
>> On 4.9.2014 11:27, Pete Muir wrote:
>>> Create a class for each bootstrap phase you want. Create an ordered list of the phase classes. Iterate over the list. Emit a CDI event for each phase, and have anything that needs to execute in that phase observe that event and start. Observe the built in @Initialized ApplicationContext event to kick off your bootstrap class.
>>>
>>> On 3 Sep 2014, at 23:38, Ondrej Zizka <ozizka at redhat.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I've hit a problem with bootstrapping.
>>>> The tests grab the parts of windup through CDI and that initializes them
>>>> with defaults.
>>>>
>>>> For example, JavaClassTest#testIterationVariableResolving():
>>>>
>>>> The context initializes at the first line.
>>>> When processor.execute() is called, the graph was somehow reused before,
>>>> but that's just because of different code in all the execute() methods.
>>>>
>>>> I could simply not set the output dir to WindupProcessorConfig, but the
>>>> output is not just where graph is.
>>>> I could also check if the graph already has been initialized, but 1)
>>>> that would make it nonconfigurable, 2) it would be nonsystemic -
>>>> checking in init code if a part of application being initialized was, by
>>>> accident, initialized somewhere else.
>>>>
>>>> My suggestion is that we should have kind of bootstrap API for the
>>>> graph, similar to WindupProcessor - with a config class, and initialize
>>>> it from that.
>>>> I don't know how to combine that with CDI, so the tests would have to
>>>> use that API instead of CDI.
>>>> That's something I have suggested before, and was rejected, perhaps I
>>>> didn't explain it clearly back then.
>>>>
>>>> I can't think up any other solution that I would not consider overkill,
>>>> like, some CDI providers of the config.
>>>> Any suggestions?
>>>>
>>>> Ondra
>>>>
>>>> -------------------------------------------------------------------------------
>>>> Test set: org.jboss.windup.rules.java.JavaClassTest
>>>> -------------------------------------------------------------------------------
>>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.678
>>>> sec <<< FAILURE! - in org.jboss.windup.rules.java.JavaClassTest
>>>> testIterationVariableResolving(org.jboss.windup.rules.java.JavaClassTest) Time
>>>> elapsed: 5.346 sec <<< ERROR!
>>>> org.jboss.windup.util.exception.WindupException_$$_javassist_9c4de665-baa6-4904-a4d3-37530e41e5a0:
>>>> Error, attempting to set graph directory to:
>>>> "/home/ondra/work/Migration/Windup/rules/app/java/target/windup_5ba22a23-c85f-49f3-b01c-39fda0eb1faa/graph",
>>>> but the graph has already been initialized (with graph folder:
>>>> "/home/ondra/work/Migration/Windup/rules/app/java/target/windupgraph_1cfccd03-8f33-43a4-a305-99fdd38bc172"!
>>>> To change this, you must first disconnect from the graph!
>>>> at
>>>> org.jboss.windup.graph.GraphContextImpl.setGraphDirectory(GraphContextImpl.java:101)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>> at
>>>> org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:38)
>>>> at
>>>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
>>>> at
>>>> org.jboss.weld.proxies.GraphContext$2110577583$Proxy$_$$_WeldClientProxy.setGraphDirectory(Unknown
>>>> Source)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>> at
>>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>>>> at
>>>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
>>>> at
>>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>>>> at
>>>> org.jboss.windup.graph.GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.setGraphDirectory(GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.java)
>>>> at
>>>> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:35)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>> at
>>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>>>> at
>>>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
>>>> at
>>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>>>> at
>>>> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.execute(WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.java)
>>>> at
>>>> org.jboss.windup.rules.java.JavaClassTest.testIterationVariableResolving(JavaClassTest.java:118)
>>>>
>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
From ozizka at redhat.com Thu Sep 4 09:42:53 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 04 Sep 2014 15:42:53 +0200
Subject: [windup-dev] Bootstrapping in tests
In-Reply-To: <BAE06FDC-A492-465A-BE5C-61F77FF6447E@redhat.com>
References: <54079871.4000104@redhat.com> <F81C67E0-1F81-4FA8-A8F2-21D6413A5523@redhat.com> <540866DA.7030301@redhat.com>
<BAE06FDC-A492-465A-BE5C-61F77FF6447E@redhat.com>
Message-ID: <54086C5D.6080307@redhat.com>
I'll shorten the original mail:
There is an existing test, which worked formerly, because there were 4
different impls of WindupProcessor#execute().
Now if done through a execute(WindupProcessorConfig), it tries to set
the outputDir of the graph, which fails because the graph is already
initialized, because the test needs to put some data to it.
Even shorter:
test(){
init graph;
put some data to graph;
create WindupProcessorConfig, including outputDir
call WindupProcessor#execute( config );
}
execute(){
initializeGraph( config )
}
Ondra
On 4.9.2014 15:21, Pete Muir wrote:
> What are you actually trying to test?
>
> On 4 Sep 2014, at 14:19, Ondrej Zizka <ozizka at redhat.com> wrote:
>
>> I think I will need more explanation on this.
>> I still don't know how could I test WindupProcessor, which should
>> initialize the graph, while having the graph already initialized.
>> Is that what the description below would solve?
>>
>> Ondra
>>
>>
>> On 4.9.2014 11:27, Pete Muir wrote:
>>> Create a class for each bootstrap phase you want. Create an ordered list of the phase classes. Iterate over the list. Emit a CDI event for each phase, and have anything that needs to execute in that phase observe that event and start. Observe the built in @Initialized ApplicationContext event to kick off your bootstrap class.
>>>
>>> On 3 Sep 2014, at 23:38, Ondrej Zizka <ozizka at redhat.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I've hit a problem with bootstrapping.
>>>> The tests grab the parts of windup through CDI and that initializes them
>>>> with defaults.
>>>>
>>>> For example, JavaClassTest#testIterationVariableResolving():
>>>>
>>>> The context initializes at the first line.
>>>> When processor.execute() is called, the graph was somehow reused before,
>>>> but that's just because of different code in all the execute() methods.
>>>>
>>>> I could simply not set the output dir to WindupProcessorConfig, but the
>>>> output is not just where graph is.
>>>> I could also check if the graph already has been initialized, but 1)
>>>> that would make it nonconfigurable, 2) it would be nonsystemic -
>>>> checking in init code if a part of application being initialized was, by
>>>> accident, initialized somewhere else.
>>>>
>>>> My suggestion is that we should have kind of bootstrap API for the
>>>> graph, similar to WindupProcessor - with a config class, and initialize
>>>> it from that.
>>>> I don't know how to combine that with CDI, so the tests would have to
>>>> use that API instead of CDI.
>>>> That's something I have suggested before, and was rejected, perhaps I
>>>> didn't explain it clearly back then.
>>>>
>>>> I can't think up any other solution that I would not consider overkill,
>>>> like, some CDI providers of the config.
>>>> Any suggestions?
>>>>
>>>> Ondra
>>>>
>>>> -------------------------------------------------------------------------------
>>>> Test set: org.jboss.windup.rules.java.JavaClassTest
>>>> -------------------------------------------------------------------------------
>>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.678
>>>> sec <<< FAILURE! - in org.jboss.windup.rules.java.JavaClassTest
>>>> testIterationVariableResolving(org.jboss.windup.rules.java.JavaClassTest) Time
>>>> elapsed: 5.346 sec <<< ERROR!
>>>> org.jboss.windup.util.exception.WindupException_$$_javassist_9c4de665-baa6-4904-a4d3-37530e41e5a0:
>>>> Error, attempting to set graph directory to:
>>>> "/home/ondra/work/Migration/Windup/rules/app/java/target/windup_5ba22a23-c85f-49f3-b01c-39fda0eb1faa/graph",
>>>> but the graph has already been initialized (with graph folder:
>>>> "/home/ondra/work/Migration/Windup/rules/app/java/target/windupgraph_1cfccd03-8f33-43a4-a305-99fdd38bc172"!
>>>> To change this, you must first disconnect from the graph!
>>>> at
>>>> org.jboss.windup.graph.GraphContextImpl.setGraphDirectory(GraphContextImpl.java:101)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>> at
>>>> org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:38)
>>>> at
>>>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
>>>> at
>>>> org.jboss.weld.proxies.GraphContext$2110577583$Proxy$_$$_WeldClientProxy.setGraphDirectory(Unknown
>>>> Source)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>> at
>>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>>>> at
>>>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
>>>> at
>>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>>>> at
>>>> org.jboss.windup.graph.GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.setGraphDirectory(GraphContext_$$_javassist_328a8426-f2d1-4f83-9490-e69b40a9c068.java)
>>>> at
>>>> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:35)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>> at
>>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>>>> at
>>>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
>>>> at
>>>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>>>> at
>>>> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.execute(WindupProcessorImpl_$$_javassist_5bf57ffb-10b3-495a-81bb-f630878e67e5.java)
>>>> at
>>>> org.jboss.windup.rules.java.JavaClassTest.testIterationVariableResolving(JavaClassTest.java:118)
>>>>
>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From sgilda at redhat.com Thu Sep 4 11:26:19 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 04 Sep 2014 11:26:19 -0400
Subject: [windup-dev] Wiki links trick for colon
In-Reply-To: <8843127B-D21C-400E-A071-C51DB8DAB649@redhat.com>
References: <54067F4A.3050200@redhat.com> <5406FCDD.8000600@redhat.com> <CAEp_U4H44qr2mMwPoOkz0JMqOTgdQY1-k=NYN=MtegO4=EeMQQ@mail.gmail.com> <540736C1.4020602@redhat.com> <075992F0-9346-4BA5-A6FC-7239646FF5E9@redhat.com> <CAEp_U4GAf9UZxM=TUnYM4xZEKa7q-PDW+mBaVJbqtA=pdr6TUw@mail.gmail.com> <9072C0F6-D827-4A87-A240-B7776D5244BF@redhat.com> <5407AB22.1090009@redhat.com> <765465901.16343766.1409789375770.JavaMail.zimbra@redhat.com> <A5C22CA8-F3A4-4709-80C1-9D9D22013DDF@redhat.com> <5408572B.5010301@redhat.com>
<8843127B-D21C-400E-A071-C51DB8DAB649@redhat.com>
Message-ID: <5408849B.4020808@redhat.com>
I use that one also, but I find it somewhat annoying that you have to
click 'View Result' to see how it renders. I'm backwards (maybe because
I'm left-handed?) and like to find the formatting I'm going for and then
see how it's done.
On 09/04/2014 08:23 AM, Pete Muir wrote:
> Also check out http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/
>
> On 4 Sep 2014, at 13:12, Sande Gilda <sgilda at redhat.com> wrote:
>
>> Thanks Pete. I guess we all need to be sure to change the selection when we create new pages.
>>
>> For those not familiar with AsciiDoc, I found a really helpful 'cheatsheet' here:
>> http://powerman.name/doc/asciidoc
>> Also, Joshua Wolf pinged me with these links related to new efforts to standardize Markdown last night:
>> http://www.2ality.com/2014/09/standard-markdown.html
>> http://blog.codinghorror.com/standard-flavored-markdown/
>>
>> On 09/04/2014 04:31 AM, Pete Muir wrote:
>>> I can?t see one https://help.github.com/articles/adding-wiki-pages-via-the-online-interface
>>>
>>>
>>> On 4 Sep 2014, at 01:09, Sande Gilda
>>> <sgilda at redhat.com>
>>> wrote:
>>>
>>>
>>>> Also, is there a way to make the Wiki 'New Page' button default to a file type of Asciidoc instead of Markdown?
>>>>
>>>> ----- Original Message -----
>>>>
>>>>> From: "Sande Gilda" <sgilda at redhat.com>
>>>>>
>>>>> To: "Windup-dev List"
>>>>> <windup-dev at lists.jboss.org>
>>>>>
>>>>> Sent: Wednesday, September 3, 2014 7:58:26 PM
>>>>> Subject: Re: [windup-dev] Wiki links trick for colon
>>>>>
>>>>> The Windup Wiki pages are now converted to Asciidoc. I tried using the
>>>>> 'mv' command, but it didn't seem to convert the source correctly, so I
>>>>> used Pandoc to convert the pages locally and pasted the results into the
>>>>> Wiki pages. All the pages have now been converted except
>>>>> 'Dev:-Decompile' because Ondra was editing that one. I still need to go
>>>>> through them and clean up any additional conversion issues and fix
>>>>> broken links. Let me know if you see any problems.
>>>>>
>>>>> On 09/03/2014 01:04 PM, Pete Muir wrote:
>>>>>
>>>>>> Yes, some of it is not the advised syntax for asciidoc, but it does work
>>>>>> iirc (actually now i?m not sure if mark-down links work?)
>>>>>>
>>>>>> On 3 Sep 2014, at 17:58, Lincoln Baxter, III
>>>>>> <lincolnbaxter at gmail.com>
>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>> Asciidoc can read all the standard Markdown syntax? Interesting. Figures
>>>>>>> :)
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Sep 3, 2014 at 11:45 AM, Pete Muir
>>>>>>> <pmuir at redhat.com>
>>>>>>> wrote:
>>>>>>> You can just do mv my.md my.adoc
>>>>>>>
>>>>>>> Asciidoc can read all the standard asciidoc syntax afaik.
>>>>>>>
>>>>>>> On 3 Sep 2014, at 16:41, Sande Gilda
>>>>>>> <sgilda at redhat.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Yes, that makes total sense. I wonder if there's a Markdown --> Asciidoc
>>>>>>>> converter utility? ;-)
>>>>>>>>
>>>>>>>> I need to get up to speed with Asciidoc so I can convert the pages.
>>>>>>>>
>>>>>>>> On 09/03/2014 11:25 AM, Lincoln Baxter, III wrote:
>>>>>>>>
>>>>>>>>> Speaking of Formatting, it would be nice if the Wiki pages were written
>>>>>>>>> in Asciidoc instead of Markdown. It doesn't *really* matter, but it
>>>>>>>>> kind of matters because Asciidoc interops with Docbook well.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Sep 3, 2014 at 7:34 AM, Sande Gilda
>>>>>>>>> <sgilda at redhat.com>
>>>>>>>>> wrote:
>>>>>>>>> Hi Ondra,
>>>>>>>>>
>>>>>>>>> Should we replace the colons in the page titles with '_' or something
>>>>>>>>> else to make it easier? For example 'Foo_BarI don't mind doing that and
>>>>>>>>> it shouldn't take too long.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Sande
>>>>>>>>>
>>>>>>>>> On 09/02/2014 10:39 PM, Ondrej Zizka wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> to save you some time figuring it out:
>>>>>>>>>> GitHub wiki doesn't like : in links, so a link to "Foo: Bar" may look
>>>>>>>>>> like this:
>>>>>>>>>>
>>>>>>>>>> A) [blah](Foo%3A-Bar)
>>>>>>>>>> B) [blah](./Foo:-Bar)
>>>>>>>>>> C) [blah](./Foo: Bar)
>>>>>>>>>> D) If all fails - full URL.
>>>>>>>>>>
>>>>>>>>>> HTH,
>>>>>>>>>> Ondra
>>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> windup-dev mailing list
>>>>>>>>>
>>>>>>>>> windup-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Lincoln Baxter, III
>>>>>>>>>
>>>>>>>>> http://ocpsoft.org
>>>>>>>>>
>>>>>>>>> "Simpler is better."
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> windup-dev mailing list
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> windup-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>>> _______________________________________________
>>>>>>>> windup-dev mailing list
>>>>>>>>
>>>>>>>> windup-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>> _______________________________________________
>>>>>>> windup-dev mailing list
>>>>>>>
>>>>>>> windup-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Lincoln Baxter, III
>>>>>>>
>>>>>>> http://ocpsoft.org
>>>>>>>
>>>>>>> "Simpler is better."
>>>>>>> _______________________________________________
>>>>>>> windup-dev mailing list
>>>>>>>
>>>>>>> windup-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>>
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>>
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>>
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From lincolnbaxter at gmail.com Thu Sep 4 12:19:29 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 4 Sep 2014 12:19:29 -0400
Subject: [windup-dev] Windup Jira Triage Meeting Log - 2014-09-04
Message-ID: <CAEp_U4FZvhjVRHCGffEzxh-7JOYmg-CinXtUU2g3Z6xu8hx=Jg@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-04-14.25.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-04-14.25.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-04-14.25.log.html
Meeting summary
---------------
* WINDUP-90 closed as rejected (lincolnthree, 14:25:36)
* WINDUP-93 closed as done (lincolnthree, 14:28:34)
* WINDUP-99 closed as done (lincolnthree, 14:32:03)
* WINDUP-130 closed as done (lincolnthree, 14:47:25)
* WINDUP-140 closed as done (lincolnthree, 15:01:13)
* WINDUP-145 closed as rejected (lincolnthree, 15:05:37)
* WINDUP-187 closed as duplicate (lincolnthree, 15:56:09)
* WINDUP-189 closed as rejected (lincolnthree, 15:59:02)
* LINK: https://issues.jboss.org/browse/FORGE-1969 (lincolnthree,
16:16:52)
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140904/a427bff0/attachment.html
From lincolnbaxter at gmail.com Thu Sep 4 14:26:18 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 4 Sep 2014 14:26:18 -0400
Subject: [windup-dev] Windup 1 vs 2 comparison - automated
In-Reply-To: <7E0FB107-5D53-41E9-A9A5-C4382D76F051@redhat.com>
References: <5403A5C4.7030400@redhat.com>
<CAEp_U4GL9rmG_zjFUTz=GEf1UT+++e1ZCAwwV6Wkca21SEwANg@mail.gmail.com>
<54086577.1090403@redhat.com>
<7E0FB107-5D53-41E9-A9A5-C4382D76F051@redhat.com>
Message-ID: <CAEp_U4EMyY-uwrAef5ZNH6Crzii7yNzm+6H0RH_x=LVWP1RigQ@mail.gmail.com>
What is that IP address?
On Thu, Sep 4, 2014 at 9:17 AM, Pete Muir <pmuir at redhat.com> wrote:
> Those old jboss.com internal URLs have semi-broken DNS.
>
> If you are on mac or ubuntu you need to put the IP in your hosts file.
>
> On 4 Sep 2014, at 14:13, Ondrej Zizka <ozizka at redhat.com> wrote:
>
> > It should be accessible, IDK why you get 404, can you see something at
> > http://www.qa.jboss.com/~ozizka/ ?
> >
> > Ondra
> >
> > On 2.9.2014 22:37, Lincoln Baxter, III wrote:
> >> Hmm... I am unable to view those files. 404 (I am on the VPN) Could you
> grant public access? Thanks!
> >>
> >>
> >> On Sun, Aug 31, 2014 at 6:46 PM, Ondrej Zizka <ozizka at redhat.com>
> wrote:
> >> Hi all,
> >>
> >> I've finished automation of $subj.
> >> In terms of speed, memory, and links to the reports and logs next to
> >> each other, in a matrix.
> >> Check the results here:
> >>
> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02/Results.html
> >> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02.zip
> >>
> >> There are some issues with Windup 2.x - namely, failing with exceptions
> >> inside of rules, not reacting to multiple --packages.
> >>
> >> It needs a bit of setup - the test apps need to be at given relative
> paths.
> >> Let me know if you are interested in running this for yourself.
> >>
> >> I hope you'll find this useful.
> >> Ondra
> >> _______________________________________________
> >> windup-dev mailing list
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> >>
> >>
> >>
> >> --
> >> Lincoln Baxter, III
> >> http://ocpsoft.org
> >> "Simpler is better."
> >>
> >>
> >> _______________________________________________
> >> windup-dev mailing list
> >>
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> >
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140904/1fc658a4/attachment-0001.html
From lincolnbaxter at gmail.com Thu Sep 4 14:59:01 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 4 Sep 2014 14:59:01 -0400
Subject: [windup-dev] Windup 1 vs 2 comparison - automated
In-Reply-To: <CAEp_U4EMyY-uwrAef5ZNH6Crzii7yNzm+6H0RH_x=LVWP1RigQ@mail.gmail.com>
References: <5403A5C4.7030400@redhat.com>
<CAEp_U4GL9rmG_zjFUTz=GEf1UT+++e1ZCAwwV6Wkca21SEwANg@mail.gmail.com>
<54086577.1090403@redhat.com>
<7E0FB107-5D53-41E9-A9A5-C4382D76F051@redhat.com>
<CAEp_U4EMyY-uwrAef5ZNH6Crzii7yNzm+6H0RH_x=LVWP1RigQ@mail.gmail.com>
Message-ID: <CAEp_U4E+HUSRB4FpXxd9ebLfK1rPvWq-ZN91DgOOn=ze+4ZUTw@mail.gmail.com>
got it. thx.
On Thu, Sep 4, 2014 at 2:26 PM, Lincoln Baxter, III <lincolnbaxter at gmail.com
> wrote:
> What is that IP address?
>
>
> On Thu, Sep 4, 2014 at 9:17 AM, Pete Muir <pmuir at redhat.com> wrote:
>
>> Those old jboss.com internal URLs have semi-broken DNS.
>>
>> If you are on mac or ubuntu you need to put the IP in your hosts file.
>>
>> On 4 Sep 2014, at 14:13, Ondrej Zizka <ozizka at redhat.com> wrote:
>>
>> > It should be accessible, IDK why you get 404, can you see something at
>> > http://www.qa.jboss.com/~ozizka/ ?
>> >
>> > Ondra
>> >
>> > On 2.9.2014 22:37, Lincoln Baxter, III wrote:
>> >> Hmm... I am unable to view those files. 404 (I am on the VPN) Could
>> you grant public access? Thanks!
>> >>
>> >>
>> >> On Sun, Aug 31, 2014 at 6:46 PM, Ondrej Zizka <ozizka at redhat.com>
>> wrote:
>> >> Hi all,
>> >>
>> >> I've finished automation of $subj.
>> >> In terms of speed, memory, and links to the reports and logs next to
>> >> each other, in a matrix.
>> >> Check the results here:
>> >>
>> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02/Results.html
>> >> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02.zip
>> >>
>> >> There are some issues with Windup 2.x - namely, failing with exceptions
>> >> inside of rules, not reacting to multiple --packages.
>> >>
>> >> It needs a bit of setup - the test apps need to be at given relative
>> paths.
>> >> Let me know if you are interested in running this for yourself.
>> >>
>> >> I hope you'll find this useful.
>> >> Ondra
>> >> _______________________________________________
>> >> windup-dev mailing list
>> >> windup-dev at lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/windup-dev
>> >>
>> >>
>> >>
>> >> --
>> >> Lincoln Baxter, III
>> >> http://ocpsoft.org
>> >> "Simpler is better."
>> >>
>> >>
>> >> _______________________________________________
>> >> windup-dev mailing list
>> >>
>> >> windup-dev at lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/windup-dev
>> >
>> > _______________________________________________
>> > windup-dev mailing list
>> > windup-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140904/85053f12/attachment.html
From lincolnbaxter at gmail.com Thu Sep 4 14:59:07 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 4 Sep 2014 14:59:07 -0400
Subject: [windup-dev] Windup 1 vs 2 comparison - automated
In-Reply-To: <CAEp_U4E+HUSRB4FpXxd9ebLfK1rPvWq-ZN91DgOOn=ze+4ZUTw@mail.gmail.com>
References: <5403A5C4.7030400@redhat.com>
<CAEp_U4GL9rmG_zjFUTz=GEf1UT+++e1ZCAwwV6Wkca21SEwANg@mail.gmail.com>
<54086577.1090403@redhat.com>
<7E0FB107-5D53-41E9-A9A5-C4382D76F051@redhat.com>
<CAEp_U4EMyY-uwrAef5ZNH6Crzii7yNzm+6H0RH_x=LVWP1RigQ@mail.gmail.com>
<CAEp_U4E+HUSRB4FpXxd9ebLfK1rPvWq-ZN91DgOOn=ze+4ZUTw@mail.gmail.com>
Message-ID: <CAEp_U4FMACG+mGksVagKKYFM9ciDNPw88gJs=J9V3cbXFv0nDA@mail.gmail.com>
10.16.89.17
On Thu, Sep 4, 2014 at 2:59 PM, Lincoln Baxter, III <lincolnbaxter at gmail.com
> wrote:
> got it. thx.
>
>
> On Thu, Sep 4, 2014 at 2:26 PM, Lincoln Baxter, III <
> lincolnbaxter at gmail.com> wrote:
>
>> What is that IP address?
>>
>>
>> On Thu, Sep 4, 2014 at 9:17 AM, Pete Muir <pmuir at redhat.com> wrote:
>>
>>> Those old jboss.com internal URLs have semi-broken DNS.
>>>
>>> If you are on mac or ubuntu you need to put the IP in your hosts file.
>>>
>>> On 4 Sep 2014, at 14:13, Ondrej Zizka <ozizka at redhat.com> wrote:
>>>
>>> > It should be accessible, IDK why you get 404, can you see something at
>>> > http://www.qa.jboss.com/~ozizka/ ?
>>> >
>>> > Ondra
>>> >
>>> > On 2.9.2014 22:37, Lincoln Baxter, III wrote:
>>> >> Hmm... I am unable to view those files. 404 (I am on the VPN) Could
>>> you grant public access? Thanks!
>>> >>
>>> >>
>>> >> On Sun, Aug 31, 2014 at 6:46 PM, Ondrej Zizka <ozizka at redhat.com>
>>> wrote:
>>> >> Hi all,
>>> >>
>>> >> I've finished automation of $subj.
>>> >> In terms of speed, memory, and links to the reports and logs next to
>>> >> each other, in a matrix.
>>> >> Check the results here:
>>> >>
>>> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02/Results.html
>>> >> http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02.zip
>>> >>
>>> >> There are some issues with Windup 2.x - namely, failing with
>>> exceptions
>>> >> inside of rules, not reacting to multiple --packages.
>>> >>
>>> >> It needs a bit of setup - the test apps need to be at given relative
>>> paths.
>>> >> Let me know if you are interested in running this for yourself.
>>> >>
>>> >> I hope you'll find this useful.
>>> >> Ondra
>>> >> _______________________________________________
>>> >> windup-dev mailing list
>>> >> windup-dev at lists.jboss.org
>>> >> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Lincoln Baxter, III
>>> >> http://ocpsoft.org
>>> >> "Simpler is better."
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> windup-dev mailing list
>>> >>
>>> >> windup-dev at lists.jboss.org
>>> >> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> >
>>> > _______________________________________________
>>> > windup-dev mailing list
>>> > windup-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140904/b7162631/attachment.html
From ozizka at redhat.com Sat Sep 6 09:01:12 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Sat, 06 Sep 2014 15:01:12 +0200
Subject: [windup-dev] Problem with WindupConfigModel
Message-ID: <540B0598.9070003@redhat.com>
Problem with WindupConfigModel is that *currently* it needs context
initialized, since it is initialized like this:
WindupConfigurationModel config =
GraphService.getConfigurationModel(context);
And at the same time this config "DTO" needs to be passed into the
top-level API (currently WindupProcessor).
I can see 2 solutions:
A) Continue using WCM, implement WINDUP-147 GraphService.merge()
to store classes implementing the model interface
so that supports adjacent models (needed for the scan packages)
B) Have WindupConfig, and copy stuff to WCM (which is the same as A,
only done manually)
C) What I am currently doing, an ugly hack - passing final variables
into GraphLifecycleListener
Ondra
From ozizka at redhat.com Mon Sep 8 18:13:36 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 09 Sep 2014 00:13:36 +0200
Subject: [windup-dev] Asciidoc - lists
Message-ID: <540E2A10.4000704@redhat.com>
Hi Sande,
is there any way to prevent asciidoc put <p> to each <li>? Makes the
list tall and breaks the whole page layout.
Thanks,
Ondra
From sgilda at redhat.com Mon Sep 8 18:29:37 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 08 Sep 2014 18:29:37 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <540E2A10.4000704@redhat.com>
References: <540E2A10.4000704@redhat.com>
Message-ID: <540E2DD1.80203@redhat.com>
Hi Ondra,
You're asking me? ;-)
I'm totally new to asciidoc. I'll research it and see what I can find out.
Thanks,
Sande
On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
> Hi Sande,
>
> is there any way to prevent asciidoc put <p> to each <li>? Makes the
> list tall and breaks the whole page layout.
>
> Thanks,
> Ondra
From sgilda at redhat.com Mon Sep 8 19:17:00 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 08 Sep 2014 19:17:00 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <540E2DD1.80203@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com>
Message-ID: <540E38EC.9000802@redhat.com>
Hi all,
Ondra asked me about the advantages of AsciiDoc over Markdown. I really
don't know, but I do remember Pete saying AsciiDoc would be better for
the quickstart README files long ago. And I believe Drupal, the new host
for documentation, supports AsciiDoc.
TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
come up with a good reason for sticking with it, I'm fine with going
back to Markdown if it's easier for everyone.
So, AsciiDoc advocates, please speak up now.
Thanks,
Sande
On 09/08/2014 06:29 PM, Sande Gilda wrote:
> Hi Ondra,
>
> You're asking me? ;-)
>
> I'm totally new to asciidoc. I'll research it and see what I can find
> out.
>
> Thanks,
> Sande
>
> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>> Hi Sande,
>>
>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>> list tall and breaks the whole page layout.
>>
>> Thanks,
>> Ondra
>
From ozizka at redhat.com Mon Sep 8 19:58:20 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 09 Sep 2014 01:58:20 +0200
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <540E38EC.9000802@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com>
<540E38EC.9000802@redhat.com>
Message-ID: <540E429C.1080004@redhat.com>
For the record: I don't strongly prefer either, only that I only touched
few things in AsciiDoc, and:
1) certain constructs are quite less readable -> editable in the
source text (e.g. links)
2) the render results are not satisfactory - things like a bold text
in a lists are not properly implemented on whatever GitHub uses.
Ondra
On 9.9.2014 01:17, Sande Gilda wrote:
> Hi all,
>
> Ondra asked me about the advantages of AsciiDoc over Markdown. I
> really don't know, but I do remember Pete saying AsciiDoc would be
> better for the quickstart README files long ago. And I believe Drupal,
> the new host for documentation, supports AsciiDoc.
>
> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
> come up with a good reason for sticking with it, I'm fine with going
> back to Markdown if it's easier for everyone.
>
> So, AsciiDoc advocates, please speak up now.
>
> Thanks,
> Sande
>
> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>> Hi Ondra,
>>
>> You're asking me? ;-)
>>
>> I'm totally new to asciidoc. I'll research it and see what I can find
>> out.
>>
>> Thanks,
>> Sande
>>
>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>> Hi Sande,
>>>
>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>> list tall and breaks the whole page layout.
>>>
>>> Thanks,
>>> Ondra
>>
>
From bdavis at redhat.com Mon Sep 8 20:12:53 2014
From: bdavis at redhat.com (Brad Davis)
Date: Mon, 8 Sep 2014 20:12:53 -0400 (EDT)
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <540E429C.1080004@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com>
<540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com>
Message-ID: <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com>
I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
Brad Davis
Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka at redhat.com>
To: "Sande Gilda" <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Monday, September 8, 2014 7:58:20 PM
Subject: Re: [windup-dev] Asciidoc - lists
For the record: I don't strongly prefer either, only that I only touched
few things in AsciiDoc, and:
1) certain constructs are quite less readable -> editable in the
source text (e.g. links)
2) the render results are not satisfactory - things like a bold text
in a lists are not properly implemented on whatever GitHub uses.
Ondra
On 9.9.2014 01:17, Sande Gilda wrote:
> Hi all,
>
> Ondra asked me about the advantages of AsciiDoc over Markdown. I
> really don't know, but I do remember Pete saying AsciiDoc would be
> better for the quickstart README files long ago. And I believe Drupal,
> the new host for documentation, supports AsciiDoc.
>
> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
> come up with a good reason for sticking with it, I'm fine with going
> back to Markdown if it's easier for everyone.
>
> So, AsciiDoc advocates, please speak up now.
>
> Thanks,
> Sande
>
> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>> Hi Ondra,
>>
>> You're asking me? ;-)
>>
>> I'm totally new to asciidoc. I'll research it and see what I can find
>> out.
>>
>> Thanks,
>> Sande
>>
>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>> Hi Sande,
>>>
>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>> list tall and breaks the whole page layout.
>>>
>>> Thanks,
>>> Ondra
>>
>
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
From sgilda at redhat.com Mon Sep 8 20:23:43 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 08 Sep 2014 20:23:43 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com>
<540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com>
<216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com>
Message-ID: <540E488F.90105@redhat.com>
I'll change everything back to Markdown later this week. Ondra, in the
meantime, you can work in Markdown.
On 09/08/2014 08:12 PM, Brad Davis wrote:
> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Ondrej Zizka" <ozizka at redhat.com>
> To: "Sande Gilda" <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Monday, September 8, 2014 7:58:20 PM
> Subject: Re: [windup-dev] Asciidoc - lists
>
> For the record: I don't strongly prefer either, only that I only touched
> few things in AsciiDoc, and:
> 1) certain constructs are quite less readable -> editable in the
> source text (e.g. links)
> 2) the render results are not satisfactory - things like a bold text
> in a lists are not properly implemented on whatever GitHub uses.
>
> Ondra
>
>
> On 9.9.2014 01:17, Sande Gilda wrote:
>> Hi all,
>>
>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>> really don't know, but I do remember Pete saying AsciiDoc would be
>> better for the quickstart README files long ago. And I believe Drupal,
>> the new host for documentation, supports AsciiDoc.
>>
>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>> come up with a good reason for sticking with it, I'm fine with going
>> back to Markdown if it's easier for everyone.
>>
>> So, AsciiDoc advocates, please speak up now.
>>
>> Thanks,
>> Sande
>>
>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>> Hi Ondra,
>>>
>>> You're asking me? ;-)
>>>
>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>> out.
>>>
>>> Thanks,
>>> Sande
>>>
>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>> Hi Sande,
>>>>
>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>> list tall and breaks the whole page layout.
>>>>
>>>> Thanks,
>>>> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Tue Sep 9 03:08:44 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 09 Sep 2014 09:08:44 +0200
Subject: [windup-dev] CDI question - producer
Message-ID: <540EA77C.7010303@redhat.com>
Hi, with this
----------------------------------------------------------------
@Singleton
public class GraphContextFactoryImpl implements GraphContextFactory
{
@Inject
private GraphApiCompositeClassLoaderProvider
graphApiCompositeClassLoaderProvider;
@Inject
private Imported<Service<? extends VertexFrame>> graphServices;
@Inject
private GraphTypeRegistry graphTypeRegistry;
private GraphContext graphContext;
----------------------------------------------------------------
is there a difference between the following two?
Basically I just moved the core of the creation.
A is master, B is my branch, results in the GraphContext being created
at each @Inject.
I think I am missing something here.
Thanks, Ondra
---A-------------------------------------------------------------
@Override
public GraphContext create(){
return produceGraphContext();
}
@Produces @ApplicationScoped
public GraphContext produceGraphContext(){
if (this.graphContext == null){
this.graphContext = new GraphContextImpl(graphServices,
this.graphTypeRegistry, this.graphApiCompositeClassLoaderProvider);
}
return graphContext;
}
----B-----------------------------------------------------------
@Override
public GraphContext create() {
return new GraphContextImpl(
this.graphServices,
this.graphTypeRegistry,
this.graphApiCompositeClassLoaderProvider);
}
@Produces @ApplicationScoped
public GraphContext produceGraphContext(){
if (this.graphContext == null) {
this.graphContext = this.create();
}
return graphContext;
}
From pmuir at redhat.com Tue Sep 9 06:39:26 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 9 Sep 2014 11:39:26 +0100
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <540E488F.90105@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com>
<540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com>
<216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com>
<540E488F.90105@redhat.com>
Message-ID: <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
The big advantages of asciidoc are:
* more comprehensive markup (e.g. tables, definition lists are supported as standard)
* generation of pdf and epub is part of the standard toolchain
Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
I prefer asciidoc links as you just do link:http://redhat.com[Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
On 9 Sep 2014, at 01:23, Sande Gilda <sgilda at redhat.com> wrote:
> I'll change everything back to Markdown later this week. Ondra, in the
> meantime, you can work in Markdown.
>
> On 09/08/2014 08:12 PM, Brad Davis wrote:
>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>
>> Brad Davis
>> Red Hat Consulting
>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>
>>
>> ----- Original Message -----
>> From: "Ondrej Zizka" <ozizka at redhat.com>
>> To: "Sande Gilda" <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
>> Sent: Monday, September 8, 2014 7:58:20 PM
>> Subject: Re: [windup-dev] Asciidoc - lists
>>
>> For the record: I don't strongly prefer either, only that I only touched
>> few things in AsciiDoc, and:
>> 1) certain constructs are quite less readable -> editable in the
>> source text (e.g. links)
>> 2) the render results are not satisfactory - things like a bold text
>> in a lists are not properly implemented on whatever GitHub uses.
>>
>> Ondra
>>
>>
>> On 9.9.2014 01:17, Sande Gilda wrote:
>>> Hi all,
>>>
>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>> better for the quickstart README files long ago. And I believe Drupal,
>>> the new host for documentation, supports AsciiDoc.
>>>
>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>> come up with a good reason for sticking with it, I'm fine with going
>>> back to Markdown if it's easier for everyone.
>>>
>>> So, AsciiDoc advocates, please speak up now.
>>>
>>> Thanks,
>>> Sande
>>>
>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>> Hi Ondra,
>>>>
>>>> You're asking me? ;-)
>>>>
>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>> out.
>>>>
>>>> Thanks,
>>>> Sande
>>>>
>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>> Hi Sande,
>>>>>
>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>> list tall and breaks the whole page layout.
>>>>>
>>>>> Thanks,
>>>>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From sgilda at redhat.com Tue Sep 9 07:45:11 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 09 Sep 2014 07:45:11 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
References: <540E2A10.4000704@redhat.com>
<540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com>
<540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com>
<C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
Message-ID: <540EE847.9010507@redhat.com>
One of Ondra's complaints is the way lists seem to display an extra
paragraph between the items. Take a look at the home page here:
https://github.com/windup/windup/wiki
Note that the list items are spaced far apart. I search for a solution,
and the only thing I could find was mention of using
|[options="compact"], |but it didn't seem to work.
Ondra, what other issues did you have.
On 09/09/2014 06:39 AM, Pete Muir wrote:
> The big advantages of asciidoc are:
>
> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
> * generation of pdf and epub is part of the standard toolchain
>
> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>
> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>
> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
>
> On 9 Sep 2014, at 01:23, Sande Gilda <sgilda at redhat.com> wrote:
>
>> I'll change everything back to Markdown later this week. Ondra, in the
>> meantime, you can work in Markdown.
>>
>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>
>>> Brad Davis
>>> Red Hat Consulting
>>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>>
>>>
>>> ----- Original Message -----
>>> From: "Ondrej Zizka" <ozizka at redhat.com>
>>> To: "Sande Gilda" <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>
>>> For the record: I don't strongly prefer either, only that I only touched
>>> few things in AsciiDoc, and:
>>> 1) certain constructs are quite less readable -> editable in the
>>> source text (e.g. links)
>>> 2) the render results are not satisfactory - things like a bold text
>>> in a lists are not properly implemented on whatever GitHub uses.
>>>
>>> Ondra
>>>
>>>
>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>> Hi all,
>>>>
>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>> the new host for documentation, supports AsciiDoc.
>>>>
>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>> come up with a good reason for sticking with it, I'm fine with going
>>>> back to Markdown if it's easier for everyone.
>>>>
>>>> So, AsciiDoc advocates, please speak up now.
>>>>
>>>> Thanks,
>>>> Sande
>>>>
>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>> Hi Ondra,
>>>>>
>>>>> You're asking me? ;-)
>>>>>
>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>> out.
>>>>>
>>>>> Thanks,
>>>>> Sande
>>>>>
>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>> Hi Sande,
>>>>>>
>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>> list tall and breaks the whole page layout.
>>>>>>
>>>>>> Thanks,
>>>>>> Ondra
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140909/cd72c492/attachment.html
From pmuir at redhat.com Tue Sep 9 10:18:12 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 9 Sep 2014 15:18:12 +0100
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <540EE847.9010507@redhat.com>
References: <540E2A10.4000704@redhat.com>
<540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com>
<540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com>
<C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
<540EE847.9010507@redhat.com>
Message-ID: <4DC1CB18-29DF-4238-849A-0B8F706ADAB8@redhat.com>
I took a look at this, and it looks like a problem with the github css for the output. I think you could file a bug with them about it.
I guess a good question here is whether the wiki is just for editing, OR if it?s actually how we will present this stuff?
On 9 Sep 2014, at 12:45, Sande Gilda <sgilda at redhat.com> wrote:
> One of Ondra's complaints is the way lists seem to display an extra paragraph between the items. Take a look at the home page here: https://github.com/windup/windup/wiki
>
> Note that the list items are spaced far apart. I search for a solution, and the only thing I could find was mention of using [options="compact"], but it didn't seem to work.
>
> Ondra, what other issues did you have.
>
>
> On 09/09/2014 06:39 AM, Pete Muir wrote:
>> The big advantages of asciidoc are:
>>
>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>> * generation of pdf and epub is part of the standard toolchain
>>
>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>
>> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>
>> I prefer asciidoc links as you just do link:
>> http://redhat.com
>> [Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
>>
>> On 9 Sep 2014, at 01:23, Sande Gilda
>> <sgilda at redhat.com>
>> wrote:
>>
>>
>>> I'll change everything back to Markdown later this week. Ondra, in the
>>> meantime, you can work in Markdown.
>>>
>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>
>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>
>>>> Brad Davis
>>>> Red Hat Consulting
>>>> Email:
>>>> bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>>>
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Ondrej Zizka"
>>>> <ozizka at redhat.com>
>>>>
>>>> To: "Sande Gilda"
>>>> <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
>>>>
>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>
>>>> For the record: I don't strongly prefer either, only that I only touched
>>>> few things in AsciiDoc, and:
>>>> 1) certain constructs are quite less readable -> editable in the
>>>> source text (e.g. links)
>>>> 2) the render results are not satisfactory - things like a bold text
>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>
>>>> Ondra
>>>>
>>>>
>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>> the new host for documentation, supports AsciiDoc.
>>>>>
>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>> back to Markdown if it's easier for everyone.
>>>>>
>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>
>>>>> Thanks,
>>>>> Sande
>>>>>
>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>
>>>>>> Hi Ondra,
>>>>>>
>>>>>> You're asking me? ;-)
>>>>>>
>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>> out.
>>>>>>
>>>>>> Thanks,
>>>>>> Sande
>>>>>>
>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>
>>>>>>> Hi Sande,
>>>>>>>
>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>> list tall and breaks the whole page layout.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Ondra
>>>>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>>
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>>
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>>
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From sgilda at redhat.com Tue Sep 9 10:32:54 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 09 Sep 2014 10:32:54 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <4DC1CB18-29DF-4238-849A-0B8F706ADAB8@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com> <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com> <540EE847.9010507@redhat.com>
<4DC1CB18-29DF-4238-849A-0B8F706ADAB8@redhat.com>
Message-ID: <540F0F96.6000802@redhat.com>
On 09/09/2014 10:18 AM, Pete Muir wrote:
> I took a look at this, and it looks like a problem with the github css for the output. I think you could file a bug with them about it.
I'll file a bug for this.
>
> I guess a good question here is whether the wiki is just for editing, OR if it?s actually how we will present this stuff?
I had originally thought I could reuse the pages to suck the content
into Drupal, but I now that's unrealistic. At this point I think the
best approach is the one that is the easiest and the least burden for
whoever is using it. Ondra produces the most doc, so I'm happy to switch
back to his preference for Markdown. In the event that we need to go to
AsciiDoc at any point, there are tools that make the conversion very easy.
>
> On 9 Sep 2014, at 12:45, Sande Gilda <sgilda at redhat.com> wrote:
>
>> One of Ondra's complaints is the way lists seem to display an extra paragraph between the items. Take a look at the home page here: https://github.com/windup/windup/wiki
>>
>> Note that the list items are spaced far apart. I search for a solution, and the only thing I could find was mention of using [options="compact"], but it didn't seem to work.
>>
>> Ondra, what other issues did you have.
>>
>>
>> On 09/09/2014 06:39 AM, Pete Muir wrote:
>>> The big advantages of asciidoc are:
>>>
>>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>>> * generation of pdf and epub is part of the standard toolchain
>>>
>>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>>
>>> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>>
>>> I prefer asciidoc links as you just do link:
>>> http://redhat.com
>>> [Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
>>>
>>> On 9 Sep 2014, at 01:23, Sande Gilda
>>> <sgilda at redhat.com>
>>> wrote:
>>>
>>>
>>>> I'll change everything back to Markdown later this week. Ondra, in the
>>>> meantime, you can work in Markdown.
>>>>
>>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>>
>>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>>
>>>>> Brad Davis
>>>>> Red Hat Consulting
>>>>> Email:
>>>>> bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>>>>
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Ondrej Zizka"
>>>>> <ozizka at redhat.com>
>>>>>
>>>>> To: "Sande Gilda"
>>>>> <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
>>>>>
>>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>>
>>>>> For the record: I don't strongly prefer either, only that I only touched
>>>>> few things in AsciiDoc, and:
>>>>> 1) certain constructs are quite less readable -> editable in the
>>>>> source text (e.g. links)
>>>>> 2) the render results are not satisfactory - things like a bold text
>>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>>
>>>>> Ondra
>>>>>
>>>>>
>>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>>> the new host for documentation, supports AsciiDoc.
>>>>>>
>>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>>> back to Markdown if it's easier for everyone.
>>>>>>
>>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>>
>>>>>> Thanks,
>>>>>> Sande
>>>>>>
>>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>>
>>>>>>> Hi Ondra,
>>>>>>>
>>>>>>> You're asking me? ;-)
>>>>>>>
>>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>>> out.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sande
>>>>>>>
>>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>>
>>>>>>>> Hi Sande,
>>>>>>>>
>>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>>> list tall and breaks the whole page layout.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Ondra
>>>>>>>>
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>>
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>>
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>>
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From sgilda at redhat.com Tue Sep 9 11:32:59 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 09 Sep 2014 11:32:59 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <4DC1CB18-29DF-4238-849A-0B8F706ADAB8@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com> <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com> <540EE847.9010507@redhat.com>
<4DC1CB18-29DF-4238-849A-0B8F706ADAB8@redhat.com>
Message-ID: <540F1DAB.1000102@redhat.com>
Ondra, it looks like Markdown has the same problem rendering lists.
See:
https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.4.x-develop/README.md#introduction
On 09/09/2014 10:18 AM, Pete Muir wrote:
> I took a look at this, and it looks like a problem with the github css for the output. I think you could file a bug with them about it.
>
> I guess a good question here is whether the wiki is just for editing, OR if it?s actually how we will present this stuff?
>
> On 9 Sep 2014, at 12:45, Sande Gilda <sgilda at redhat.com> wrote:
>
>> One of Ondra's complaints is the way lists seem to display an extra paragraph between the items. Take a look at the home page here: https://github.com/windup/windup/wiki
>>
>> Note that the list items are spaced far apart. I search for a solution, and the only thing I could find was mention of using [options="compact"], but it didn't seem to work.
>>
>> Ondra, what other issues did you have.
>>
>>
>> On 09/09/2014 06:39 AM, Pete Muir wrote:
>>> The big advantages of asciidoc are:
>>>
>>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>>> * generation of pdf and epub is part of the standard toolchain
>>>
>>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>>
>>> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>>
>>> I prefer asciidoc links as you just do link:
>>> http://redhat.com
>>> [Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
>>>
>>> On 9 Sep 2014, at 01:23, Sande Gilda
>>> <sgilda at redhat.com>
>>> wrote:
>>>
>>>
>>>> I'll change everything back to Markdown later this week. Ondra, in the
>>>> meantime, you can work in Markdown.
>>>>
>>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>>
>>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>>
>>>>> Brad Davis
>>>>> Red Hat Consulting
>>>>> Email:
>>>>> bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>>>>
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Ondrej Zizka"
>>>>> <ozizka at redhat.com>
>>>>>
>>>>> To: "Sande Gilda"
>>>>> <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
>>>>>
>>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>>
>>>>> For the record: I don't strongly prefer either, only that I only touched
>>>>> few things in AsciiDoc, and:
>>>>> 1) certain constructs are quite less readable -> editable in the
>>>>> source text (e.g. links)
>>>>> 2) the render results are not satisfactory - things like a bold text
>>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>>
>>>>> Ondra
>>>>>
>>>>>
>>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>>> the new host for documentation, supports AsciiDoc.
>>>>>>
>>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>>> back to Markdown if it's easier for everyone.
>>>>>>
>>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>>
>>>>>> Thanks,
>>>>>> Sande
>>>>>>
>>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>>
>>>>>>> Hi Ondra,
>>>>>>>
>>>>>>> You're asking me? ;-)
>>>>>>>
>>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>>> out.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sande
>>>>>>>
>>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>>
>>>>>>>> Hi Sande,
>>>>>>>>
>>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>>> list tall and breaks the whole page layout.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Ondra
>>>>>>>>
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>>
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>>
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>>
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From pmuir at redhat.com Tue Sep 9 10:53:45 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 9 Sep 2014 15:53:45 +0100
Subject: [windup-dev] CDI question - producer
In-Reply-To: <540EA77C.7010303@redhat.com>
References: <540EA77C.7010303@redhat.com>
Message-ID: <31274351-9F80-4B18-BC32-5084B8F4A26B@redhat.com>
There shouldn?t be any difference, but there is no need to to have @ApplicationScoped on both the producer method and the managed bean you declare it on, and do lazy init. Putting it on the producer method means CDI will cache it. Putting it on the declaring bean means the same bean will be called each time to execute the method. With the code you show, the simplest thing is to just put @Produces @ApplicationScoped on the create() method.
As a side note, you probably want to use @ApplicationScoped not @Singleton.
On 9 Sep 2014, at 08:08, Ondrej Zizka <ozizka at redhat.com> wrote:
> Hi, with this
>
> ----------------------------------------------------------------
> @Singleton
> public class GraphContextFactoryImpl implements GraphContextFactory
> {
> @Inject
> private GraphApiCompositeClassLoaderProvider graphApiCompositeClassLoaderProvider;
>
> @Inject
> private Imported<Service<? extends VertexFrame>> graphServices;
>
> @Inject
> private GraphTypeRegistry graphTypeRegistry;
>
> private GraphContext graphContext;
> ----------------------------------------------------------------
>
>
> is there a difference between the following two?
> Basically I just moved the core of the creation.
> A is master, B is my branch, results in the GraphContext being created at each @Inject.
> I think I am missing something here.
>
> Thanks, Ondra
>
>
> ---A-------------------------------------------------------------
> @Override
> public GraphContext create(){
> return produceGraphContext();
> }
>
> @Produces @ApplicationScoped
> public GraphContext produceGraphContext(){
> if (this.graphContext == null){
> this.graphContext = new GraphContextImpl(graphServices, this.graphTypeRegistry, this.graphApiCompositeClassLoaderProvider);
> }
> return graphContext;
> }
>
> ----B-----------------------------------------------------------
>
> @Override
> public GraphContext create() {
> return new GraphContextImpl(
> this.graphServices,
> this.graphTypeRegistry,
> this.graphApiCompositeClassLoaderProvider);
> }
>
> @Produces @ApplicationScoped
> public GraphContext produceGraphContext(){
> if (this.graphContext == null) {
> this.graphContext = this.create();
> }
> return graphContext;
> }
>
From ozizka at redhat.com Tue Sep 9 18:19:33 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 10 Sep 2014 00:19:33 +0200
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
References: <540E2A10.4000704@redhat.com>
<540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com>
<540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com>
<C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
Message-ID: <540F7CF5.1060406@redhat.com>
On 9.9.2014 12:39, Pete Muir wrote:
> The big advantages of asciidoc are:
>
> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
That's nice, but we have 0 tables and just one DL in our docs :)
> * generation of pdf and epub is part of the standard toolchain
>
> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
Same as above - will we have more complex docs?
Will we produce PDF? Will users expect a PDF document? I don't know
their customs, but personally I never use PDF docs, except when
printing, which I never did for anything except Java EE specs /
tutorials and Spring.
How about keeping MarkDown for short and simple pages, and AsciiDoc
optionally when needed? One more syntax should not matter.
> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>
> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
How about this nice paragraph
A
link:https://maps.google.com/maps?saddr=Hn%C4%9Bvkovsk%C3%A9ho%2FRoute+41&daddr=Kr%C3%B3lewska&hl=en&ie=UTF8&sll=52.229692,21.006203&sspn=0.214911,0.385551&geocode=FW5S7gId0qf9AA%3BFYYeHQMdx6BAAQ&t=h&mra=mift&mrsp=1&sz=12&z=12[way]
to
link:https://www.google.cz/search?q=poland&client=ubuntu&hs=1q&channel=fs&source=lnms&tbm=isch&sa=X&ei=MHwPVM_jLs7EPJfCgbgL&ved=0CAkQ_AUoAg&biw=1504&bih=1083[Poland].
And now compare with:
A
"way":https://maps.google.com/maps?saddr=Hn%C4%9Bvkovsk%C3%A9ho%2FRoute+41&daddr=Kr%C3%B3lewska&hl=en&ie=UTF8&sll=52.229692,21.006203&sspn=0.214911,0.385551&geocode=FW5S7gId0qf9AA%3BFYYeHQMdx6BAAQ&t=h&mra=mift&mrsp=1&sz=12&z=12
to
"Poland":https://www.google.cz/search?q=poland&client=ubuntu&hs=1q&channel=fs&source=lnms&tbm=isch&sa=X&ei=MHwPVM_jLs7EPJfCgbgL&ved=0CAkQ_AUoAg&biw=1504&bih=1083
I personally prefer the first. And the {} attributes syntax doesn't make
things simpler.
my2c.
But as I said - except for this and few other things, AsciiDoc may be
better, potentially.
Ondra
> On 9 Sep 2014, at 01:23, Sande Gilda <sgilda at redhat.com> wrote:
>
>> I'll change everything back to Markdown later this week. Ondra, in the
>> meantime, you can work in Markdown.
>>
>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>
>>> Brad Davis
>>> Red Hat Consulting
>>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>>
>>>
>>> ----- Original Message -----
>>> From: "Ondrej Zizka" <ozizka at redhat.com>
>>> To: "Sande Gilda" <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>
>>> For the record: I don't strongly prefer either, only that I only touched
>>> few things in AsciiDoc, and:
>>> 1) certain constructs are quite less readable -> editable in the
>>> source text (e.g. links)
>>> 2) the render results are not satisfactory - things like a bold text
>>> in a lists are not properly implemented on whatever GitHub uses.
>>>
>>> Ondra
>>>
>>>
>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>> Hi all,
>>>>
>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>> the new host for documentation, supports AsciiDoc.
>>>>
>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>> come up with a good reason for sticking with it, I'm fine with going
>>>> back to Markdown if it's easier for everyone.
>>>>
>>>> So, AsciiDoc advocates, please speak up now.
>>>>
>>>> Thanks,
>>>> Sande
>>>>
>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>> Hi Ondra,
>>>>>
>>>>> You're asking me? ;-)
>>>>>
>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>> out.
>>>>>
>>>>> Thanks,
>>>>> Sande
>>>>>
>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>> Hi Sande,
>>>>>>
>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>> list tall and breaks the whole page layout.
>>>>>>
>>>>>> Thanks,
>>>>>> Ondra
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Tue Sep 9 18:24:46 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 10 Sep 2014 00:24:46 +0200
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <540EE847.9010507@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com> <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
<540EE847.9010507@redhat.com>
Message-ID: <540F7E2E.30504@redhat.com>
Other issues might be GitHub's translator. But IDK what's the main
target medium for our docs. Is that GitHub wiki?
Ondra
On 9.9.2014 13:45, Sande Gilda wrote:
> One of Ondra's complaints is the way lists seem to display an extra
> paragraph between the items. Take a look at the home page here:
> https://github.com/windup/windup/wiki
>
> Note that the list items are spaced far apart. I search for a
> solution, and the only thing I could find was mention of using
> |[options="compact"], |but it didn't seem to work.
>
> Ondra, what other issues did you have.
>
>
> On 09/09/2014 06:39 AM, Pete Muir wrote:
>> The big advantages of asciidoc are:
>>
>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>> * generation of pdf and epub is part of the standard toolchain
>>
>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>
>> GitHub's support for asciidoc wasn't great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>
>> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat's website]. I find this much easier to remember than the weird []() syntax in markdown.
>>
>> On 9 Sep 2014, at 01:23, Sande Gilda<sgilda at redhat.com> wrote:
>>
>>> I'll change everything back to Markdown later this week. Ondra, in the
>>> meantime, you can work in Markdown.
>>>
>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>
>>>> Brad Davis
>>>> Red Hat Consulting
>>>> Email:bdavis at redhat.com | c: 980.226.7865 |http://www.redhat.com
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Ondrej Zizka"<ozizka at redhat.com>
>>>> To: "Sande Gilda"<sgilda at redhat.com>, "Windup-dev List"<windup-dev at lists.jboss.org>
>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>
>>>> For the record: I don't strongly prefer either, only that I only touched
>>>> few things in AsciiDoc, and:
>>>> 1) certain constructs are quite less readable -> editable in the
>>>> source text (e.g. links)
>>>> 2) the render results are not satisfactory - things like a bold text
>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>
>>>> Ondra
>>>>
>>>>
>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>> Hi all,
>>>>>
>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>> the new host for documentation, supports AsciiDoc.
>>>>>
>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>> back to Markdown if it's easier for everyone.
>>>>>
>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>
>>>>> Thanks,
>>>>> Sande
>>>>>
>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>> Hi Ondra,
>>>>>>
>>>>>> You're asking me? ;-)
>>>>>>
>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>> out.
>>>>>>
>>>>>> Thanks,
>>>>>> Sande
>>>>>>
>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>> Hi Sande,
>>>>>>>
>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>> list tall and breaks the whole page layout.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Ondra
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140910/d6771a64/attachment-0001.html
From ozizka at redhat.com Tue Sep 9 18:26:45 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 10 Sep 2014 00:26:45 +0200
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <540F1DAB.1000102@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com> <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com> <540EE847.9010507@redhat.com> <4DC1CB18-29DF-4238-849A-0B8F706ADAB8@redhat.com>
<540F1DAB.1000102@redhat.com>
Message-ID: <540F7EA5.1050602@redhat.com>
That's because there are two \n's. AsciiDoc does that even with
* foo
* bar
Ondra
On 9.9.2014 17:32, Sande Gilda wrote:
> Ondra, it looks like Markdown has the same problem rendering lists.
>
> See:
> https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.4.x-develop/README.md#introduction
>
> On 09/09/2014 10:18 AM, Pete Muir wrote:
>> I took a look at this, and it looks like a problem with the github css for the output. I think you could file a bug with them about it.
>>
>> I guess a good question here is whether the wiki is just for editing, OR if it?s actually how we will present this stuff?
>>
>> On 9 Sep 2014, at 12:45, Sande Gilda <sgilda at redhat.com> wrote:
>>
>>> One of Ondra's complaints is the way lists seem to display an extra paragraph between the items. Take a look at the home page here: https://github.com/windup/windup/wiki
>>>
>>> Note that the list items are spaced far apart. I search for a solution, and the only thing I could find was mention of using [options="compact"], but it didn't seem to work.
>>>
>>> Ondra, what other issues did you have.
>>>
>>>
>>> On 09/09/2014 06:39 AM, Pete Muir wrote:
>>>> The big advantages of asciidoc are:
>>>>
>>>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>>>> * generation of pdf and epub is part of the standard toolchain
>>>>
>>>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>>>
>>>> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>>>
>>>> I prefer asciidoc links as you just do link:
>>>> http://redhat.com
>>>> [Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
>>>>
>>>> On 9 Sep 2014, at 01:23, Sande Gilda
>>>> <sgilda at redhat.com>
>>>> wrote:
>>>>
>>>>
>>>>> I'll change everything back to Markdown later this week. Ondra, in the
>>>>> meantime, you can work in Markdown.
>>>>>
>>>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>>>
>>>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>>>
>>>>>> Brad Davis
>>>>>> Red Hat Consulting
>>>>>> Email:
>>>>>> bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> ----- Original Message -----
>>>>>> From: "Ondrej Zizka"
>>>>>> <ozizka at redhat.com>
>>>>>>
>>>>>> To: "Sande Gilda"
>>>>>> <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
>>>>>>
>>>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>>>
>>>>>> For the record: I don't strongly prefer either, only that I only touched
>>>>>> few things in AsciiDoc, and:
>>>>>> 1) certain constructs are quite less readable -> editable in the
>>>>>> source text (e.g. links)
>>>>>> 2) the render results are not satisfactory - things like a bold text
>>>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>>>
>>>>>> Ondra
>>>>>>
>>>>>>
>>>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>>>> the new host for documentation, supports AsciiDoc.
>>>>>>>
>>>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>>>> back to Markdown if it's easier for everyone.
>>>>>>>
>>>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sande
>>>>>>>
>>>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>>>
>>>>>>>> Hi Ondra,
>>>>>>>>
>>>>>>>> You're asking me? ;-)
>>>>>>>>
>>>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>>>> out.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sande
>>>>>>>>
>>>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>>>
>>>>>>>>> Hi Sande,
>>>>>>>>>
>>>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>>>> list tall and breaks the whole page layout.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Ondra
>>>>>>>>>
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>>
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>>
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>>
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Tue Sep 9 18:29:32 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 10 Sep 2014 00:29:32 +0200
Subject: [windup-dev] CDI question - producer
In-Reply-To: <540EA77C.7010303@redhat.com>
References: <540EA77C.7010303@redhat.com>
Message-ID: <540F7F4C.8090909@redhat.com>
For the record:
There are few noticable things.
GraphContextImpl should be @Vetoed
So far it worked because it has no default constructor.
The test failure I was after was also in master.
But still the GraphContext is being initialized (!= constructed) on and on.
Rebasing & checking what's going on.
Ondra
On 9.9.2014 09:08, Ondrej Zizka wrote:
> Hi, with this
>
> ----------------------------------------------------------------
> @Singleton
> public class GraphContextFactoryImpl implements GraphContextFactory
> {
> @Inject
> private GraphApiCompositeClassLoaderProvider
> graphApiCompositeClassLoaderProvider;
>
> @Inject
> private Imported<Service<? extends VertexFrame>> graphServices;
>
> @Inject
> private GraphTypeRegistry graphTypeRegistry;
>
> private GraphContext graphContext;
> ----------------------------------------------------------------
>
>
> is there a difference between the following two?
> Basically I just moved the core of the creation.
> A is master, B is my branch, results in the GraphContext being created
> at each @Inject.
> I think I am missing something here.
>
> Thanks, Ondra
>
>
> ---A-------------------------------------------------------------
> @Override
> public GraphContext create(){
> return produceGraphContext();
> }
>
> @Produces @ApplicationScoped
> public GraphContext produceGraphContext(){
> if (this.graphContext == null){
> this.graphContext = new GraphContextImpl(graphServices,
> this.graphTypeRegistry, this.graphApiCompositeClassLoaderProvider);
> }
> return graphContext;
> }
>
> ----B-----------------------------------------------------------
>
> @Override
> public GraphContext create() {
> return new GraphContextImpl(
> this.graphServices,
> this.graphTypeRegistry,
> this.graphApiCompositeClassLoaderProvider);
> }
>
> @Produces @ApplicationScoped
> public GraphContext produceGraphContext(){
> if (this.graphContext == null) {
> this.graphContext = this.create();
> }
> return graphContext;
> }
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Tue Sep 9 22:24:29 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 10 Sep 2014 04:24:29 +0200
Subject: [windup-dev] Double building?
Message-ID: <540FB65D.7070704@redhat.com>
Hi (Lincoln),
could you please describe the issue with forge resolver more closely?
I think I was hit by that few times - the app is behaving differently
when I build only one module, then run test with other, and in whole run.
What's the cause and what exactly does it cause - what should I count with?
On unrelated note - I changed few things, rebuilt few times, and now
instead of
HintsClassificationsTest.testIterationVariableResolving:162
expected:<3> but was:<0>
I have
HintsClassificationsTest.testIterationVariableResolving:162
expected:<3> but was:<4>
Which is good - the whole run sticks with the same graph :)
But a bit weirder - having more nodes than the test expects...
More tomorrow.
Ondra
From pmuir at redhat.com Wed Sep 10 06:12:17 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 10 Sep 2014 11:12:17 +0100
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <540F7CF5.1060406@redhat.com>
References: <540E2A10.4000704@redhat.com>
<540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com>
<540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com>
<C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
<540F7CF5.1060406@redhat.com>
Message-ID: <805D1899-2BD9-4A52-909D-BB07779CD85A@redhat.com>
On 9 Sep 2014, at 23:19, Ondrej Zizka <ozizka at redhat.com> wrote:
>
> On 9.9.2014 12:39, Pete Muir wrote:
>> The big advantages of asciidoc are:
>>
>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
> That's nice, but we have 0 tables and just one DL in our docs :)
Understood, this is largely about what you need out of your language. For me tables are essential, as are admonitions and callouts.
>> * generation of pdf and epub is part of the standard toolchain
>>
>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
> Same as above - will we have more complex docs?
I think it?s very likely that we will have what I would class a ?complex? document for Windup - yes.
> Will we produce PDF? Will users expect a PDF document?
It?s a very commonly requested item. A sizeable majority tend to prefer this.
> I don't know
> their customs, but personally I never use PDF docs, except when
> printing, which I never did for anything except Java EE specs /
> tutorials and Spring.
>
> How about keeping MarkDown for short and simple pages, and AsciiDoc
> optionally when needed? One more syntax should not matter.
I would use asciidoc for anything that is going to go in to the docs. For other things, such as READMEs use markdown.
>> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>
>> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
> How about this nice paragraph
>
> A
> link:https://maps.google.com/maps?saddr=Hn%C4%9Bvkovsk%C3%A9ho%2FRoute+41&daddr=Kr%C3%B3lewska&hl=en&ie=UTF8&sll=52.229692,21.006203&sspn=0.214911,0.385551&geocode=FW5S7gId0qf9AA%3BFYYeHQMdx6BAAQ&t=h&mra=mift&mrsp=1&sz=12&z=12[way]
> to
> link:https://www.google.cz/search?q=poland&client=ubuntu&hs=1q&channel=fs&source=lnms&tbm=isch&sa=X&ei=MHwPVM_jLs7EPJfCgbgL&ved=0CAkQ_AUoAg&biw=1504&bih=1083[Poland].
>
> And now compare with:
>
> A
> "way":https://maps.google.com/maps?saddr=Hn%C4%9Bvkovsk%C3%A9ho%2FRoute+41&daddr=Kr%C3%B3lewska&hl=en&ie=UTF8&sll=52.229692,21.006203&sspn=0.214911,0.385551&geocode=FW5S7gId0qf9AA%3BFYYeHQMdx6BAAQ&t=h&mra=mift&mrsp=1&sz=12&z=12
> to
> "Poland":https://www.google.cz/search?q=poland&client=ubuntu&hs=1q&channel=fs&source=lnms&tbm=isch&sa=X&ei=MHwPVM_jLs7EPJfCgbgL&ved=0CAkQ_AUoAg&biw=1504&bih=1083
>
> I personally prefer the first. And the {} attributes syntax doesn't make
> things simpler.
I prefer the first approach too. So a good argument for AsciiDoc then.
Note that the markdown syntax you quote is a github extension I think. This is part of the reason I would pick AsciiDoc - all these things are standard, rather than implementation specific extensions.
>
> my2c.
> But as I said - except for this and few other things, AsciiDoc may be
> better, potentially.
>
> Ondra
>
>> On 9 Sep 2014, at 01:23, Sande Gilda <sgilda at redhat.com> wrote:
>>
>>> I'll change everything back to Markdown later this week. Ondra, in the
>>> meantime, you can work in Markdown.
>>>
>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>
>>>> Brad Davis
>>>> Red Hat Consulting
>>>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Ondrej Zizka" <ozizka at redhat.com>
>>>> To: "Sande Gilda" <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>
>>>> For the record: I don't strongly prefer either, only that I only touched
>>>> few things in AsciiDoc, and:
>>>> 1) certain constructs are quite less readable -> editable in the
>>>> source text (e.g. links)
>>>> 2) the render results are not satisfactory - things like a bold text
>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>
>>>> Ondra
>>>>
>>>>
>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>> Hi all,
>>>>>
>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>> the new host for documentation, supports AsciiDoc.
>>>>>
>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>> back to Markdown if it's easier for everyone.
>>>>>
>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>
>>>>> Thanks,
>>>>> Sande
>>>>>
>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>> Hi Ondra,
>>>>>>
>>>>>> You're asking me? ;-)
>>>>>>
>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>> out.
>>>>>>
>>>>>> Thanks,
>>>>>> Sande
>>>>>>
>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>> Hi Sande,
>>>>>>>
>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>> list tall and breaks the whole page layout.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Ondra
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140910/a664e6fa/attachment-0001.html
From pmuir at redhat.com Wed Sep 10 06:12:45 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 10 Sep 2014 11:12:45 +0100
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <540F7E2E.30504@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com> <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
<540EE847.9010507@redhat.com> <540F7E2E.30504@redhat.com>
Message-ID: <589F1405-476D-4BD4-AB65-57E17A7FAD05@redhat.com>
I doubt that the github wiki will be our target output platform. We?ll likely want to embed them in to the website.
On 9 Sep 2014, at 23:24, Ondrej Zizka <ozizka at redhat.com> wrote:
> Other issues might be GitHub's translator. But IDK what's the main target medium for our docs. Is that GitHub wiki?
>
> Ondra
>
>
> On 9.9.2014 13:45, Sande Gilda wrote:
>> One of Ondra's complaints is the way lists seem to display an extra paragraph between the items. Take a look at the home page here: https://github.com/windup/windup/wiki
>>
>> Note that the list items are spaced far apart. I search for a solution, and the only thing I could find was mention of using [options="compact"], but it didn't seem to work.
>>
>> Ondra, what other issues did you have.
>>
>>
>> On 09/09/2014 06:39 AM, Pete Muir wrote:
>>> The big advantages of asciidoc are:
>>>
>>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>>> * generation of pdf and epub is part of the standard toolchain
>>>
>>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>>
>>> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>>
>>> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
>>>
>>> On 9 Sep 2014, at 01:23, Sande Gilda <sgilda at redhat.com> wrote:
>>>
>>>> I'll change everything back to Markdown later this week. Ondra, in the
>>>> meantime, you can work in Markdown.
>>>>
>>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>>
>>>>> Brad Davis
>>>>> Red Hat Consulting
>>>>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Ondrej Zizka" <ozizka at redhat.com>
>>>>> To: "Sande Gilda" <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
>>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>>
>>>>> For the record: I don't strongly prefer either, only that I only touched
>>>>> few things in AsciiDoc, and:
>>>>> 1) certain constructs are quite less readable -> editable in the
>>>>> source text (e.g. links)
>>>>> 2) the render results are not satisfactory - things like a bold text
>>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>>
>>>>> Ondra
>>>>>
>>>>>
>>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>>> the new host for documentation, supports AsciiDoc.
>>>>>>
>>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>>> back to Markdown if it's easier for everyone.
>>>>>>
>>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>>
>>>>>> Thanks,
>>>>>> Sande
>>>>>>
>>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>>> Hi Ondra,
>>>>>>>
>>>>>>> You're asking me? ;-)
>>>>>>>
>>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>>> out.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sande
>>>>>>>
>>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>>> Hi Sande,
>>>>>>>>
>>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>>> list tall and breaks the whole page layout.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Ondra
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140910/2ec4da10/attachment.html
From sgilda at redhat.com Wed Sep 10 07:44:33 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 10 Sep 2014 07:44:33 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <589F1405-476D-4BD4-AB65-57E17A7FAD05@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com> <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com> <540EE847.9010507@redhat.com>
<540F7E2E.30504@redhat.com>
<589F1405-476D-4BD4-AB65-57E17A7FAD05@redhat.com>
Message-ID: <541039A1.8060204@redhat.com>
Coming into this late....
I agree with Pete. I think the Wiki is a temporary container for the
documentation. As Pete said, we may embed the docs into the web site or
it may be published to the Customer Portal. Similar to the other
documentation, we may also eventually need more complex structures like
tables and graphs and I'm pretty sure we will want to publish PDFs. I
hate to tie ourselves to something that can't grow with us. The syntax
for AsciiDoc is very similar and I don't find it any more difficult to
work with than Markdown.
I do think we need to be consistent with the documentation and use the
same tooling for all the pages. However, Ondra, if you feel more
comfortable and productive working with Markdown, please continue to use
it as you are doing an amazing job creating documentation! When you
think a page is ready, I am happy to convert it to AsciiDoc for you. :-)
On 09/10/2014 06:12 AM, Pete Muir wrote:
> I doubt that the github wiki will be our target output platform. We'll
> likely want to embed them in to the website.
>
> On 9 Sep 2014, at 23:24, Ondrej Zizka <ozizka at redhat.com
> <mailto:ozizka at redhat.com>> wrote:
>
>> Other issues might be GitHub's translator. But IDK what's the main
>> target medium for our docs. Is that GitHub wiki?
>>
>> Ondra
>>
>>
>> On 9.9.2014 13:45, Sande Gilda wrote:
>>> One of Ondra's complaints is the way lists seem to display an extra
>>> paragraph between the items. Take a look at the home page here:
>>> https://github.com/windup/windup/wiki
>>>
>>> Note that the list items are spaced far apart. I search for a
>>> solution, and the only thing I could find was mention of using
>>> |[options="compact"], |but it didn't seem to work.
>>>
>>> Ondra, what other issues did you have.
>>>
>>>
>>> On 09/09/2014 06:39 AM, Pete Muir wrote:
>>>> The big advantages of asciidoc are:
>>>>
>>>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>>>> * generation of pdf and epub is part of the standard toolchain
>>>>
>>>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>>>
>>>> GitHub's support for asciidoc wasn't great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>>>
>>>> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat's website]. I find this much easier to remember than the weird []() syntax in markdown.
>>>>
>>>> On 9 Sep 2014, at 01:23, Sande Gilda<sgilda at redhat.com> wrote:
>>>>
>>>>> I'll change everything back to Markdown later this week. Ondra, in the
>>>>> meantime, you can work in Markdown.
>>>>>
>>>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>>>
>>>>>> Brad Davis
>>>>>> Red Hat Consulting
>>>>>> Email:bdavis at redhat.com | c: 980.226.7865 |http://www.redhat.com
>>>>>>
>>>>>>
>>>>>> ----- Original Message -----
>>>>>> From: "Ondrej Zizka"<ozizka at redhat.com>
>>>>>> To: "Sande Gilda"<sgilda at redhat.com>, "Windup-dev List"<windup-dev at lists.jboss.org>
>>>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>>>
>>>>>> For the record: I don't strongly prefer either, only that I only touched
>>>>>> few things in AsciiDoc, and:
>>>>>> 1) certain constructs are quite less readable -> editable in the
>>>>>> source text (e.g. links)
>>>>>> 2) the render results are not satisfactory - things like a bold text
>>>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>>>
>>>>>> Ondra
>>>>>>
>>>>>>
>>>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>>>> the new host for documentation, supports AsciiDoc.
>>>>>>>
>>>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>>>> back to Markdown if it's easier for everyone.
>>>>>>>
>>>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sande
>>>>>>>
>>>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>>>> Hi Ondra,
>>>>>>>>
>>>>>>>> You're asking me? ;-)
>>>>>>>>
>>>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>>>> out.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sande
>>>>>>>>
>>>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>>>> Hi Sande,
>>>>>>>>>
>>>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>>>> list tall and breaks the whole page layout.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Ondra
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140910/950ff31e/attachment-0001.html
From lincolnbaxter at gmail.com Wed Sep 10 11:07:23 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 10 Sep 2014 11:07:23 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2014-09-10
Message-ID: <CAEp_U4GPrVO8eh3VXi8axawk+z+YDiY-OV_J0QHgDVs3-iQYKw@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-10-14.01.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-10-14.01.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-10-14.01.log.html
Meeting summary
---------------
* Agenda (lincolnthree, 14:02:10)
* Windup general progress and priorities (lincolnthree, 14:37:19)
* Our release for Tech Preview is in TWENTY - 20 DAYS. (lincolnthree,
14:37:56)
* This includes documentation for RH associates to learn how to use
windup (lincolnthree, 14:38:20)
* It includes an actually working tool that doesn't run forever :)
(lincolnthree, 14:38:32)
* It must include feature parity with Windup 1 (lincolnthree,
14:38:45)
* It should be possible to write custom rules using our new API (I
think this is working) (lincolnthree, 14:39:12)
* We need: A reference guide, a presentation and a reproducible demo
of usage, as well as a presentation and demo of how to write rules.
(lincolnthree, 14:39:54)
* Those last things will probably be up to sgilda and robbg primarily,
with some help from us. (lincolnthree, 14:40:29)
* Status reports (lincolnthree, 14:04:28) * I have been working on
finishing up the port of visitors from the earlier "cdi" branch of windup
(jsightler, 14:06:20) * I am mostly done, but I am trying to get the class
file metadata over along with at least some method indexing (without too
much of a performance impact) (jsightler, 14:06:29) * Once that is
complete, I will work on putting some of this information into the reports,
and building queries to make the data actually useful (jsightler, 14:06:59)
* I've been working on WINDUP-104 - and have submitted a massive PR
updating about 318 files :p (lincolnthree, 14:09:38) * as part of this
issue, I've also refactored a few things (mostly around dependencies
between addons) (lincolnthree, 14:10:29) * I've also taken the opportunity
to add some tests for the reporting, to assert that we actually generate
something with content (lincolnthree, 14:11:40) * I've also reviewed a
number of PRs and been dealing with some crazy political fallout from our
"1 month release delay" (lincolnthree, 14:12:51) * I'm working on
refactoring of WindupProcessor, GraphContext/Factory, related tests.
(ozizka, 14:17:34) * I've observed interesting forge behavior WRT resolving
artifacts, which confused me a bit when changing between master and my
branch, and rebuilding (ozizka, 14:17:34) * I've also spend a while on CI -
but the job also fails due to the same Forge bug (ozizka, 14:17:34) *
Besides that, I'm documenting how the core works internally. (ozizka,
14:17:34) * I am also going to be working on the XML-config next (because
of some of this political stuff) - should be quick (lincolnthree, 14:20:32)
* Fixed the bug caused by java legacy rules. It is actually fun, because
they pointed out a bug in windup java file processing. The source java
files were not loaded to graph completely (opposed to binary java classes)
(mbriskar, 14:25:02) * XML legacy rules fully merged, however I am
suspicious of some problems caused by a lot of rebases. (mbriskar,
14:26:09) * LINK:
https://github.com/windup/windup/commit/700639f2eec5c7f997d7ee9b19c8e133fe983143
(jsightler, 14:28:51) * Trying to run the rexster embedded, so even during
the debugging there would be option to see how the graph looks like. This
is questionable, but I want to try (mbriskar, 14:32:38) * and also
implemented an option to run windup execution on one RuleProvider only (the
dependencies get counted).. this however is for discussion.. It is for
testing purposes (mbriskar, 14:34:34)
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140910/db42a787/attachment.html
From ozizka at redhat.com Wed Sep 10 18:05:14 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 11 Sep 2014 00:05:14 +0200
Subject: [windup-dev] Doubled matching
Message-ID: <5410CB1A.7050605@redhat.com>
(23:56:23) ozizka-FN: Regarding java matching:
2014-09-10 23:58:11 INFO
org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform
First rule matched:
rules/app/java/src/test/java/org/jboss/windup/rules/java/HintsClassificationsTest.java
2014-09-10 23:58:11 INFO
org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform
First rule matched:
rules/app/java/src/test/java/org/jboss/windup/rules/java/JavaClassTest.java
2014-09-10 23:58:11 INFO
org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform
First rule matched:
rules/app/java/src/test/java/org/jboss/windup/rules/java/HintsClassificationsTest.java
2014-09-10 23:58:11 INFO
org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform
First rule matched:
rules/app/java/src/test/java/org/jboss/windup/rules/java/JavaClassTest.java
(23:56:41) ozizka-FN: This is a result of:
(23:56:50) ozizka-FN:
JavaClass.references("org.jboss.forge.furnace.*").inFile(".*").at(TypeReferenceLocation.IMPORT)
(23:59:22) ozizka-FN: Any idea why that is doubled?
Ondra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/32d21979/attachment.html
From ozizka at redhat.com Wed Sep 10 18:30:28 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 11 Sep 2014 00:30:28 +0200
Subject: [windup-dev] Doubled matching
In-Reply-To: <5410CB1A.7050605@redhat.com>
References: <5410CB1A.7050605@redhat.com>
Message-ID: <5410D104.2080209@redhat.com>
Got it... it's not doubled, it's per import. ;-)
On 11.9.2014 00:05, Ondrej Zizka wrote:
>
> (23:56:23) ozizka-FN: Regarding java matching:
>
> 2014-09-10 23:58:11 INFO
> org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform
> First rule matched:
> rules/app/java/src/test/java/org/jboss/windup/rules/java/HintsClassificationsTest.java
> 2014-09-10 23:58:11 INFO
> org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform
> First rule matched:
> rules/app/java/src/test/java/org/jboss/windup/rules/java/JavaClassTest.java
> 2014-09-10 23:58:11 INFO
> org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform
> First rule matched:
> rules/app/java/src/test/java/org/jboss/windup/rules/java/HintsClassificationsTest.java
> 2014-09-10 23:58:11 INFO
> org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform
> First rule matched:
> rules/app/java/src/test/java/org/jboss/windup/rules/java/JavaClassTest.java
>
> (23:56:41) ozizka-FN: This is a result of:
> (23:56:50) ozizka-FN:
> JavaClass.references("org.jboss.forge.furnace.*").inFile(".*").at(TypeReferenceLocation.IMPORT)
> (23:59:22) ozizka-FN: Any idea why that is doubled?
>
> Ondra
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/3fe1bbe9/attachment.html
From ozizka at redhat.com Wed Sep 10 20:25:03 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 11 Sep 2014 02:25:03 +0200
Subject: [windup-dev] Performance - Forge scanning through Weld
Message-ID: <5410EBDF.4040208@redhat.com>
It seems that Forge spends considerable time (around 10 seconds on my
laptop) scanning the classes for annotated types;
Somehow related to
org.jboss.forge.furnace.container.cdi.impl.ContainerServiceExtension.processRemoteServiceTypes()
This repeats for each test in which Forge is involved.
Could this scanning be sped up using jandex? If we have 40 tests, then
it would buy us over 5 minutes.
Ondra
From ozizka at redhat.com Wed Sep 10 20:58:49 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 11 Sep 2014 02:58:49 +0200
Subject: [windup-dev] Refactoring merge?
Message-ID: <5410F3C9.3090300@redhat.com>
Hi,
The refactoring for WINDUP-272
<https://issues.jboss.org/browse/WINDUP-272> and WINDUP-274
<https://issues.jboss.org/browse/WINDUP-274> is done.
However, it changed so many files, that I would need another few days to
merge.
The commits after the structural changes just changed few files, so I
suggest:
Let's merge my PR, then do the changes again (it's just few dir move
steps), and put the rest of the commits on top of that.
Ondra
PS: It would be COOL if such structural changes would be done when we
don't expect a big commit.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/905fcf8b/attachment.html
From ozizka at redhat.com Wed Sep 10 23:04:56 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 11 Sep 2014 05:04:56 +0200
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <541039A1.8060204@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com> <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com> <540EE847.9010507@redhat.com> <540F7E2E.30504@redhat.com> <589F1405-476D-4BD4-AB65-57E17A7FAD05@redhat.com>
<541039A1.8060204@redhat.com>
Message-ID: <54111158.70901@redhat.com>
Okay, in that case, let's do AsciiDoc, except for the few pages where I
am just storing temp info before converting to a real page, mostly
"Dev:", because that's changing often, shouldn't go to any official
docs, and I edit faster in Markdown. These pages will have "Draft" at
the top. But I'll update the existing pages in AsciiDoc.
Will that work fine?
Regards,
Ondra
On 10.9.2014 13:44, Sande Gilda wrote:
> Coming into this late....
>
> I agree with Pete. I think the Wiki is a temporary container for the
> documentation. As Pete said, we may embed the docs into the web site
> or it may be published to the Customer Portal. Similar to the other
> documentation, we may also eventually need more complex structures
> like tables and graphs and I'm pretty sure we will want to publish
> PDFs. I hate to tie ourselves to something that can't grow with us.
> The syntax for AsciiDoc is very similar and I don't find it any more
> difficult to work with than Markdown.
>
> I do think we need to be consistent with the documentation and use the
> same tooling for all the pages. However, Ondra, if you feel more
> comfortable and productive working with Markdown, please continue to
> use it as you are doing an amazing job creating documentation! When
> you think a page is ready, I am happy to convert it to AsciiDoc for
> you. :-)
>
> On 09/10/2014 06:12 AM, Pete Muir wrote:
>> I doubt that the github wiki will be our target output platform.
>> We'll likely want to embed them in to the website.
>>
>> On 9 Sep 2014, at 23:24, Ondrej Zizka <ozizka at redhat.com
>> <mailto:ozizka at redhat.com>> wrote:
>>
>>> Other issues might be GitHub's translator. But IDK what's the main
>>> target medium for our docs. Is that GitHub wiki?
>>>
>>> Ondra
>>>
>>>
>>> On 9.9.2014 13:45, Sande Gilda wrote:
>>>> One of Ondra's complaints is the way lists seem to display an extra
>>>> paragraph between the items. Take a look at the home page here:
>>>> https://github.com/windup/windup/wiki
>>>>
>>>> Note that the list items are spaced far apart. I search for a
>>>> solution, and the only thing I could find was mention of using
>>>> |[options="compact"], |but it didn't seem to work.
>>>>
>>>> Ondra, what other issues did you have.
>>>>
>>>>
>>>> On 09/09/2014 06:39 AM, Pete Muir wrote:
>>>>> The big advantages of asciidoc are:
>>>>>
>>>>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>>>>> * generation of pdf and epub is part of the standard toolchain
>>>>>
>>>>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>>>>
>>>>> GitHub's support for asciidoc wasn't great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>>>>
>>>>> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat's website]. I find this much easier to remember than the weird []() syntax in markdown.
>>>>>
>>>>> On 9 Sep 2014, at 01:23, Sande Gilda<sgilda at redhat.com> wrote:
>>>>>
>>>>>> I'll change everything back to Markdown later this week. Ondra, in the
>>>>>> meantime, you can work in Markdown.
>>>>>>
>>>>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>>>>
>>>>>>> Brad Davis
>>>>>>> Red Hat Consulting
>>>>>>> Email:bdavis at redhat.com | c: 980.226.7865 |http://www.redhat.com
>>>>>>>
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>> From: "Ondrej Zizka"<ozizka at redhat.com>
>>>>>>> To: "Sande Gilda"<sgilda at redhat.com>, "Windup-dev List"<windup-dev at lists.jboss.org>
>>>>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>>>>
>>>>>>> For the record: I don't strongly prefer either, only that I only touched
>>>>>>> few things in AsciiDoc, and:
>>>>>>> 1) certain constructs are quite less readable -> editable in the
>>>>>>> source text (e.g. links)
>>>>>>> 2) the render results are not satisfactory - things like a bold text
>>>>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>>>>
>>>>>>> Ondra
>>>>>>>
>>>>>>>
>>>>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>>>>> the new host for documentation, supports AsciiDoc.
>>>>>>>>
>>>>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>>>>> back to Markdown if it's easier for everyone.
>>>>>>>>
>>>>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sande
>>>>>>>>
>>>>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>>>>> Hi Ondra,
>>>>>>>>>
>>>>>>>>> You're asking me? ;-)
>>>>>>>>>
>>>>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>>>>> out.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Sande
>>>>>>>>>
>>>>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>>>>> Hi Sande,
>>>>>>>>>>
>>>>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>>>>> list tall and breaks the whole page layout.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Ondra
>>>>>>> _______________________________________________
>>>>>>> windup-dev mailing list
>>>>>>> windup-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/d15c3526/attachment-0001.html
From pmuir at redhat.com Thu Sep 11 04:52:05 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 11 Sep 2014 09:52:05 +0100
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <54111158.70901@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com> <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com> <540EE847.9010507@redhat.com> <540F7E2E.30504@redhat.com> <589F1405-476D-4BD4-AB65-57E17A7FAD05@redhat.com>
<541039A1.8060204@redhat.com> <54111158.70901@redhat.com>
Message-ID: <574D0BCE-C9C7-493E-89E8-ACBF4F84BD1F@redhat.com>
Sounds good to me.
On 11 Sep 2014, at 04:04, Ondrej Zizka <ozizka at redhat.com> wrote:
> Okay, in that case, let's do AsciiDoc, except for the few pages where I am just storing temp info before converting to a real page, mostly "Dev:", because that's changing often, shouldn't go to any official docs, and I edit faster in Markdown. These pages will have "Draft" at the top. But I'll update the existing pages in AsciiDoc.
>
> Will that work fine?
>
> Regards,
> Ondra
>
>
>
> On 10.9.2014 13:44, Sande Gilda wrote:
>> Coming into this late....
>>
>> I agree with Pete. I think the Wiki is a temporary container for the documentation. As Pete said, we may embed the docs into the web site or it may be published to the Customer Portal. Similar to the other documentation, we may also eventually need more complex structures like tables and graphs and I'm pretty sure we will want to publish PDFs. I hate to tie ourselves to something that can't grow with us. The syntax for AsciiDoc is very similar and I don't find it any more difficult to work with than Markdown.
>>
>> I do think we need to be consistent with the documentation and use the same tooling for all the pages. However, Ondra, if you feel more comfortable and productive working with Markdown, please continue to use it as you are doing an amazing job creating documentation! When you think a page is ready, I am happy to convert it to AsciiDoc for you. :-)
>>
>> On 09/10/2014 06:12 AM, Pete Muir wrote:
>>> I doubt that the github wiki will be our target output platform. We?ll likely want to embed them in to the website.
>>>
>>> On 9 Sep 2014, at 23:24, Ondrej Zizka <ozizka at redhat.com> wrote:
>>>
>>>> Other issues might be GitHub's translator. But IDK what's the main target medium for our docs. Is that GitHub wiki?
>>>>
>>>> Ondra
>>>>
>>>>
>>>> On 9.9.2014 13:45, Sande Gilda wrote:
>>>>> One of Ondra's complaints is the way lists seem to display an extra paragraph between the items. Take a look at the home page here: https://github.com/windup/windup/wiki
>>>>>
>>>>> Note that the list items are spaced far apart. I search for a solution, and the only thing I could find was mention of using [options="compact"], but it didn't seem to work.
>>>>>
>>>>> Ondra, what other issues did you have.
>>>>>
>>>>>
>>>>> On 09/09/2014 06:39 AM, Pete Muir wrote:
>>>>>> The big advantages of asciidoc are:
>>>>>>
>>>>>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>>>>>> * generation of pdf and epub is part of the standard toolchain
>>>>>>
>>>>>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>>>>>
>>>>>> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>>>>>
>>>>>> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
>>>>>>
>>>>>> On 9 Sep 2014, at 01:23, Sande Gilda <sgilda at redhat.com> wrote:
>>>>>>
>>>>>>> I'll change everything back to Markdown later this week. Ondra, in the
>>>>>>> meantime, you can work in Markdown.
>>>>>>>
>>>>>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>>>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>>>>>
>>>>>>>> Brad Davis
>>>>>>>> Red Hat Consulting
>>>>>>>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>>>>>>>
>>>>>>>>
>>>>>>>> ----- Original Message -----
>>>>>>>> From: "Ondrej Zizka" <ozizka at redhat.com>
>>>>>>>> To: "Sande Gilda" <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
>>>>>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>>>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>>>>>
>>>>>>>> For the record: I don't strongly prefer either, only that I only touched
>>>>>>>> few things in AsciiDoc, and:
>>>>>>>> 1) certain constructs are quite less readable -> editable in the
>>>>>>>> source text (e.g. links)
>>>>>>>> 2) the render results are not satisfactory - things like a bold text
>>>>>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>>>>>
>>>>>>>> Ondra
>>>>>>>>
>>>>>>>>
>>>>>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>>>>>> the new host for documentation, supports AsciiDoc.
>>>>>>>>>
>>>>>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>>>>>> back to Markdown if it's easier for everyone.
>>>>>>>>>
>>>>>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Sande
>>>>>>>>>
>>>>>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>>>>>> Hi Ondra,
>>>>>>>>>>
>>>>>>>>>> You're asking me? ;-)
>>>>>>>>>>
>>>>>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>>>>>> out.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Sande
>>>>>>>>>>
>>>>>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>>>>>> Hi Sande,
>>>>>>>>>>>
>>>>>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>>>>>> list tall and breaks the whole page layout.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Ondra
>>>>>>>> _______________________________________________
>>>>>>>> windup-dev mailing list
>>>>>>>> windup-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>> _______________________________________________
>>>>>>> windup-dev mailing list
>>>>>>> windup-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/b268536c/attachment.html
From pmuir at redhat.com Thu Sep 11 05:02:49 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 11 Sep 2014 10:02:49 +0100
Subject: [windup-dev] Refactoring merge?
In-Reply-To: <5410F3C9.3090300@redhat.com>
References: <5410F3C9.3090300@redhat.com>
Message-ID: <C4558CD6-73D6-493D-97EC-55A56E3D4786@redhat.com>
I can?t spot the PRs for these. Got a link?
On 11 Sep 2014, at 01:58, Ondrej Zizka <ozizka at redhat.com> wrote:
> Hi,
>
> The refactoring for WINDUP-272 and WINDUP-274 is done.
>
> However, it changed so many files, that I would need another few days to merge.
> The commits after the structural changes just changed few files, so I suggest:
>
> Let's merge my PR, then do the changes again (it's just few dir move steps), and put the rest of the commits on top of that.
>
> Ondra
>
> PS: It would be COOL if such structural changes would be done when we don't expect a big commit.
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/83d44f01/attachment.html
From sgilda at redhat.com Thu Sep 11 07:13:53 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 11 Sep 2014 07:13:53 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <54111158.70901@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com> <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com> <540EE847.9010507@redhat.com> <540F7E2E.30504@redhat.com> <589F1405-476D-4BD4-AB65-57E17A7FAD05@redhat.com> <541039A1.8060204@redhat.com>
<54111158.70901@redhat.com>
Message-ID: <541183F1.9000405@redhat.com>
Hi Ondra,
Of course! As I said on IRC, what ever is easiest for you is fine by me. :-)
Thanks,
Sande
On 09/10/2014 11:04 PM, Ondrej Zizka wrote:
> Okay, in that case, let's do AsciiDoc, except for the few pages where
> I am just storing temp info before converting to a real page, mostly
> "Dev:", because that's changing often, shouldn't go to any official
> docs, and I edit faster in Markdown. These pages will have "Draft" at
> the top. But I'll update the existing pages in AsciiDoc.
>
> Will that work fine?
>
> Regards,
> Ondra
>
>
>
> On 10.9.2014 13:44, Sande Gilda wrote:
>> Coming into this late....
>>
>> I agree with Pete. I think the Wiki is a temporary container for the
>> documentation. As Pete said, we may embed the docs into the web site
>> or it may be published to the Customer Portal. Similar to the other
>> documentation, we may also eventually need more complex structures
>> like tables and graphs and I'm pretty sure we will want to publish
>> PDFs. I hate to tie ourselves to something that can't grow with us.
>> The syntax for AsciiDoc is very similar and I don't find it any more
>> difficult to work with than Markdown.
>>
>> I do think we need to be consistent with the documentation and use
>> the same tooling for all the pages. However, Ondra, if you feel more
>> comfortable and productive working with Markdown, please continue to
>> use it as you are doing an amazing job creating documentation! When
>> you think a page is ready, I am happy to convert it to AsciiDoc for
>> you. :-)
>>
>> On 09/10/2014 06:12 AM, Pete Muir wrote:
>>> I doubt that the github wiki will be our target output platform.
>>> We'll likely want to embed them in to the website.
>>>
>>> On 9 Sep 2014, at 23:24, Ondrej Zizka <ozizka at redhat.com
>>> <mailto:ozizka at redhat.com>> wrote:
>>>
>>>> Other issues might be GitHub's translator. But IDK what's the main
>>>> target medium for our docs. Is that GitHub wiki?
>>>>
>>>> Ondra
>>>>
>>>>
>>>> On 9.9.2014 13:45, Sande Gilda wrote:
>>>>> One of Ondra's complaints is the way lists seem to display an
>>>>> extra paragraph between the items. Take a look at the home page
>>>>> here: https://github.com/windup/windup/wiki
>>>>>
>>>>> Note that the list items are spaced far apart. I search for a
>>>>> solution, and the only thing I could find was mention of using
>>>>> |[options="compact"], |but it didn't seem to work.
>>>>>
>>>>> Ondra, what other issues did you have.
>>>>>
>>>>>
>>>>> On 09/09/2014 06:39 AM, Pete Muir wrote:
>>>>>> The big advantages of asciidoc are:
>>>>>>
>>>>>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>>>>>> * generation of pdf and epub is part of the standard toolchain
>>>>>>
>>>>>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>>>>>
>>>>>> GitHub's support for asciidoc wasn't great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>>>>>
>>>>>> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat's website]. I find this much easier to remember than the weird []() syntax in markdown.
>>>>>>
>>>>>> On 9 Sep 2014, at 01:23, Sande Gilda<sgilda at redhat.com> wrote:
>>>>>>
>>>>>>> I'll change everything back to Markdown later this week. Ondra, in the
>>>>>>> meantime, you can work in Markdown.
>>>>>>>
>>>>>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>>>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>>>>>
>>>>>>>> Brad Davis
>>>>>>>> Red Hat Consulting
>>>>>>>> Email:bdavis at redhat.com | c: 980.226.7865 |http://www.redhat.com
>>>>>>>>
>>>>>>>>
>>>>>>>> ----- Original Message -----
>>>>>>>> From: "Ondrej Zizka"<ozizka at redhat.com>
>>>>>>>> To: "Sande Gilda"<sgilda at redhat.com>, "Windup-dev List"<windup-dev at lists.jboss.org>
>>>>>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>>>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>>>>>
>>>>>>>> For the record: I don't strongly prefer either, only that I only touched
>>>>>>>> few things in AsciiDoc, and:
>>>>>>>> 1) certain constructs are quite less readable -> editable in the
>>>>>>>> source text (e.g. links)
>>>>>>>> 2) the render results are not satisfactory - things like a bold text
>>>>>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>>>>>
>>>>>>>> Ondra
>>>>>>>>
>>>>>>>>
>>>>>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>>>>>> the new host for documentation, supports AsciiDoc.
>>>>>>>>>
>>>>>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>>>>>> back to Markdown if it's easier for everyone.
>>>>>>>>>
>>>>>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Sande
>>>>>>>>>
>>>>>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>>>>>> Hi Ondra,
>>>>>>>>>>
>>>>>>>>>> You're asking me? ;-)
>>>>>>>>>>
>>>>>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>>>>>> out.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Sande
>>>>>>>>>>
>>>>>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>>>>>> Hi Sande,
>>>>>>>>>>>
>>>>>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>>>>>> list tall and breaks the whole page layout.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Ondra
>>>>>>>> _______________________________________________
>>>>>>>> windup-dev mailing list
>>>>>>>> windup-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>> _______________________________________________
>>>>>>> windup-dev mailing list
>>>>>>> windup-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>> windup-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/2aea5ade/attachment-0001.html
From sgilda at redhat.com Thu Sep 11 07:23:20 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 11 Sep 2014 07:23:20 -0400
Subject: [windup-dev] Fwd: Re: GitHub problem rendering AsciiDoc lists
In-Reply-To: <discussions/b281008038fa11e4882d991f07d79882/comments/1323289@github.com>
References: <discussions/b281008038fa11e4882d991f07d79882/comments/1323289@github.com>
Message-ID: <54118628.3080104@redhat.com>
Ondra, I reported the issue you brought up where GitHub renders AsciiDoc
list items with a paragraph tag. It looks like they are going to address
it. :-)
-------- Original Message --------
Subject: Re: GitHub problem rendering AsciiDoc lists
Date: Thu, 11 Sep 2014 03:18:00 -0700
From: Jess Hosman (GitHub Staff) <support at github.com>
To: Sande Gilda <sgilda at redhat.com>
Hi Sande,
Thanks for pointing this out! I've opened an issue to let our developers know about it. If they have any questions, we'll hit you up for more information.
Cheers,
Jess
> GitHub renders Markdown list items correctly, but renders AsciiDoc list
items with a `<p></p>` tag. The resulting list has blank lines between
list items, resulting in a very spread out list.
> You can see examples here:
Markdown: https://github.com/sgilda/playground/blob/master/file-markdown.md
Asciidoc:
https://github.com/sgilda/playground/blob/master/file-asciidoc.asciidoc
Is this a stylesheet issue?
Thanks,
Sande Gilda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/64b3f405/attachment.html
From ozizka at redhat.com Thu Sep 11 07:53:44 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 11 Sep 2014 13:53:44 +0200
Subject: [windup-dev] Fwd: Re: GitHub problem rendering AsciiDoc lists
In-Reply-To: <54118628.3080104@redhat.com>
References: <discussions/b281008038fa11e4882d991f07d79882/comments/1323289@github.com>
<54118628.3080104@redhat.com>
Message-ID: <54118D48.8030409@redhat.com>
Thanks!
Actually I have reported it too, directly to AsciiDoc forum, but that
seems to be a wrong place - I should have posted it to whichever impl
they are using, which I don't know, so thanks for your mail to them.
Ondra
On 11.9.2014 13:23, Sande Gilda wrote:
> Ondra, I reported the issue you brought up where GitHub renders
> AsciiDoc list items with a paragraph tag. It looks like they are going
> to address it. :-)
>
>
> -------- Original Message --------
> Subject: Re: GitHub problem rendering AsciiDoc lists
> Date: Thu, 11 Sep 2014 03:18:00 -0700
> From: Jess Hosman (GitHub Staff) <support at github.com>
> To: Sande Gilda <sgilda at redhat.com>
>
>
>
> Hi Sande,
>
> Thanks for pointing this out! I've opened an issue to let our developers know about it. If they have any questions, we'll hit you up for more information.
>
> Cheers,
> Jess
>
>
> > GitHub renders Markdown list items correctly, but renders AsciiDoc list
> items with a `<p></p>` tag. The resulting list has blank lines between
> list items, resulting in a very spread out list.
>
> > You can see examples here:
>
> Markdown:https://github.com/sgilda/playground/blob/master/file-markdown.md
> Asciidoc:
> https://github.com/sgilda/playground/blob/master/file-asciidoc.asciidoc
>
> Is this a stylesheet issue?
>
> Thanks,
> Sande Gilda
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/2748ba6d/attachment.html
From sgilda at redhat.com Thu Sep 11 08:07:16 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 11 Sep 2014 08:07:16 -0400
Subject: [windup-dev] Fwd: Re: GitHub problem rendering AsciiDoc lists
In-Reply-To: <54118D48.8030409@redhat.com>
References: <discussions/b281008038fa11e4882d991f07d79882/comments/1323289@github.com> <54118628.3080104@redhat.com>
<54118D48.8030409@redhat.com>
Message-ID: <54119074.80806@redhat.com>
Pete pointed out it's probably a GitHub stylesheet issue, so I went to
them. I think it renders fine using other tooling. :-)
On 09/11/2014 07:53 AM, Ondrej Zizka wrote:
> Thanks!
>
> Actually I have reported it too, directly to AsciiDoc forum, but that
> seems to be a wrong place - I should have posted it to whichever impl
> they are using, which I don't know, so thanks for your mail to them.
>
> Ondra
>
>
> On 11.9.2014 13:23, Sande Gilda wrote:
>> Ondra, I reported the issue you brought up where GitHub renders
>> AsciiDoc list items with a paragraph tag. It looks like they are
>> going to address it. :-)
>>
>>
>> -------- Original Message --------
>> Subject: Re: GitHub problem rendering AsciiDoc lists
>> Date: Thu, 11 Sep 2014 03:18:00 -0700
>> From: Jess Hosman (GitHub Staff) <support at github.com>
>> To: Sande Gilda <sgilda at redhat.com>
>>
>>
>>
>> Hi Sande,
>>
>> Thanks for pointing this out! I've opened an issue to let our developers know about it. If they have any questions, we'll hit you up for more information.
>>
>> Cheers,
>> Jess
>>
>>
>> > GitHub renders Markdown list items correctly, but renders AsciiDoc list
>> items with a `<p></p>` tag. The resulting list has blank lines between
>> list items, resulting in a very spread out list.
>>
>> > You can see examples here:
>>
>> Markdown:https://github.com/sgilda/playground/blob/master/file-markdown.md
>> Asciidoc:
>> https://github.com/sgilda/playground/blob/master/file-asciidoc.asciidoc
>>
>> Is this a stylesheet issue?
>>
>> Thanks,
>> Sande Gilda
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/671c23f5/attachment.html
From sgilda at redhat.com Thu Sep 11 09:16:11 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 11 Sep 2014 09:16:11 -0400
Subject: [windup-dev] Fwd: Re: GitHub problem rendering AsciiDoc lists
In-Reply-To: <54118D48.8030409@redhat.com>
References: <discussions/b281008038fa11e4882d991f07d79882/comments/1323289@github.com> <54118628.3080104@redhat.com>
<54118D48.8030409@redhat.com>
Message-ID: <5411A09B.2030608@redhat.com>
Ondra, you are right. I just tested a build of an AsciiDoc file using
Asciidoctor and it renders list items with the paragraph tag too. So
it's not just GitHub!
On 09/11/2014 07:53 AM, Ondrej Zizka wrote:
> Thanks!
>
> Actually I have reported it too, directly to AsciiDoc forum, but that
> seems to be a wrong place - I should have posted it to whichever impl
> they are using, which I don't know, so thanks for your mail to them.
>
> Ondra
>
>
> On 11.9.2014 13:23, Sande Gilda wrote:
>> Ondra, I reported the issue you brought up where GitHub renders
>> AsciiDoc list items with a paragraph tag. It looks like they are
>> going to address it. :-)
>>
>>
>> -------- Original Message --------
>> Subject: Re: GitHub problem rendering AsciiDoc lists
>> Date: Thu, 11 Sep 2014 03:18:00 -0700
>> From: Jess Hosman (GitHub Staff) <support at github.com>
>> To: Sande Gilda <sgilda at redhat.com>
>>
>>
>>
>> Hi Sande,
>>
>> Thanks for pointing this out! I've opened an issue to let our developers know about it. If they have any questions, we'll hit you up for more information.
>>
>> Cheers,
>> Jess
>>
>>
>> > GitHub renders Markdown list items correctly, but renders AsciiDoc list
>> items with a `<p></p>` tag. The resulting list has blank lines between
>> list items, resulting in a very spread out list.
>>
>> > You can see examples here:
>>
>> Markdown:https://github.com/sgilda/playground/blob/master/file-markdown.md
>> Asciidoc:
>> https://github.com/sgilda/playground/blob/master/file-asciidoc.asciidoc
>>
>> Is this a stylesheet issue?
>>
>> Thanks,
>> Sande Gilda
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/37a4cc64/attachment-0001.html
From jsightle at redhat.com Thu Sep 11 10:57:44 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 11 Sep 2014 10:57:44 -0400
Subject: [windup-dev] Refactoring merge?
In-Reply-To: <5410F3C9.3090300@redhat.com>
References: <5410F3C9.3090300@redhat.com>
Message-ID: <5411B868.70809@redhat.com>
Hi Ondra,
I don't see how this could take days to rebase. Would you like me to
take a look?
Thanks,
Jess
On 09/10/2014 08:58 PM, Ondrej Zizka wrote:
> Hi,
>
> The refactoring for WINDUP-272
> <https://issues.jboss.org/browse/WINDUP-272> and WINDUP-274
> <https://issues.jboss.org/browse/WINDUP-274> is done.
>
> However, it changed so many files, that I would need another few days
> to merge.
> The commits after the structural changes just changed few files, so I
> suggest:
>
> Let's merge my PR, then do the changes again (it's just few dir move
> steps), and put the rest of the commits on top of that.
>
> Ondra
>
> PS: It would be COOL if such structural changes would be done when we
> don't expect a big commit.
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/0123c1b4/attachment.html
From ozizka at redhat.com Thu Sep 11 15:40:06 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 11 Sep 2014 21:40:06 +0200
Subject: [windup-dev] Refactoring merge?
In-Reply-To: <5411B868.70809@redhat.com>
References: <5410F3C9.3090300@redhat.com> <5411B868.70809@redhat.com>
Message-ID: <5411FA96.8060904@redhat.com>
Days was an overstatement, but I might see it very pessimistically after
long time of pushing all tests to pass and then seeing conflicts, which
upon resolving introduced new failures.
Thanks though!
Ondra
On 11.9.2014 16:57, Jess Sightler wrote:
> Hi Ondra,
>
> I don't see how this could take days to rebase. Would you like me to
> take a look?
>
> Thanks,
> Jess
>
> On 09/10/2014 08:58 PM, Ondrej Zizka wrote:
>> Hi,
>>
>> The refactoring for WINDUP-272
>> <https://issues.jboss.org/browse/WINDUP-272> and WINDUP-274
>> <https://issues.jboss.org/browse/WINDUP-274> is done.
>>
>> However, it changed so many files, that I would need another few days
>> to merge.
>> The commits after the structural changes just changed few files, so I
>> suggest:
>>
>> Let's merge my PR, then do the changes again (it's just few dir move
>> steps), and put the rest of the commits on top of that.
>>
>> Ondra
>>
>> PS: It would be COOL if such structural changes would be done when
>> we don't expect a big commit.
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/72a0a161/attachment.html
From sgilda at redhat.com Thu Sep 11 16:23:49 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 11 Sep 2014 16:23:49 -0400
Subject: [windup-dev] Fwd: Re: GitHub problem rendering AsciiDoc lists
In-Reply-To: <discussions/b281008038fa11e4882d991f07d79882/comments/1323980@github.com>
References: <discussions/b281008038fa11e4882d991f07d79882/comments/1323980@github.com>
Message-ID: <541204D5.7020005@redhat.com>
This is interesting. GitHub uses Asciidoctor to render the asciidoc files!
Ondra, where did you report this issue? If you didn't report it to
Asciidoctor, I will.
-------- Original Message --------
Subject: Re: GitHub problem rendering AsciiDoc lists
Date: Thu, 11 Sep 2014 10:08:00 -0700
From: Jess Hosman (GitHub Staff) <support at github.com>
To: Sande Gilda <sgilda at redhat.com>
Hi Sande,
Thanks for your patience. After some digging, it looks like we use the third party tool Asciidoctor [1] for the conversion, which is where the extra `<p>` tags are coming from. I'd recommend opening an issue in the Asciidoctor repo about this. Once changes are made there, we should be able to pull them into GitHub.
Cheers,
Jess
[1]: https://github.com/asciidoctor/asciidoctor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/378610d1/attachment.html
From ozizka at redhat.com Thu Sep 11 17:17:08 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 11 Sep 2014 23:17:08 +0200
Subject: [windup-dev] Fwd: Re: GitHub problem rendering AsciiDoc lists
In-Reply-To: <541204D5.7020005@redhat.com>
References: <discussions/b281008038fa11e4882d991f07d79882/comments/1323980@github.com>
<541204D5.7020005@redhat.com>
Message-ID: <54121154.5040205@redhat.com>
I posted it to AsciiDoc. But they don't share my opinion that <p> in
<li> is a wrong idea.
https://groups.google.com/forum/#!topic/asciidoc/BF9HlACuNjE
They have an unfortunate mix of "DocBook legacy" and forward compatibility.
But it's a bit configurable. Dan wrote:
It's also pretty each to change by hacking the html5.conf file:
----
[paragraph]
{title?<div class="title">{title}</div>}
<p class="paragraph{role? {role}}{unbreakable-option? unbreakable}"{id?
id="{id}"}>
|
</p>
----
We could ask GitHub to change that for li I guess.
Or, as I suggested earlier, find out if GitHub allows to apply
per-project CSS.
Ondra
On 11.9.2014 22:23, Sande Gilda wrote:
> This is interesting. GitHub uses Asciidoctor to render the asciidoc files!
>
> Ondra, where did you report this issue? If you didn't report it to
> Asciidoctor, I will.
>
>
> -------- Original Message --------
> Subject: Re: GitHub problem rendering AsciiDoc lists
> Date: Thu, 11 Sep 2014 10:08:00 -0700
> From: Jess Hosman (GitHub Staff) <support at github.com>
> To: Sande Gilda <sgilda at redhat.com>
>
>
>
> Hi Sande,
>
> Thanks for your patience. After some digging, it looks like we use the third party tool Asciidoctor [1] for the conversion, which is where the extra `<p>` tags are coming from. I'd recommend opening an issue in the Asciidoctor repo about this. Once changes are made there, we should be able to pull them into GitHub.
>
> Cheers,
> Jess
>
> [1]:https://github.com/asciidoctor/asciidoctor
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140911/d46e8e92/attachment.html
From lincolnbaxter at gmail.com Fri Sep 12 07:04:58 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 12 Sep 2014 07:04:58 -0400
Subject: [windup-dev] Problem with WindupConfigModel
In-Reply-To: <540B0598.9070003@redhat.com>
References: <540B0598.9070003@redhat.com>
Message-ID: <CAEp_U4En=CG5v9doo+afjNF07Qy7hD8R3f9_vmnLkK-D2cG8Gw@mail.gmail.com>
Discussion moved to pull request: https://github.com/windup/windup/pull/228
On Sat, Sep 6, 2014 at 9:01 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Problem with WindupConfigModel is that *currently* it needs context
> initialized, since it is initialized like this:
>
> WindupConfigurationModel config =
> GraphService.getConfigurationModel(context);
>
> And at the same time this config "DTO" needs to be passed into the
> top-level API (currently WindupProcessor).
>
> I can see 2 solutions:
>
> A) Continue using WCM, implement WINDUP-147 GraphService.merge()
> to store classes implementing the model interface
> so that supports adjacent models (needed for the scan packages)
>
> B) Have WindupConfig, and copy stuff to WCM (which is the same as A,
> only done manually)
>
> C) What I am currently doing, an ugly hack - passing final variables
> into GraphLifecycleListener
>
> Ondra
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/6db8083e/attachment.html
From lincolnbaxter at gmail.com Fri Sep 12 07:09:31 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 12 Sep 2014 07:09:31 -0400
Subject: [windup-dev] Double building?
In-Reply-To: <540FB65D.7070704@redhat.com>
References: <540FB65D.7070704@redhat.com>
Message-ID: <CAEp_U4Ek_tiAT7MBaC26+ozb=ntx240uqjQXd8CK2TsSx_X72w@mail.gmail.com>
Sorry, I missed this mail until now. The issue is that <optional> maven
deps were not being picked up by the maven reactor build without performing
the 'mvn install' step. This issue FORGE-2003, has been resolved and is now
in Forge 2.10.0.Final - I will do an update and send a PR to fix this in
Windup.
On Tue, Sep 9, 2014 at 10:24 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Hi (Lincoln),
>
> could you please describe the issue with forge resolver more closely?
> I think I was hit by that few times - the app is behaving differently
> when I build only one module, then run test with other, and in whole run.
>
> What's the cause and what exactly does it cause - what should I count with?
>
> On unrelated note - I changed few things, rebuilt few times, and now
> instead of
> HintsClassificationsTest.testIterationVariableResolving:162
> expected:<3> but was:<0>
> I have
> HintsClassificationsTest.testIterationVariableResolving:162
> expected:<3> but was:<4>
> Which is good - the whole run sticks with the same graph :)
> But a bit weirder - having more nodes than the test expects...
> More tomorrow.
>
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/4b790b33/attachment-0001.html
From lincolnbaxter at gmail.com Fri Sep 12 11:28:43 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 12 Sep 2014 11:28:43 -0400
Subject: [windup-dev] Doubled matching
In-Reply-To: <5410D104.2080209@redhat.com>
References: <5410CB1A.7050605@redhat.com>
<5410D104.2080209@redhat.com>
Message-ID: <CAEp_U4H8trth5GArLxRJ0O2x2=9HFdddQj68sLyqxM5aOQmP=Q@mail.gmail.com>
Ahhh yes. That makes sense. Good to know! The new hint logging should help
with clearing this up. I imagine we will probably make that a little more
verbose in the future.
On Wed, Sep 10, 2014 at 6:30 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Got it... it's not doubled, it's per import. ;-)
>
>
> On 11.9.2014 00:05, Ondrej Zizka wrote:
>
>
> (23:56:23) ozizka-FN: Regarding java matching:
>
> 2014-09-10 23:58:11 INFO
> org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform First
> rule matched:
> rules/app/java/src/test/java/org/jboss/windup/rules/java/HintsClassificationsTest.java
> 2014-09-10 23:58:11 INFO
> org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform First
> rule matched:
> rules/app/java/src/test/java/org/jboss/windup/rules/java/JavaClassTest.java
> 2014-09-10 23:58:11 INFO
> org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform First
> rule matched:
> rules/app/java/src/test/java/org/jboss/windup/rules/java/HintsClassificationsTest.java
> 2014-09-10 23:58:11 INFO
> org.jboss.windup.rules.java.TestJavaClassTestRuleProvider$2 perform First
> rule matched:
> rules/app/java/src/test/java/org/jboss/windup/rules/java/JavaClassTest.java
>
> (23:56:41) ozizka-FN: This is a result of:
> (23:56:50) ozizka-FN:
> JavaClass.references("org.jboss.forge.furnace.*").inFile(".*").at(TypeReferenceLocation.IMPORT)
> (23:59:22) ozizka-FN: Any idea why that is doubled?
>
> Ondra
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/159e0f10/attachment.html
From lincolnbaxter at gmail.com Fri Sep 12 11:29:38 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 12 Sep 2014 11:29:38 -0400
Subject: [windup-dev] Performance - Forge scanning through Weld
In-Reply-To: <5410EBDF.4040208@redhat.com>
References: <5410EBDF.4040208@redhat.com>
Message-ID: <CAEp_U4H8Pw-oGuX_fcg53FvnZOPrktt8gHABw_Opdmq3DgeTXQ@mail.gmail.com>
I would be happy to see an improvement in the furnace-cdi container to
support this, when we have time to work on it. Right now it's not critical,
but it would be nice once things settle down after the tech-preview release.
On Wed, Sep 10, 2014 at 8:25 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> It seems that Forge spends considerable time (around 10 seconds on my
> laptop) scanning the classes for annotated types;
> Somehow related to
>
> org.jboss.forge.furnace.container.cdi.impl.ContainerServiceExtension.processRemoteServiceTypes()
>
> This repeats for each test in which Forge is involved.
>
> Could this scanning be sped up using jandex? If we have 40 tests, then
> it would buy us over 5 minutes.
>
> Ondra
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/70467af5/attachment.html
From lincolnbaxter at gmail.com Fri Sep 12 11:30:53 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 12 Sep 2014 11:30:53 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <541183F1.9000405@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com>
<540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com>
<216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com>
<540E488F.90105@redhat.com>
<C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
<540EE847.9010507@redhat.com> <540F7E2E.30504@redhat.com>
<589F1405-476D-4BD4-AB65-57E17A7FAD05@redhat.com>
<541039A1.8060204@redhat.com> <54111158.70901@redhat.com>
<541183F1.9000405@redhat.com>
Message-ID: <CAEp_U4H_fc3c4kiRzCnyqjfCZefO476Zf29bWA=o8Dmah9twQQ@mail.gmail.com>
Coming in to this late, I'd prefer to stick with one format, and it seems
like we (as JBoss) are moving toward asciidoc, so I think we should stick
with that (for all of the previously stated reasons.)
On Thu, Sep 11, 2014 at 7:13 AM, Sande Gilda <sgilda at redhat.com> wrote:
> Hi Ondra,
>
> Of course! As I said on IRC, what ever is easiest for you is fine by me.
> :-)
>
> Thanks,
> Sande
>
>
> On 09/10/2014 11:04 PM, Ondrej Zizka wrote:
>
> Okay, in that case, let's do AsciiDoc, except for the few pages where I am
> just storing temp info before converting to a real page, mostly "Dev:",
> because that's changing often, shouldn't go to any official docs, and I
> edit faster in Markdown. These pages will have "Draft" at the top. But I'll
> update the existing pages in AsciiDoc.
>
> Will that work fine?
>
> Regards,
> Ondra
>
>
>
> On 10.9.2014 13:44, Sande Gilda wrote:
>
> Coming into this late....
>
> I agree with Pete. I think the Wiki is a temporary container for the
> documentation. As Pete said, we may embed the docs into the web site or it
> may be published to the Customer Portal. Similar to the other
> documentation, we may also eventually need more complex structures like
> tables and graphs and I'm pretty sure we will want to publish PDFs. I hate
> to tie ourselves to something that can't grow with us. The syntax for
> AsciiDoc is very similar and I don't find it any more difficult to work
> with than Markdown.
>
> I do think we need to be consistent with the documentation and use the
> same tooling for all the pages. However, Ondra, if you feel more
> comfortable and productive working with Markdown, please continue to use it
> as you are doing an amazing job creating documentation! When you think a
> page is ready, I am happy to convert it to AsciiDoc for you. :-)
>
> On 09/10/2014 06:12 AM, Pete Muir wrote:
>
> I doubt that the github wiki will be our target output platform. We?ll
> likely want to embed them in to the website.
>
> On 9 Sep 2014, at 23:24, Ondrej Zizka <ozizka at redhat.com> wrote:
>
> Other issues might be GitHub's translator. But IDK what's the main
> target medium for our docs. Is that GitHub wiki?
>
> Ondra
>
>
> On 9.9.2014 13:45, Sande Gilda wrote:
>
> One of Ondra's complaints is the way lists seem to display an extra
> paragraph between the items. Take a look at the home page here:
> https://github.com/windup/windup/wiki
>
> Note that the list items are spaced far apart. I search for a solution,
> and the only thing I could find was mention of using [options="compact"], but
> it didn't seem to work.
>
> Ondra, what other issues did you have.
>
>
> On 09/09/2014 06:39 AM, Pete Muir wrote:
>
> The big advantages of asciidoc are:
>
> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
> * generation of pdf and epub is part of the standard toolchain
>
> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>
> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>
> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
>
> On 9 Sep 2014, at 01:23, Sande Gilda <sgilda at redhat.com> <sgilda at redhat.com> wrote:
>
>
> I'll change everything back to Markdown later this week. Ondra, in the
> meantime, you can work in Markdown.
>
> On 09/08/2014 08:12 PM, Brad Davis wrote:
>
> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Ondrej Zizka" <ozizka at redhat.com> <ozizka at redhat.com>
> To: "Sande Gilda" <sgilda at redhat.com> <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org> <windup-dev at lists.jboss.org>
> Sent: Monday, September 8, 2014 7:58:20 PM
> Subject: Re: [windup-dev] Asciidoc - lists
>
> For the record: I don't strongly prefer either, only that I only touched
> few things in AsciiDoc, and:
> 1) certain constructs are quite less readable -> editable in the
> source text (e.g. links)
> 2) the render results are not satisfactory - things like a bold text
> in a lists are not properly implemented on whatever GitHub uses.
>
> Ondra
>
>
> On 9.9.2014 01:17, Sande Gilda wrote:
>
> Hi all,
>
> Ondra asked me about the advantages of AsciiDoc over Markdown. I
> really don't know, but I do remember Pete saying AsciiDoc would be
> better for the quickstart README files long ago. And I believe Drupal,
> the new host for documentation, supports AsciiDoc.
>
> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
> come up with a good reason for sticking with it, I'm fine with going
> back to Markdown if it's easier for everyone.
>
> So, AsciiDoc advocates, please speak up now.
>
> Thanks,
> Sande
>
> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>
> Hi Ondra,
>
> You're asking me? ;-)
>
> I'm totally new to asciidoc. I'll research it and see what I can find
> out.
>
> Thanks,
> Sande
>
> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>
> Hi Sande,
>
> is there any way to prevent asciidoc put <p> to each <li>? Makes the
> list tall and breaks the whole page layout.
>
> Thanks,
> Ondra
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/f1bf6dc4/attachment-0001.html
From sgilda at redhat.com Fri Sep 12 11:46:11 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 12 Sep 2014 11:46:11 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <CAEp_U4H_fc3c4kiRzCnyqjfCZefO476Zf29bWA=o8Dmah9twQQ@mail.gmail.com>
References: <540E2A10.4000704@redhat.com>
<540E2DD1.80203@redhat.com> <540E38EC.9000802@redhat.com>
<540E429C.1080004@redhat.com> <216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com> <540E488F.90105@redhat.com> <C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com> <540EE847.9010507@redhat.com>
<540F7E2E.30504@redhat.com> <589F1405-476D-4BD4-AB65-57E17A7FAD05@redhat.com> <541039A1.8060204@redhat.com>
<54111158.70901@redhat.com> <541183F1.9000405@redhat.com>
<CAEp_U4H_fc3c4kiRzCnyqjfCZefO476Zf29bWA=o8Dmah9twQQ@mail.gmail.com>
Message-ID: <54131543.50909@redhat.com>
Hi Lincoln,
The plan is definitely to make them all Asciidoc format. Ondra writes a
lot of doc and if he feels more productive using Markdown when creating
a new document, that's fine by me. When he's finished with a topic, I
will convert it to Asciidoc. Then he will have to make any updates using
the Asciidoc format. So everything will be Asciidoc.
Thanks,
Sande
On 09/12/2014 11:30 AM, Lincoln Baxter, III wrote:
> Coming in to this late, I'd prefer to stick with one format, and it
> seems like we (as JBoss) are moving toward asciidoc, so I think we
> should stick with that (for all of the previously stated reasons.)
>
> On Thu, Sep 11, 2014 at 7:13 AM, Sande Gilda <sgilda at redhat.com
> <mailto:sgilda at redhat.com>> wrote:
>
> Hi Ondra,
>
> Of course! As I said on IRC, what ever is easiest for you is fine
> by me. :-)
>
> Thanks,
> Sande
>
>
> On 09/10/2014 11:04 PM, Ondrej Zizka wrote:
>> Okay, in that case, let's do AsciiDoc, except for the few pages
>> where I am just storing temp info before converting to a real
>> page, mostly "Dev:", because that's changing often, shouldn't go
>> to any official docs, and I edit faster in Markdown. These pages
>> will have "Draft" at the top. But I'll update the existing pages
>> in AsciiDoc.
>>
>> Will that work fine?
>>
>> Regards,
>> Ondra
>>
>>
>>
>> On 10.9.2014 13:44, Sande Gilda wrote:
>>> Coming into this late....
>>>
>>> I agree with Pete. I think the Wiki is a temporary container for
>>> the documentation. As Pete said, we may embed the docs into the
>>> web site or it may be published to the Customer Portal. Similar
>>> to the other documentation, we may also eventually need more
>>> complex structures like tables and graphs and I'm pretty sure we
>>> will want to publish PDFs. I hate to tie ourselves to something
>>> that can't grow with us. The syntax for AsciiDoc is very similar
>>> and I don't find it any more difficult to work with than Markdown.
>>>
>>> I do think we need to be consistent with the documentation and
>>> use the same tooling for all the pages. However, Ondra, if you
>>> feel more comfortable and productive working with Markdown,
>>> please continue to use it as you are doing an amazing job
>>> creating documentation! When you think a page is ready, I am
>>> happy to convert it to AsciiDoc for you. :-)
>>>
>>> On 09/10/2014 06:12 AM, Pete Muir wrote:
>>>> I doubt that the github wiki will be our target output
>>>> platform. We'll likely want to embed them in to the website.
>>>>
>>>> On 9 Sep 2014, at 23:24, Ondrej Zizka <ozizka at redhat.com
>>>> <mailto:ozizka at redhat.com>> wrote:
>>>>
>>>>> Other issues might be GitHub's translator. But IDK what's the
>>>>> main target medium for our docs. Is that GitHub wiki?
>>>>>
>>>>> Ondra
>>>>>
>>>>>
>>>>> On 9.9.2014 13:45, Sande Gilda wrote:
>>>>>> One of Ondra's complaints is the way lists seem to display an
>>>>>> extra paragraph between the items. Take a look at the home
>>>>>> page here: https://github.com/windup/windup/wiki
>>>>>>
>>>>>> Note that the list items are spaced far apart. I search for a
>>>>>> solution, and the only thing I could find was mention of
>>>>>> using |[options="compact"], |but it didn't seem to work.
>>>>>>
>>>>>> Ondra, what other issues did you have.
>>>>>>
>>>>>>
>>>>>> On 09/09/2014 06:39 AM, Pete Muir wrote:
>>>>>>> The big advantages of asciidoc are:
>>>>>>>
>>>>>>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>>>>>>> * generation of pdf and epub is part of the standard toolchain
>>>>>>>
>>>>>>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>>>>>>
>>>>>>> GitHub's support for asciidoc wasn't great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>>>>>>
>>>>>>> I prefer asciidoc links as you just do link:http://redhat.com <http://redhat.com/>[Red Hat's website]. I find this much easier to remember than the weird []() syntax in markdown.
>>>>>>>
>>>>>>> On 9 Sep 2014, at 01:23, Sande Gilda<sgilda at redhat.com> <mailto:sgilda at redhat.com> wrote:
>>>>>>>
>>>>>>>> I'll change everything back to Markdown later this week. Ondra, in the
>>>>>>>> meantime, you can work in Markdown.
>>>>>>>>
>>>>>>>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>>>>>>>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>>>>>>>>
>>>>>>>>> Brad Davis
>>>>>>>>> Red Hat Consulting
>>>>>>>>> Email:bdavis at redhat.com <mailto:bdavis at redhat.com> | c:980.226.7865 <tel:980.226.7865> |http://www.redhat.com <http://www.redhat.com/>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ----- Original Message -----
>>>>>>>>> From: "Ondrej Zizka"<ozizka at redhat.com> <mailto:ozizka at redhat.com>
>>>>>>>>> To: "Sande Gilda"<sgilda at redhat.com> <mailto:sgilda at redhat.com>, "Windup-dev List"<windup-dev at lists.jboss.org> <mailto:windup-dev at lists.jboss.org>
>>>>>>>>> Sent: Monday, September 8, 2014 7:58:20 PM
>>>>>>>>> Subject: Re: [windup-dev] Asciidoc - lists
>>>>>>>>>
>>>>>>>>> For the record: I don't strongly prefer either, only that I only touched
>>>>>>>>> few things in AsciiDoc, and:
>>>>>>>>> 1) certain constructs are quite less readable -> editable in the
>>>>>>>>> source text (e.g. links)
>>>>>>>>> 2) the render results are not satisfactory - things like a bold text
>>>>>>>>> in a lists are not properly implemented on whatever GitHub uses.
>>>>>>>>>
>>>>>>>>> Ondra
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 9.9.2014 01:17, Sande Gilda wrote:
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>>>>>>>>>> really don't know, but I do remember Pete saying AsciiDoc would be
>>>>>>>>>> better for the quickstart README files long ago. And I believe Drupal,
>>>>>>>>>> the new host for documentation, supports AsciiDoc.
>>>>>>>>>>
>>>>>>>>>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>>>>>>>>>> come up with a good reason for sticking with it, I'm fine with going
>>>>>>>>>> back to Markdown if it's easier for everyone.
>>>>>>>>>>
>>>>>>>>>> So, AsciiDoc advocates, please speak up now.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Sande
>>>>>>>>>>
>>>>>>>>>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>>>>>>>>>> Hi Ondra,
>>>>>>>>>>>
>>>>>>>>>>> You're asking me? ;-)
>>>>>>>>>>>
>>>>>>>>>>> I'm totally new to asciidoc. I'll research it and see what I can find
>>>>>>>>>>> out.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Sande
>>>>>>>>>>>
>>>>>>>>>>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>>>>>>>>>>> Hi Sande,
>>>>>>>>>>>>
>>>>>>>>>>>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>>>>>>>>>>>> list tall and breaks the whole page layout.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Ondra
>>>>>>>>> _______________________________________________
>>>>>>>>> windup-dev mailing list
>>>>>>>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>>> _______________________________________________
>>>>>>>> windup-dev mailing list
>>>>>>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>> _______________________________________________
>>>>>>> windup-dev mailing list
>>>>>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> windup-dev mailing list
>>>>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/df6ef5b1/attachment.html
From lincolnbaxter at gmail.com Fri Sep 12 11:48:08 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 12 Sep 2014 11:48:08 -0400
Subject: [windup-dev] Fwd: Re: GitHub problem rendering AsciiDoc lists
In-Reply-To: <54121154.5040205@redhat.com>
References: <discussions/b281008038fa11e4882d991f07d79882/comments/1323980@github.com>
<541204D5.7020005@redhat.com> <54121154.5040205@redhat.com>
Message-ID: <CAEp_U4Eq20xCUW+wnyUGM3w4MKLYZ3PFhS5+spmgPua9MZaz-Q@mail.gmail.com>
GitHub uses Asciidoctor to render their asciidoc files.
One major point of AsciiDoctor is that it allows you to customize your
rendering. If we want custom CSS, we should not use Github Wiki directly,
and instead use something like Redoculous, which is what the Forge website
uses to render its docs and display them in its own CSS:
http://redoculous-lincolnbaxter.rhcloud.com/api/v1/preview?repo=https://github.com/windup/windup.wiki.git&path=/Rules:%20Rules%20Development%20Guide.asciidoc&ref=master
(looks like I need to fix a bug in some of the link handling, but you
should get the idea. It lets you embed docs directly from github into a
webapp: http://forge.jboss.org/document/develop-an-addon )
~Lincoln
On Thu, Sep 11, 2014 at 5:17 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> I posted it to AsciiDoc. But they don't share my opinion that <p> in <li>
> is a wrong idea.
> https://groups.google.com/forum/#!topic/asciidoc/BF9HlACuNjE
>
> They have an unfortunate mix of "DocBook legacy" and forward compatibility.
> But it's a bit configurable. Dan wrote:
>
> It's also pretty each to change by hacking the html5.conf file:
>
> ----
> [paragraph]
> {title?<div class="title">{title}</div>}
> <p class="paragraph{role? {role}}{unbreakable-option? unbreakable}"{id?
> id="{id}"}>
> |
> </p>
> ----
>
> We could ask GitHub to change that for li I guess.
> Or, as I suggested earlier, find out if GitHub allows to apply per-project
> CSS.
>
> Ondra
>
>
>
> On 11.9.2014 22:23, Sande Gilda wrote:
>
> This is interesting. GitHub uses Asciidoctor to render the asciidoc files!
>
> Ondra, where did you report this issue? If you didn't report it to
> Asciidoctor, I will.
>
>
> -------- Original Message -------- Subject: Re: GitHub problem rendering
> AsciiDoc lists Date: Thu, 11 Sep 2014 10:08:00 -0700 From: Jess Hosman
> (GitHub Staff) <support at github.com> <support at github.com> To: Sande Gilda
> <sgilda at redhat.com> <sgilda at redhat.com>
>
> Hi Sande,
>
> Thanks for your patience. After some digging, it looks like we use the third party tool Asciidoctor [1] for the conversion, which is where the extra `<p>` tags are coming from. I'd recommend opening an issue in the Asciidoctor repo about this. Once changes are made there, we should be able to pull them into GitHub.
>
> Cheers,
> Jess
>
> [1]: https://github.com/asciidoctor/asciidoctor
>
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/71d7be4e/attachment-0001.html
From sgilda at redhat.com Fri Sep 12 11:51:05 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 12 Sep 2014 11:51:05 -0400
Subject: [windup-dev] Fwd: Re: GitHub problem rendering AsciiDoc lists
In-Reply-To: <CAEp_U4Eq20xCUW+wnyUGM3w4MKLYZ3PFhS5+spmgPua9MZaz-Q@mail.gmail.com>
References: <discussions/b281008038fa11e4882d991f07d79882/comments/1323980@github.com> <541204D5.7020005@redhat.com> <54121154.5040205@redhat.com>
<CAEp_U4Eq20xCUW+wnyUGM3w4MKLYZ3PFhS5+spmgPua9MZaz-Q@mail.gmail.com>
Message-ID: <54131669.8000009@redhat.com>
Agreed. At some point I'm thinking we need to place these pages in 'doc'
or some other directory so we can build it for the portal or where ever
it will reside.. I had thought Asciidoctor, but if Redoculous is better,
that's fine.
On 09/12/2014 11:48 AM, Lincoln Baxter, III wrote:
> GitHub uses Asciidoctor to render their asciidoc files.
>
> One major point of AsciiDoctor is that it allows you to customize your
> rendering. If we want custom CSS, we should not use Github Wiki
> directly, and instead use something like Redoculous, which is what the
> Forge website uses to render its docs and display them in its own CSS:
>
> http://redoculous-lincolnbaxter.rhcloud.com/api/v1/preview?repo=https://github.com/windup/windup.wiki.git&path=/Rules:%20Rules%20Development%20Guide.asciidoc&ref=master
>
> (looks like I need to fix a bug in some of the link handling, but you
> should get the idea. It lets you embed docs directly from github into
> a webapp: http://forge.jboss.org/document/develop-an-addon )
>
> ~Lincoln
>
>
>
>
>
> On Thu, Sep 11, 2014 at 5:17 PM, Ondrej Zizka <ozizka at redhat.com
> <mailto:ozizka at redhat.com>> wrote:
>
> I posted it to AsciiDoc. But they don't share my opinion that <p>
> in <li> is a wrong idea.
> https://groups.google.com/forum/#!topic/asciidoc/BF9HlACuNjE
> <https://groups.google.com/forum/#%21topic/asciidoc/BF9HlACuNjE>
>
> They have an unfortunate mix of "DocBook legacy" and forward
> compatibility.
> But it's a bit configurable. Dan wrote:
>
> It's also pretty each to change by hacking the html5.conf file:
>
> ----
> [paragraph]
> {title?<div class="title">{title}</div>}
> <p class="paragraph{role? {role}}{unbreakable-option?
> unbreakable}"{id? id="{id}"}>
> |
> </p>
> ----
>
> We could ask GitHub to change that for li I guess.
> Or, as I suggested earlier, find out if GitHub allows to apply
> per-project CSS.
>
> Ondra
>
>
>
> On 11.9.2014 22:23, Sande Gilda wrote:
>> This is interesting. GitHub uses Asciidoctor to render the
>> asciidoc files!
>>
>> Ondra, where did you report this issue? If you didn't report it
>> to Asciidoctor, I will.
>>
>>
>> -------- Original Message --------
>> Subject: Re: GitHub problem rendering AsciiDoc lists
>> Date: Thu, 11 Sep 2014 10:08:00 -0700
>> From: Jess Hosman (GitHub Staff) <support at github.com>
>> <mailto:support at github.com>
>> To: Sande Gilda <sgilda at redhat.com> <mailto:sgilda at redhat.com>
>>
>>
>>
>> Hi Sande,
>>
>> Thanks for your patience. After some digging, it looks like we use the third party tool Asciidoctor [1] for the conversion, which is where the extra `<p>` tags are coming from. I'd recommend opening an issue in the Asciidoctor repo about this. Once changes are made there, we should be able to pull them into GitHub.
>>
>> Cheers,
>> Jess
>>
>> [1]:https://github.com/asciidoctor/asciidoctor
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/865fddce/attachment.html
From lincolnbaxter at gmail.com Fri Sep 12 12:52:02 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 12 Sep 2014 12:52:02 -0400
Subject: [windup-dev] Fwd: Re: GitHub problem rendering AsciiDoc lists
In-Reply-To: <54131669.8000009@redhat.com>
References: <discussions/b281008038fa11e4882d991f07d79882/comments/1323980@github.com>
<541204D5.7020005@redhat.com> <54121154.5040205@redhat.com>
<CAEp_U4Eq20xCUW+wnyUGM3w4MKLYZ3PFhS5+spmgPua9MZaz-Q@mail.gmail.com>
<54131669.8000009@redhat.com>
Message-ID: <CAEp_U4GPPQS2+=6y1TSYMS75MhdNm4ePqa_=FABgDUrraG3bgA@mail.gmail.com>
Redoculous just uses asciidoctor to render things from github on the fly.
On Fri, Sep 12, 2014 at 11:51 AM, Sande Gilda <sgilda at redhat.com> wrote:
> Agreed. At some point I'm thinking we need to place these pages in 'doc'
> or some other directory so we can build it for the portal or where ever it
> will reside.. I had thought Asciidoctor, but if Redoculous is better,
> that's fine.
>
>
> On 09/12/2014 11:48 AM, Lincoln Baxter, III wrote:
>
> GitHub uses Asciidoctor to render their asciidoc files.
>
> One major point of AsciiDoctor is that it allows you to customize your
> rendering. If we want custom CSS, we should not use Github Wiki directly,
> and instead use something like Redoculous, which is what the Forge website
> uses to render its docs and display them in its own CSS:
>
>
> http://redoculous-lincolnbaxter.rhcloud.com/api/v1/preview?repo=https://github.com/windup/windup.wiki.git&path=/Rules:%20Rules%20Development%20Guide.asciidoc&ref=master
>
> (looks like I need to fix a bug in some of the link handling, but you
> should get the idea. It lets you embed docs directly from github into a
> webapp: http://forge.jboss.org/document/develop-an-addon )
>
> ~Lincoln
>
>
>
>
>
> On Thu, Sep 11, 2014 at 5:17 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
>
>> I posted it to AsciiDoc. But they don't share my opinion that <p> in
>> <li> is a wrong idea.
>> https://groups.google.com/forum/#!topic/asciidoc/BF9HlACuNjE
>>
>> They have an unfortunate mix of "DocBook legacy" and forward
>> compatibility.
>> But it's a bit configurable. Dan wrote:
>>
>> It's also pretty each to change by hacking the html5.conf file:
>>
>> ----
>> [paragraph]
>> {title?<div class="title">{title}</div>}
>> <p class="paragraph{role? {role}}{unbreakable-option? unbreakable}"{id?
>> id="{id}"}>
>> |
>> </p>
>> ----
>>
>> We could ask GitHub to change that for li I guess.
>> Or, as I suggested earlier, find out if GitHub allows to apply
>> per-project CSS.
>>
>> Ondra
>>
>>
>>
>> On 11.9.2014 22:23, Sande Gilda wrote:
>>
>> This is interesting. GitHub uses Asciidoctor to render the asciidoc
>> files!
>>
>> Ondra, where did you report this issue? If you didn't report it to
>> Asciidoctor, I will.
>>
>>
>> -------- Original Message -------- Subject: Re: GitHub problem
>> rendering AsciiDoc lists Date: Thu, 11 Sep 2014 10:08:00 -0700 From: Jess
>> Hosman (GitHub Staff) <support at github.com> <support at github.com> To: Sande
>> Gilda <sgilda at redhat.com> <sgilda at redhat.com>
>>
>> Hi Sande,
>>
>> Thanks for your patience. After some digging, it looks like we use the third party tool Asciidoctor [1] for the conversion, which is where the extra `<p>` tags are coming from. I'd recommend opening an issue in the Asciidoctor repo about this. Once changes are made there, we should be able to pull them into GitHub.
>>
>> Cheers,
>> Jess
>>
>> [1]: https://github.com/asciidoctor/asciidoctor
>>
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/d084f30e/attachment.html
From lincolnbaxter at gmail.com Fri Sep 12 12:56:24 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 12 Sep 2014 12:56:24 -0400
Subject: [windup-dev] Asciidoc - lists
In-Reply-To: <54131543.50909@redhat.com>
References: <540E2A10.4000704@redhat.com> <540E2DD1.80203@redhat.com>
<540E38EC.9000802@redhat.com> <540E429C.1080004@redhat.com>
<216398716.28241481.1410221573065.JavaMail.zimbra@redhat.com>
<540E488F.90105@redhat.com>
<C25BCFE3-C0E5-4269-8566-989A4D87013D@redhat.com>
<540EE847.9010507@redhat.com> <540F7E2E.30504@redhat.com>
<589F1405-476D-4BD4-AB65-57E17A7FAD05@redhat.com>
<541039A1.8060204@redhat.com> <54111158.70901@redhat.com>
<541183F1.9000405@redhat.com>
<CAEp_U4H_fc3c4kiRzCnyqjfCZefO476Zf29bWA=o8Dmah9twQQ@mail.gmail.com>
<54131543.50909@redhat.com>
Message-ID: <CAEp_U4G9Xf_LdVFxuz76Tuo7=1H8=mAyNsz_JD1DtitPs3YCCQ@mail.gmail.com>
Ok, if that works for you two, that's fine with me.
On Fri, Sep 12, 2014 at 11:46 AM, Sande Gilda <sgilda at redhat.com> wrote:
> Hi Lincoln,
>
> The plan is definitely to make them all Asciidoc format. Ondra writes a
> lot of doc and if he feels more productive using Markdown when creating a
> new document, that's fine by me. When he's finished with a topic, I will
> convert it to Asciidoc. Then he will have to make any updates using the
> Asciidoc format. So everything will be Asciidoc.
>
> Thanks,
> Sande
>
>
> On 09/12/2014 11:30 AM, Lincoln Baxter, III wrote:
>
> Coming in to this late, I'd prefer to stick with one format, and it seems
> like we (as JBoss) are moving toward asciidoc, so I think we should stick
> with that (for all of the previously stated reasons.)
>
> On Thu, Sep 11, 2014 at 7:13 AM, Sande Gilda <sgilda at redhat.com> wrote:
>
>> Hi Ondra,
>>
>> Of course! As I said on IRC, what ever is easiest for you is fine by me.
>> :-)
>>
>> Thanks,
>> Sande
>>
>>
>> On 09/10/2014 11:04 PM, Ondrej Zizka wrote:
>>
>> Okay, in that case, let's do AsciiDoc, except for the few pages where I
>> am just storing temp info before converting to a real page, mostly "Dev:",
>> because that's changing often, shouldn't go to any official docs, and I
>> edit faster in Markdown. These pages will have "Draft" at the top. But I'll
>> update the existing pages in AsciiDoc.
>>
>> Will that work fine?
>>
>> Regards,
>> Ondra
>>
>>
>>
>> On 10.9.2014 13:44, Sande Gilda wrote:
>>
>> Coming into this late....
>>
>> I agree with Pete. I think the Wiki is a temporary container for the
>> documentation. As Pete said, we may embed the docs into the web site or it
>> may be published to the Customer Portal. Similar to the other
>> documentation, we may also eventually need more complex structures like
>> tables and graphs and I'm pretty sure we will want to publish PDFs. I hate
>> to tie ourselves to something that can't grow with us. The syntax for
>> AsciiDoc is very similar and I don't find it any more difficult to work
>> with than Markdown.
>>
>> I do think we need to be consistent with the documentation and use the
>> same tooling for all the pages. However, Ondra, if you feel more
>> comfortable and productive working with Markdown, please continue to use it
>> as you are doing an amazing job creating documentation! When you think a
>> page is ready, I am happy to convert it to AsciiDoc for you. :-)
>>
>> On 09/10/2014 06:12 AM, Pete Muir wrote:
>>
>> I doubt that the github wiki will be our target output platform. We?ll
>> likely want to embed them in to the website.
>>
>> On 9 Sep 2014, at 23:24, Ondrej Zizka <ozizka at redhat.com> wrote:
>>
>> Other issues might be GitHub's translator. But IDK what's the main
>> target medium for our docs. Is that GitHub wiki?
>>
>> Ondra
>>
>>
>> On 9.9.2014 13:45, Sande Gilda wrote:
>>
>> One of Ondra's complaints is the way lists seem to display an extra
>> paragraph between the items. Take a look at the home page here:
>> https://github.com/windup/windup/wiki
>>
>> Note that the list items are spaced far apart. I search for a solution,
>> and the only thing I could find was mention of using [options="compact"],
>> but it didn't seem to work.
>>
>> Ondra, what other issues did you have.
>>
>>
>> On 09/09/2014 06:39 AM, Pete Muir wrote:
>>
>> The big advantages of asciidoc are:
>>
>> * more comprehensive markup (e.g. tables, definition lists are supported as standard)
>> * generation of pdf and epub is part of the standard toolchain
>>
>> Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.
>>
>> GitHub?s support for asciidoc wasn?t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.
>>
>> I prefer asciidoc links as you just do link:http://redhat.com[Red Hat?s website]. I find this much easier to remember than the weird []() syntax in markdown.
>>
>> On 9 Sep 2014, at 01:23, Sande Gilda <sgilda at redhat.com> <sgilda at redhat.com> wrote:
>>
>>
>> I'll change everything back to Markdown later this week. Ondra, in the
>> meantime, you can work in Markdown.
>>
>> On 09/08/2014 08:12 PM, Brad Davis wrote:
>>
>> I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.
>>
>> Brad Davis
>> Red Hat Consulting
>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>
>>
>> ----- Original Message -----
>> From: "Ondrej Zizka" <ozizka at redhat.com> <ozizka at redhat.com>
>> To: "Sande Gilda" <sgilda at redhat.com> <sgilda at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org> <windup-dev at lists.jboss.org>
>> Sent: Monday, September 8, 2014 7:58:20 PM
>> Subject: Re: [windup-dev] Asciidoc - lists
>>
>> For the record: I don't strongly prefer either, only that I only touched
>> few things in AsciiDoc, and:
>> 1) certain constructs are quite less readable -> editable in the
>> source text (e.g. links)
>> 2) the render results are not satisfactory - things like a bold text
>> in a lists are not properly implemented on whatever GitHub uses.
>>
>> Ondra
>>
>>
>> On 9.9.2014 01:17, Sande Gilda wrote:
>>
>> Hi all,
>>
>> Ondra asked me about the advantages of AsciiDoc over Markdown. I
>> really don't know, but I do remember Pete saying AsciiDoc would be
>> better for the quickstart README files long ago. And I believe Drupal,
>> the new host for documentation, supports AsciiDoc.
>>
>> TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
>> come up with a good reason for sticking with it, I'm fine with going
>> back to Markdown if it's easier for everyone.
>>
>> So, AsciiDoc advocates, please speak up now.
>>
>> Thanks,
>> Sande
>>
>> On 09/08/2014 06:29 PM, Sande Gilda wrote:
>>
>> Hi Ondra,
>>
>> You're asking me? ;-)
>>
>> I'm totally new to asciidoc. I'll research it and see what I can find
>> out.
>>
>> Thanks,
>> Sande
>>
>> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>>
>> Hi Sande,
>>
>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>> list tall and breaks the whole page layout.
>>
>> Thanks,
>> Ondra
>>
>> _______________________________________________
>> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/8ab8f956/attachment-0001.html
From mbriskar at redhat.com Sat Sep 13 13:03:29 2014
From: mbriskar at redhat.com (Matej Briskar)
Date: Sat, 13 Sep 2014 13:03:29 -0400 (EDT)
Subject: [windup-dev] Further Iteration simplification
In-Reply-To: <811843967.37517888.1410627303574.JavaMail.zimbra@redhat.com>
Message-ID: <140881225.37518491.1410627809318.JavaMail.zimbra@redhat.com>
Hi,
after migrating the XML rules, I have figured out some simplification that I strongly suggest.
The change is a bigger one, so I would like to know your opinions. I'd like to start working on this as soon as possible.
The whole issue is described here (it is technical):
https://issues.jboss.org/browse/WINDUP-200
From mbriskar at redhat.com Sat Sep 13 13:11:55 2014
From: mbriskar at redhat.com (Matej Briskar)
Date: Sat, 13 Sep 2014 13:11:55 -0400 (EDT)
Subject: [windup-dev] Further Iteration simplification - URL Correction
In-Reply-To: <140881225.37518491.1410627809318.JavaMail.zimbra@redhat.com>
References: <140881225.37518491.1410627809318.JavaMail.zimbra@redhat.com>
Message-ID: <482922129.37518716.1410628315696.JavaMail.zimbra@redhat.com>
Sorry, correction.
It is the WINDUP-288: https://issues.jboss.org/browse/WINDUP-288
----- Original Message -----
From: "Matej Briskar" <mbriskar at redhat.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Saturday, September 13, 2014 7:03:29 PM
Subject: Further Iteration simplification
Hi,
after migrating the XML rules, I have figured out some simplification that I strongly suggest.
The change is a bigger one, so I would like to know your opinions. I'd like to start working on this as soon as possible.
The whole issue is described here (it is technical):
https://issues.jboss.org/browse/WINDUP-200
From ozizka at redhat.com Sun Sep 14 19:30:50 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 15 Sep 2014 01:30:50 +0200
Subject: [windup-dev] Performance - Forge scanning through Weld
In-Reply-To: <CAEp_U4H8Pw-oGuX_fcg53FvnZOPrktt8gHABw_Opdmq3DgeTXQ@mail.gmail.com>
References: <5410EBDF.4040208@redhat.com>
<CAEp_U4H8Pw-oGuX_fcg53FvnZOPrktt8gHABw_Opdmq3DgeTXQ@mail.gmail.com>
Message-ID: <5416252A.7080904@redhat.com>
Are you saying that Furnace change would be needed? I thought Weld
supports Jandex out of the box and transparently. If not, let's keep as
a performance reserve.
Ondra
On 12.9.2014 17:29, Lincoln Baxter, III wrote:
> I would be happy to see an improvement in the furnace-cdi container to
> support this, when we have time to work on it. Right now it's not
> critical, but it would be nice once things settle down after the
> tech-preview release.
>
> On Wed, Sep 10, 2014 at 8:25 PM, Ondrej Zizka <ozizka at redhat.com
> <mailto:ozizka at redhat.com>> wrote:
>
> It seems that Forge spends considerable time (around 10 seconds on my
> laptop) scanning the classes for annotated types;
> Somehow related to
> org.jboss.forge.furnace.container.cdi.impl.ContainerServiceExtension.processRemoteServiceTypes()
>
> This repeats for each test in which Forge is involved.
>
> Could this scanning be sped up using jandex? If we have 40 tests, then
> it would buy us over 5 minutes.
>
> Ondra
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140915/5181f639/attachment.html
From ozizka at redhat.com Sun Sep 14 19:34:44 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 15 Sep 2014 01:34:44 +0200
Subject: [windup-dev] Double building?
In-Reply-To: <CAEp_U4Ek_tiAT7MBaC26+ozb=ntx240uqjQXd8CK2TsSx_X72w@mail.gmail.com>
References: <540FB65D.7070704@redhat.com>
<CAEp_U4Ek_tiAT7MBaC26+ozb=ntx240uqjQXd8CK2TsSx_X72w@mail.gmail.com>
Message-ID: <54162614.6020709@redhat.com>
If it's fixed, then just out of curiosity - mvn install of what? When I
did `mvn install` over the whole project, e.g. graph should be already
`mvn install`ed before it gets to windup-tests module. So I wonder why I
was seeing behavior which I'd classify as forge not picking up the
freshly built artifact.
Thanks,
Ondra
On 12.9.2014 13:09, Lincoln Baxter, III wrote:
> Sorry, I missed this mail until now. The issue is that <optional>
> maven deps were not being picked up by the maven reactor build without
> performing the 'mvn install' step. This issue FORGE-2003, has been
> resolved and is now in Forge 2.10.0.Final - I will do an update and
> send a PR to fix this in Windup.
>
> On Tue, Sep 9, 2014 at 10:24 PM, Ondrej Zizka <ozizka at redhat.com
> <mailto:ozizka at redhat.com>> wrote:
>
> Hi (Lincoln),
>
> could you please describe the issue with forge resolver more closely?
> I think I was hit by that few times - the app is behaving differently
> when I build only one module, then run test with other, and in
> whole run.
>
> What's the cause and what exactly does it cause - what should I
> count with?
>
> On unrelated note - I changed few things, rebuilt few times, and now
> instead of
> HintsClassificationsTest.testIterationVariableResolving:162
> expected:<3> but was:<0>
> I have
> HintsClassificationsTest.testIterationVariableResolving:162
> expected:<3> but was:<4>
> Which is good - the whole run sticks with the same graph :)
> But a bit weirder - having more nodes than the test expects...
> More tomorrow.
>
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140915/952b850c/attachment.html
From robb.greathouse at redhat.com Mon Sep 15 11:26:52 2014
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Mon, 15 Sep 2014 11:26:52 -0400 (EDT)
Subject: [windup-dev] Performance - Forge scanning through Weld
In-Reply-To: <5416252A.7080904@redhat.com>
References: <5410EBDF.4040208@redhat.com>
<CAEp_U4H8Pw-oGuX_fcg53FvnZOPrktt8gHABw_Opdmq3DgeTXQ@mail.gmail.com>
<5416252A.7080904@redhat.com>
Message-ID: <1229087930.22585767.1410794812109.JavaMail.zimbra@redhat.com>
How is this a Windup issue?
Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> Are you saying that Furnace change would be needed? I thought Weld supports
> Jandex out of the box and transparently. If not, let's keep as a performance
> reserve.
> Ondra
> On 12.9.2014 17:29, Lincoln Baxter, III wrote:
> > I would be happy to see an improvement in the furnace-cdi container to
> > support this, when we have time to work on it. Right now it's not critical,
> > but it would be nice once things settle down after the tech-preview
> > release.
>
> > On Wed, Sep 10, 2014 at 8:25 PM, Ondrej Zizka < ozizka at redhat.com > wrote:
>
> > > It seems that Forge spends considerable time (around 10 seconds on my
> >
>
> > > laptop) scanning the classes for annotated types;
> >
>
> > > Somehow related to
> >
>
> > > org.jboss.forge.furnace.container.cdi.impl.ContainerServiceExtension.processRemoteServiceTypes()
> >
>
> > > This repeats for each test in which Forge is involved.
> >
>
> > > Could this scanning be sped up using jandex? If we have 40 tests, then
> >
>
> > > it would buy us over 5 minutes.
> >
>
> > > Ondra
> >
>
> > > _______________________________________________
> >
>
> > > windup-dev mailing list
> >
>
> > > windup-dev at lists.jboss.org
> >
>
> > > https://lists.jboss.org/mailman/listinfo/windup-dev
> >
>
> > --
>
> > Lincoln Baxter, III
>
> > http://ocpsoft.org
>
> > "Simpler is better."
>
> > _______________________________________________
>
> > windup-dev mailing list windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140915/776061d6/attachment.html
From ozizka at redhat.com Tue Sep 16 09:31:05 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 16 Sep 2014 15:31:05 +0200
Subject: [windup-dev] Performance - Forge scanning through Weld
In-Reply-To: <1229087930.22585767.1410794812109.JavaMail.zimbra@redhat.com>
References: <5410EBDF.4040208@redhat.com> <CAEp_U4H8Pw-oGuX_fcg53FvnZOPrktt8gHABw_Opdmq3DgeTXQ@mail.gmail.com> <5416252A.7080904@redhat.com>
<1229087930.22585767.1410794812109.JavaMail.zimbra@redhat.com>
Message-ID: <54183B99.4010803@redhat.com>
Windup core startup takes few seconds more.
On 15.9.2014 17:26, Robb Greathouse wrote:
> How is this a Windup issue?
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------------------------------------------------
>
> Are you saying that Furnace change would be needed? I thought Weld
> supports Jandex out of the box and transparently. If not, let's
> keep as a performance reserve.
>
> Ondra
>
>
>
> On 12.9.2014 17:29, Lincoln Baxter, III wrote:
>
> I would be happy to see an improvement in the furnace-cdi
> container to support this, when we have time to work on it.
> Right now it's not critical, but it would be nice once things
> settle down after the tech-preview release.
>
> On Wed, Sep 10, 2014 at 8:25 PM, Ondrej Zizka
> <ozizka at redhat.com <mailto:ozizka at redhat.com>> wrote:
>
> It seems that Forge spends considerable time (around 10
> seconds on my
> laptop) scanning the classes for annotated types;
> Somehow related to
> org.jboss.forge.furnace.container.cdi.impl.ContainerServiceExtension.processRemoteServiceTypes()
>
> This repeats for each test in which Forge is involved.
>
> Could this scanning be sped up using jandex? If we have 40
> tests, then
> it would buy us over 5 minutes.
>
> Ondra
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140916/0a5dc8f7/attachment-0001.html
From lincolnbaxter at gmail.com Wed Sep 17 11:29:12 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 17 Sep 2014 11:29:12 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2014-09-17
Message-ID: <CAEp_U4HmAkGwrbf2QXoBoNVzo0J916F=o1YnSXxxY+a5s5ZfFw@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-17-14.32.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-17-14.32.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-17-14.32.log.html
Meeting summary
---------------
* Agenda (lincolnthree, 14:32:05)
* Status Reports (lincolnthree, 14:36:00)
* I've been handling JBDS release stuff, as well as meeting with
Pete/BU to discuss planning and trying to get good requirements out
of them (lincolnthree, 14:36:57)
* I've also worked on refactoring and merging for WINDUP-253 and
WINDUP-222 (lincolnthree, 14:37:13)
* I'll be continuing to work on WINDUP-222 as well as more meetings
(yayyyy!) (lincolnthree, 14:37:32)
* Status: I finished the refactoring and now working on single class
decompilation. It's almost working. It could be ready tomorrow.
(ozizka, 14:37:54)
* I will update the tutorial and example rule (quickstart) (ozizka,
14:38:50)
* It was shown that there was really one commit that got lost from the
xmls. With Licoln we got it together and PR is there (mbriskar,
14:40:41)
* jsightler WINDUP-271 - BUG - addTypeToElement does not check for
duplicate values - This was hurting performance and causing some
items to be duplicated in reports (lincolnthree, 14:41:35)
* jsightler WINDUP-245 - Catalog properties file contents, and report
on all properties files in the overview report (lincolnthree,
14:41:35)
* jsightler WINDUP-243 - Include a hash of all archives in the report
(lincolnthree, 14:41:35)
* jsightler WINDUP-242 - Import some hibernate metadata (from mapping
files and cfg files) into the graph (lincolnthree, 14:41:35)
* jsightler The coming week I will focus on missing gaps for the
upcoming preview/beta. This includes making sure that
classifications/hints are displaying properly in the reports, and
making sure that estimated effort levels appear in the reports as
well. (lincolnthree, 14:41:45)
* Release Status (lincolnthree, 14:41:53)
* WINDUP-280: we have 3 open sub-tasks, one of which is a business
task and we are helping them with it. (lincolnthree, 14:43:14)
* I think we are looking good/on schedule to release as planned.
(lincolnthree, 14:43:28)
* We will be doing some planning with BU to do better requirements for
future releases. (lincolnthree, 14:44:10)
Meeting ended at 15:01:43 UTC.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140917/78d614ab/attachment.html
From lincolnbaxter at gmail.com Wed Sep 17 17:29:21 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 17 Sep 2014 17:29:21 -0400
Subject: [windup-dev] Double building?
In-Reply-To: <54162614.6020709@redhat.com>
References: <540FB65D.7070704@redhat.com>
<CAEp_U4Ek_tiAT7MBaC26+ozb=ntx240uqjQXd8CK2TsSx_X72w@mail.gmail.com>
<54162614.6020709@redhat.com>
Message-ID: <CAEp_U4Ew2crVVkH13CZkn8j-JvBn3G4kzzX5SUN4+4TrsiUu5A@mail.gmail.com>
Please explain this behavior in more detail. Steps to reproduce. I will try
to debug, but a bit busy at the moment to work on a non-critical issue :)
so it might wait.
On Sun, Sep 14, 2014 at 7:34 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> If it's fixed, then just out of curiosity - mvn install of what? When I
> did `mvn install` over the whole project, e.g. graph should be already `mvn
> install`ed before it gets to windup-tests module. So I wonder why I was
> seeing behavior which I'd classify as forge not picking up the freshly
> built artifact.
>
> Thanks,
> Ondra
>
>
>
> On 12.9.2014 13:09, Lincoln Baxter, III wrote:
>
> Sorry, I missed this mail until now. The issue is that <optional> maven
> deps were not being picked up by the maven reactor build without performing
> the 'mvn install' step. This issue FORGE-2003, has been resolved and is now
> in Forge 2.10.0.Final - I will do an update and send a PR to fix this in
> Windup.
>
> On Tue, Sep 9, 2014 at 10:24 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
>
>> Hi (Lincoln),
>>
>> could you please describe the issue with forge resolver more closely?
>> I think I was hit by that few times - the app is behaving differently
>> when I build only one module, then run test with other, and in whole run.
>>
>> What's the cause and what exactly does it cause - what should I count
>> with?
>>
>> On unrelated note - I changed few things, rebuilt few times, and now
>> instead of
>> HintsClassificationsTest.testIterationVariableResolving:162
>> expected:<3> but was:<0>
>> I have
>> HintsClassificationsTest.testIterationVariableResolving:162
>> expected:<3> but was:<4>
>> Which is good - the whole run sticks with the same graph :)
>> But a bit weirder - having more nodes than the test expects...
>> More tomorrow.
>>
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140917/23b14e70/attachment.html
From ozizka at redhat.com Thu Sep 18 13:21:33 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 18 Sep 2014 19:21:33 +0200
Subject: [windup-dev] Double building?
In-Reply-To: <CAEp_U4Ew2crVVkH13CZkn8j-JvBn3G4kzzX5SUN4+4TrsiUu5A@mail.gmail.com>
References: <540FB65D.7070704@redhat.com> <CAEp_U4Ek_tiAT7MBaC26+ozb=ntx240uqjQXd8CK2TsSx_X72w@mail.gmail.com> <54162614.6020709@redhat.com>
<CAEp_U4Ew2crVVkH13CZkn8j-JvBn3G4kzzX5SUN4+4TrsiUu5A@mail.gmail.com>
Message-ID: <541B149D.30208@redhat.com>
I will get back to it when it occurs again, which is typically when
figuring out why something doesn't work, which I believe will be soon :)
On 17.9.2014 23:29, Lincoln Baxter, III wrote:
> Please explain this behavior in more detail. Steps to reproduce. I
> will try to debug, but a bit busy at the moment to work on a
> non-critical issue :) so it might wait.
>
> On Sun, Sep 14, 2014 at 7:34 PM, Ondrej Zizka <ozizka at redhat.com
> <mailto:ozizka at redhat.com>> wrote:
>
> If it's fixed, then just out of curiosity - mvn install of what?
> When I did `mvn install` over the whole project, e.g. graph should
> be already `mvn install`ed before it gets to windup-tests module.
> So I wonder why I was seeing behavior which I'd classify as forge
> not picking up the freshly built artifact.
>
> Thanks,
> Ondra
>
>
>
> On 12.9.2014 13:09, Lincoln Baxter, III wrote:
>> Sorry, I missed this mail until now. The issue is that <optional>
>> maven deps were not being picked up by the maven reactor build
>> without performing the 'mvn install' step. This issue FORGE-2003,
>> has been resolved and is now in Forge 2.10.0.Final - I will do an
>> update and send a PR to fix this in Windup.
>>
>> On Tue, Sep 9, 2014 at 10:24 PM, Ondrej Zizka <ozizka at redhat.com
>> <mailto:ozizka at redhat.com>> wrote:
>>
>> Hi (Lincoln),
>>
>> could you please describe the issue with forge resolver more
>> closely?
>> I think I was hit by that few times - the app is behaving
>> differently
>> when I build only one module, then run test with other, and
>> in whole run.
>>
>> What's the cause and what exactly does it cause - what should
>> I count with?
>>
>> On unrelated note - I changed few things, rebuilt few times,
>> and now
>> instead of
>> HintsClassificationsTest.testIterationVariableResolving:162
>> expected:<3> but was:<0>
>> I have
>> HintsClassificationsTest.testIterationVariableResolving:162
>> expected:<3> but was:<4>
>> Which is good - the whole run sticks with the same graph :)
>> But a bit weirder - having more nodes than the test expects...
>> More tomorrow.
>>
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140918/2424c261/attachment.html
From sgilda at redhat.com Thu Sep 18 14:56:20 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 18 Sep 2014 14:56:20 -0400
Subject: [windup-dev] Windup terminology question
Message-ID: <541B2AD4.1010008@redhat.com>
Ondra and I have created a glossary on the Windup Wiki to document
terminology that is used by Windup. The goal is to finalize the correct
terms we want to use in Windup and avoid confusion down the road.
One of the open issues is whether to describe a "ruleset" (formerly
referred to as "rulebase") as a "Forge add-on" or as a "Windup plug-in".
Does anyone have a preference?
The glossary page is located here:
https://github.com/windup/windup/wiki/Glossary. As you come across other
Windup terms, feel free to update the page directly or email/ping me so
that we include them on that page.
Robb, I included some terms from your presentation and took an educated
guess at the meanings. Please let me know if they are incorrect.
Thanks,
Sande
From pmuir at redhat.com Thu Sep 18 15:58:17 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 18 Sep 2014 20:58:17 +0100
Subject: [windup-dev] Windup terminology question
In-Reply-To: <541B2AD4.1010008@redhat.com>
References: <541B2AD4.1010008@redhat.com>
Message-ID: <DCEDEA2B-458B-4E34-A370-771DCBBA856F@redhat.com>
On 18 Sep 2014, at 19:56, Sande Gilda <sgilda at redhat.com> wrote:
> Ondra and I have created a glossary on the Windup Wiki to document terminology that is used by Windup. The goal is to finalize the correct terms we want to use in Windup and avoid confusion down the road.
>
> One of the open issues is whether to describe a "ruleset" (formerly referred to as "rulebase") as a "Forge add-on" or as a "Windup plug-in". Does anyone have a preference?
I prefer ?ruleset? ;-) IOW I don?t think either those are the right description.
>
> The glossary page is located here: https://github.com/windup/windup/wiki/Glossary. As you come across other Windup terms, feel free to update the page directly or email/ping me so that we include them on that page.
>
> Robb, I included some terms from your presentation and took an educated guess at the meanings. Please let me know if they are incorrect.
>
> Thanks,
> Sande
>
From sgilda at redhat.com Thu Sep 18 16:40:02 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 18 Sep 2014 16:40:02 -0400
Subject: [windup-dev] Windup terminology question
In-Reply-To: <DCEDEA2B-458B-4E34-A370-771DCBBA856F@redhat.com>
References: <541B2AD4.1010008@redhat.com>
<DCEDEA2B-458B-4E34-A370-771DCBBA856F@redhat.com>
Message-ID: <541B4322.4070209@redhat.com>
On 09/18/2014 03:58 PM, Pete Muir wrote:
> On 18 Sep 2014, at 19:56, Sande Gilda <sgilda at redhat.com> wrote:
>
>> Ondra and I have created a glossary on the Windup Wiki to document terminology that is used by Windup. The goal is to finalize the correct terms we want to use in Windup and avoid confusion down the road.
>>
>> One of the open issues is whether to describe a "ruleset" (formerly referred to as "rulebase") as a "Forge add-on" or as a "Windup plug-in". Does anyone have a preference?
> I prefer ?ruleset? ;-) IOW I don?t think either those are the right description.
We already decided on ruleset over rulebase, so I'm glad you agree.
How should we describe a ruleset? Won't customers be able to create
their own?
>> The glossary page is located here: https://github.com/windup/windup/wiki/Glossary. As you come across other Windup terms, feel free to update the page directly or email/ping me so that we include them on that page.
>>
>> Robb, I included some terms from your presentation and took an educated guess at the meanings. Please let me know if they are incorrect.
>>
>> Thanks,
>> Sande
>>
From pmuir at redhat.com Thu Sep 18 17:41:17 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 18 Sep 2014 22:41:17 +0100
Subject: [windup-dev] Windup terminology question
In-Reply-To: <541B4322.4070209@redhat.com>
References: <541B2AD4.1010008@redhat.com>
<DCEDEA2B-458B-4E34-A370-771DCBBA856F@redhat.com>
<541B4322.4070209@redhat.com>
Message-ID: <D2B59347-6B7F-491B-9A3A-8002FD72DD18@redhat.com>
On 18 Sep 2014, at 21:40, Sande Gilda <sgilda at redhat.com> wrote:
>
> On 09/18/2014 03:58 PM, Pete Muir wrote:
>> On 18 Sep 2014, at 19:56, Sande Gilda <sgilda at redhat.com> wrote:
>>
>>> Ondra and I have created a glossary on the Windup Wiki to document terminology that is used by Windup. The goal is to finalize the correct terms we want to use in Windup and avoid confusion down the road.
>>>
>>> One of the open issues is whether to describe a "ruleset" (formerly referred to as "rulebase") as a "Forge add-on" or as a "Windup plug-in". Does anyone have a preference?
>> I prefer ?ruleset? ;-) IOW I don?t think either those are the right description.
> We already decided on ruleset over rulebase, so I'm glad you agree.
>
> How should we describe a ruleset? Won't customers be able to create their own?
I would describe a ruleset as a ruleset, or perhaps a ?collection rules packaged as a JAR??
>>> The glossary page is located here: https://github.com/windup/windup/wiki/Glossary. As you come across other Windup terms, feel free to update the page directly or email/ping me so that we include them on that page.
>>>
>>> Robb, I included some terms from your presentation and took an educated guess at the meanings. Please let me know if they are incorrect.
>>>
>>> Thanks,
>>> Sande
>>>
>
From robb.greathouse at redhat.com Thu Sep 18 17:46:29 2014
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Thu, 18 Sep 2014 17:46:29 -0400 (EDT)
Subject: [windup-dev] Windup terminology question
In-Reply-To: <541B2AD4.1010008@redhat.com>
References: <541B2AD4.1010008@redhat.com>
Message-ID: <645826470.25473223.1411076789895.JavaMail.zimbra@redhat.com>
I would go with neither.
Originally, the rulebase was a set of rules that would always be loaded. Additional rulesets would be added dependent on the project.
I would a ruleset would apply to a group of rules that are used together for a purpose. Such as a WebSphere 7 to JBoss EAP 6 ruleset. A ruleset could also define a group of rules that work together in to perform a part of a migration. Such as 2 or more rules that are used to migrate an XML file or particular piece of functionality.
My two cents.
Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> Ondra and I have created a glossary on the Windup Wiki to document
> terminology that is used by Windup. The goal is to finalize the correct
> terms we want to use in Windup and avoid confusion down the road.
>
> One of the open issues is whether to describe a "ruleset" (formerly
> referred to as "rulebase") as a "Forge add-on" or as a "Windup plug-in".
> Does anyone have a preference?
>
> The glossary page is located here:
> https://github.com/windup/windup/wiki/Glossary. As you come across other
> Windup terms, feel free to update the page directly or email/ping me so
> that we include them on that page.
>
> Robb, I included some terms from your presentation and took an educated
> guess at the meanings. Please let me know if they are incorrect.
>
> Thanks,
> Sande
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
From sgilda at redhat.com Fri Sep 19 10:03:31 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 19 Sep 2014 10:03:31 -0400
Subject: [windup-dev] Windup terminology question
In-Reply-To: <D2B59347-6B7F-491B-9A3A-8002FD72DD18@redhat.com>
References: <541B2AD4.1010008@redhat.com>
<DCEDEA2B-458B-4E34-A370-771DCBBA856F@redhat.com>
<541B4322.4070209@redhat.com>
<D2B59347-6B7F-491B-9A3A-8002FD72DD18@redhat.com>
Message-ID: <541C37B3.5010102@redhat.com>
On 09/18/2014 05:41 PM, Pete Muir wrote:
> On 18 Sep 2014, at 21:40, Sande Gilda <sgilda at redhat.com> wrote:
>
>> On 09/18/2014 03:58 PM, Pete Muir wrote:
>>> On 18 Sep 2014, at 19:56, Sande Gilda <sgilda at redhat.com> wrote:
>>>
>>>> Ondra and I have created a glossary on the Windup Wiki to document terminology that is used by Windup. The goal is to finalize the correct terms we want to use in Windup and avoid confusion down the road.
>>>>
>>>> One of the open issues is whether to describe a "ruleset" (formerly referred to as "rulebase") as a "Forge add-on" or as a "Windup plug-in". Does anyone have a preference?
>>> I prefer ?ruleset? ;-) IOW I don?t think either those are the right description.
>> We already decided on ruleset over rulebase, so I'm glad you agree.
>>
>> How should we describe a ruleset? Won't customers be able to create their own?
> I would describe a ruleset as a ruleset, or perhaps a ?collection rules packaged as a JAR??
I like it! Thanks!
>
>>>> The glossary page is located here: https://github.com/windup/windup/wiki/Glossary. As you come across other Windup terms, feel free to update the page directly or email/ping me so that we include them on that page.
>>>>
>>>> Robb, I included some terms from your presentation and took an educated guess at the meanings. Please let me know if they are incorrect.
>>>>
>>>> Thanks,
>>>> Sande
>>>>
From sgilda at redhat.com Fri Sep 19 10:05:50 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 19 Sep 2014 10:05:50 -0400
Subject: [windup-dev] Windup terminology question
In-Reply-To: <645826470.25473223.1411076789895.JavaMail.zimbra@redhat.com>
References: <541B2AD4.1010008@redhat.com>
<645826470.25473223.1411076789895.JavaMail.zimbra@redhat.com>
Message-ID: <541C383E.40900@redhat.com>
It sounds like everyone is in agreement. No to add-on or plug-in. :-)
On 09/18/2014 05:46 PM, Robb Greathouse wrote:
> I would go with neither.
>
> Originally, the rulebase was a set of rules that would always be loaded. Additional rulesets would be added dependent on the project.
>
> I would a ruleset would apply to a group of rules that are used together for a purpose. Such as a WebSphere 7 to JBoss EAP 6 ruleset. A ruleset could also define a group of rules that work together in to perform a part of a migration. Such as 2 or more rules that are used to migrate an XML file or particular piece of functionality.
>
> My two cents.
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ----- Original Message -----
>> Ondra and I have created a glossary on the Windup Wiki to document
>> terminology that is used by Windup. The goal is to finalize the correct
>> terms we want to use in Windup and avoid confusion down the road.
>>
>> One of the open issues is whether to describe a "ruleset" (formerly
>> referred to as "rulebase") as a "Forge add-on" or as a "Windup plug-in".
>> Does anyone have a preference?
>>
>> The glossary page is located here:
>> https://github.com/windup/windup/wiki/Glossary. As you come across other
>> Windup terms, feel free to update the page directly or email/ping me so
>> that we include them on that page.
>>
>> Robb, I included some terms from your presentation and took an educated
>> guess at the meanings. Please let me know if they are incorrect.
>>
>> Thanks,
>> Sande
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From robb.greathouse at redhat.com Fri Sep 19 11:32:57 2014
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Fri, 19 Sep 2014 11:32:57 -0400 (EDT)
Subject: [windup-dev] Windup terminology question
In-Reply-To: <541C37B3.5010102@redhat.com>
References: <541B2AD4.1010008@redhat.com>
<DCEDEA2B-458B-4E34-A370-771DCBBA856F@redhat.com>
<541B4322.4070209@redhat.com>
<D2B59347-6B7F-491B-9A3A-8002FD72DD18@redhat.com>
<541C37B3.5010102@redhat.com>
Message-ID: <663868600.26238102.1411140777685.JavaMail.zimbra@redhat.com>
For the moment the classifications are just place holders until we find something more descriptive.
Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
>
> On 09/18/2014 05:41 PM, Pete Muir wrote:
> > On 18 Sep 2014, at 21:40, Sande Gilda <sgilda at redhat.com> wrote:
> >
> >> On 09/18/2014 03:58 PM, Pete Muir wrote:
> >>> On 18 Sep 2014, at 19:56, Sande Gilda <sgilda at redhat.com> wrote:
> >>>
> >>>> Ondra and I have created a glossary on the Windup Wiki to document
> >>>> terminology that is used by Windup. The goal is to finalize the correct
> >>>> terms we want to use in Windup and avoid confusion down the road.
> >>>>
> >>>> One of the open issues is whether to describe a "ruleset" (formerly
> >>>> referred to as "rulebase") as a "Forge add-on" or as a "Windup
> >>>> plug-in". Does anyone have a preference?
> >>> I prefer ?ruleset? ;-) IOW I don?t think either those are the right
> >>> description.
> >> We already decided on ruleset over rulebase, so I'm glad you agree.
> >>
> >> How should we describe a ruleset? Won't customers be able to create their
> >> own?
> > I would describe a ruleset as a ruleset, or perhaps a ?collection rules
> > packaged as a JAR??
> I like it! Thanks!
> >
> >>>> The glossary page is located here:
> >>>> https://github.com/windup/windup/wiki/Glossary. As you come across
> >>>> other Windup terms, feel free to update the page directly or email/ping
> >>>> me so that we include them on that page.
> >>>>
> >>>> Robb, I included some terms from your presentation and took an educated
> >>>> guess at the meanings. Please let me know if they are incorrect.
> >>>>
> >>>> Thanks,
> >>>> Sande
> >>>>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
From sgilda at redhat.com Fri Sep 19 11:56:02 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 19 Sep 2014 11:56:02 -0400
Subject: [windup-dev] Windup terminology question
In-Reply-To: <663868600.26238102.1411140777685.JavaMail.zimbra@redhat.com>
References: <541B2AD4.1010008@redhat.com> <DCEDEA2B-458B-4E34-A370-771DCBBA856F@redhat.com> <541B4322.4070209@redhat.com> <D2B59347-6B7F-491B-9A3A-8002FD72DD18@redhat.com> <541C37B3.5010102@redhat.com>
<663868600.26238102.1411140777685.JavaMail.zimbra@redhat.com>
Message-ID: <541C5212.3070601@redhat.com>
Robb, which classifications? The 'level of effort'?
On 09/19/2014 11:32 AM, Robb Greathouse wrote:
> For the moment the classifications are just place holders until we find something more descriptive.
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ----- Original Message -----
>> On 09/18/2014 05:41 PM, Pete Muir wrote:
>>> On 18 Sep 2014, at 21:40, Sande Gilda <sgilda at redhat.com> wrote:
>>>
>>>> On 09/18/2014 03:58 PM, Pete Muir wrote:
>>>>> On 18 Sep 2014, at 19:56, Sande Gilda <sgilda at redhat.com> wrote:
>>>>>
>>>>>> Ondra and I have created a glossary on the Windup Wiki to document
>>>>>> terminology that is used by Windup. The goal is to finalize the correct
>>>>>> terms we want to use in Windup and avoid confusion down the road.
>>>>>>
>>>>>> One of the open issues is whether to describe a "ruleset" (formerly
>>>>>> referred to as "rulebase") as a "Forge add-on" or as a "Windup
>>>>>> plug-in". Does anyone have a preference?
>>>>> I prefer ?ruleset? ;-) IOW I don?t think either those are the right
>>>>> description.
>>>> We already decided on ruleset over rulebase, so I'm glad you agree.
>>>>
>>>> How should we describe a ruleset? Won't customers be able to create their
>>>> own?
>>> I would describe a ruleset as a ruleset, or perhaps a ?collection rules
>>> packaged as a JAR??
>> I like it! Thanks!
>>>>>> The glossary page is located here:
>>>>>> https://github.com/windup/windup/wiki/Glossary. As you come across
>>>>>> other Windup terms, feel free to update the page directly or email/ping
>>>>>> me so that we include them on that page.
>>>>>>
>>>>>> Robb, I included some terms from your presentation and took an educated
>>>>>> guess at the meanings. Please let me know if they are incorrect.
>>>>>>
>>>>>> Thanks,
>>>>>> Sande
>>>>>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From robb.greathouse at redhat.com Fri Sep 19 12:02:42 2014
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Fri, 19 Sep 2014 12:02:42 -0400 (EDT)
Subject: [windup-dev] Windup terminology question
In-Reply-To: <541C5212.3070601@redhat.com>
References: <541B2AD4.1010008@redhat.com>
<DCEDEA2B-458B-4E34-A370-771DCBBA856F@redhat.com>
<541B4322.4070209@redhat.com>
<D2B59347-6B7F-491B-9A3A-8002FD72DD18@redhat.com>
<541C37B3.5010102@redhat.com>
<663868600.26238102.1411140777685.JavaMail.zimbra@redhat.com>
<541C5212.3070601@redhat.com>
Message-ID: <114171787.26261802.1411142562194.JavaMail.zimbra@redhat.com>
Yes.
Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> Robb, which classifications? The 'level of effort'?
>
> On 09/19/2014 11:32 AM, Robb Greathouse wrote:
> > For the moment the classifications are just place holders until we find
> > something more descriptive.
> >
> > Robb Greathouse
> > Chief Evangelist
> > Middleware Business Unit
> > JBoss, a Division of Red Hat
> > cellphone 505-507-4906
> >
> > ----- Original Message -----
> >> On 09/18/2014 05:41 PM, Pete Muir wrote:
> >>> On 18 Sep 2014, at 21:40, Sande Gilda <sgilda at redhat.com> wrote:
> >>>
> >>>> On 09/18/2014 03:58 PM, Pete Muir wrote:
> >>>>> On 18 Sep 2014, at 19:56, Sande Gilda <sgilda at redhat.com> wrote:
> >>>>>
> >>>>>> Ondra and I have created a glossary on the Windup Wiki to document
> >>>>>> terminology that is used by Windup. The goal is to finalize the
> >>>>>> correct
> >>>>>> terms we want to use in Windup and avoid confusion down the road.
> >>>>>>
> >>>>>> One of the open issues is whether to describe a "ruleset" (formerly
> >>>>>> referred to as "rulebase") as a "Forge add-on" or as a "Windup
> >>>>>> plug-in". Does anyone have a preference?
> >>>>> I prefer ?ruleset? ;-) IOW I don?t think either those are the right
> >>>>> description.
> >>>> We already decided on ruleset over rulebase, so I'm glad you agree.
> >>>>
> >>>> How should we describe a ruleset? Won't customers be able to create
> >>>> their
> >>>> own?
> >>> I would describe a ruleset as a ruleset, or perhaps a ?collection rules
> >>> packaged as a JAR??
> >> I like it! Thanks!
> >>>>>> The glossary page is located here:
> >>>>>> https://github.com/windup/windup/wiki/Glossary. As you come across
> >>>>>> other Windup terms, feel free to update the page directly or
> >>>>>> email/ping
> >>>>>> me so that we include them on that page.
> >>>>>>
> >>>>>> Robb, I included some terms from your presentation and took an
> >>>>>> educated
> >>>>>> guess at the meanings. Please let me know if they are incorrect.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Sande
> >>>>>>
> >> _______________________________________________
> >> windup-dev mailing list
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> >>
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From lincolnbaxter at gmail.com Wed Sep 24 10:47:30 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 24 Sep 2014 10:47:30 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2014-09-24
Message-ID: <CAEp_U4EUde3bBThqH7sOB7mi+fnoiHrJx5cKFx9cTHsVvbFDig@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-24-14.06.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-24-14.06.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-09-24-14.06.log.html
Meeting summary
---------------
* Agenda (lincolnthree, 14:07:09)
* Status Reports (lincolnthree, 14:08:33)
* This past week I worked on merging several larger PRs, including the
configuration / graphImpl changes (lincolnthree, 14:09:41)
* I've also worked on merging the XML PR, and a few others
(lincolnthree, 14:10:00)
* This week I am preparing for JavaOne so not working on windup as
much, but still trying to review things (lincolnthree, 14:10:24)
* I have the weekly BU meeting today so we'll see what they want :)
(lincolnthree, 14:10:35)
* Next week I will be mostly offline because I'll be at JavaOne
(lincolnthree, 14:10:48)
* I also worked on creating the Roaster command line tool
https://github.com/forge/roaster#cli so that folks can work in their
own code format and still submit code that matches the project
(lincolnthree, 14:11:42)
* I worked on finishing up the port of visitors from the earlier
brad/grapher branch (jsightler, 14:13:02)
* I completed that, and then worked on finishing up some tweaks to the
reporting, as well as fixing a few problems with the charts that
lincolnthree found (jsightler, 14:13:24)
* Now, I am working on getting rules written in an xml syntax to work
within windup (jsightler, 14:13:44)
* I also worked on tweaking the groovy syntax a little to make it less
verbose, and to provide an example of basic Java hinting in Groovy
(jsightler, 14:14:25)
* I sent PRs for: (ozizka, 14:15:25)
* WINDUP-301 Skip certain packages when scanning for *Model classes.
(ozizka, 14:15:25)
* WINDUP-299 Refactor FurnaceClasspathScanner, *Filter, et al.
(ozizka, 14:15:25)
* WINDUP-235 Decompile single class (ozizka, 14:15:25)
* WINDUP-272 Refactor GraphContextFactoryImpl and GraphContextImpl
(ozizka, 14:15:25)
* (ozizka, 14:15:25)
* Windup Status (lincolnthree, 14:17:20)
* We're actually looking really good! we've basically captured all of
the functionality from windup 1 at this point and met our promise to
deliver a more poiwerful rule syntax (we'll actually deliver this in
3 ways afaik) (lincolnthree, 14:19:47)
* as far as internal tech preview goes, I think we're pretty much
there, now that effort is being reported in the reports
(lincolnthree, 14:20:52)
* Next steps (lincolnthree, 14:23:19)
* ozizka's plans: (ozizka, 14:23:26)
* Will update the tutorial, and example ruleset. (Sande asked for it)
(ozizka, 14:23:26)
* Then according to priority. Perhaps the decompilation pruning.
(ozizka, 14:23:26)
* LINK: https://github.com/forge/core/blob/master/dist/pom.xml#L71
(lincolnthree, 14:32:35)
* LINK: https://github.com/forge/core/blob/master/dist/pom.xml#L33
(lincolnthree, 14:33:06)
* LINK: https://issues.jboss.org/browse/WINDUP-88 (ozizka, 14:33:43)
Meeting ended at 14:45:47 UTC.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140924/f187f46a/attachment.html
From ozizka at redhat.com Thu Sep 25 22:29:01 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Fri, 26 Sep 2014 04:29:01 +0200
Subject: [windup-dev] Windup Demo
Message-ID: <5424CF6D.5030602@redhat.com>
Hi, this is first shot on demo video.
Not final, just trying, and ended up with a Forge Roaster error.
https://www.youtube.com/watch?v=w0Geduof93U&feature=youtu.be
--> https://issues.jboss.org/browse/WINDUP-306
Lincoln, since you know Roaster, could you please check what it is about?
Ondra
From jsightle at redhat.com Fri Sep 26 12:10:20 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Fri, 26 Sep 2014 12:10:20 -0400
Subject: [windup-dev] Windup Demo
In-Reply-To: <5424CF6D.5030602@redhat.com>
References: <5424CF6D.5030602@redhat.com>
Message-ID: <54258FEC.3090009@redhat.com>
On 09/25/2014 10:29 PM, Ondrej Zizka wrote:
> Hi, this is first shot on demo video.
> Not final, just trying, and ended up with a Forge Roaster error.
>
> https://www.youtube.com/watch?v=w0Geduof93U&feature=youtu.be
>
> --> https://issues.jboss.org/browse/WINDUP-306
> Lincoln, since you know Roaster, could you please check what it is about?
>
I have updated the JIRA with the stack more evident and some details on
what needs to be done.