[PARANAMER-26] Upgrade QDox to 2.x

[rfscholte]

I've changed a couple the method signatures in favour of QDox. Not sure what the impact is of the public methods, please verify yourself.
Most important changes:

• use JavaProjectBuilder instead of JavaDocBuilder
• Introduce JavaConstructor
• Arrays have become Lists when there's a predictable order, otherwise Collections

[paul-hammant]

merged on the command line (as I messed up by not pushing to GH some local changes)

[rfscholte]

Looking at https://github.com/paul-hammant/paranamer/commits/master it seems like these changed hasn't been added to the master. Also after verifying the code, it still uses JavaDocBuilder, that can't be right...

[paul-hammant]

You're right about JavaDocBuilder. I did the merge, and your two commits
appear in the commit history of master.

I found it easier to merge my changes (that'd I'd not pushed by accident)
on top of yours on a fresh checkout of yours, then push back to mine. I
wonder why it messed up

On Sat, Aug 16, 2014 at 5:52 PM, Robert Scholte [email protected]
wrote:

Looking at https://github.com/paul-hammant/paranamer/commits/master it
seems like these changed hasn't been added to the master. Also after
verifying the code, it still uses JavaDocBuilder, that can't be right...

—
Reply to this email directly or view it on GitHub
#16 (comment).

[paul-hammant]

Oh jeez, what a mess -
3c0ec5d#diff-d41d8cd98f00b204e9800998ecf8427e

On Sat, Aug 16, 2014 at 6:30 PM, Paul Hammant [email protected] wrote:

You're right about JavaDocBuilder. I did the merge, and your two commits
appear in the commit history of master.

I found it easier to merge my changes (that'd I'd not pushed by accident)
on top of yours on a fresh checkout of yours, then push back to mine. I
wonder why it messed up

On Sat, Aug 16, 2014 at 5:52 PM, Robert Scholte [email protected]
wrote:

Looking at https://github.com/paul-hammant/paranamer/commits/master it
seems like these changed hasn't been added to the master. Also after
verifying the code, it still uses JavaDocBuilder, that can't be right...

—
Reply to this email directly or view it on GitHub
#16 (comment)
.