Re: Issue 162 in wicketforge: NoSuchMethodError in IntelliJ 14 EAP

[wicke...@googlecode.com]

Updates:
Summary: NoSuchMethodError in IntelliJ 14 EAP
Status: Accepted
Labels: milestone-5.0.0.EAP-1

Comment #1 on issue 162 by minas.ma...@gmail.com: NoSuchMethodError in
IntelliJ 14 EAP
http://code.google.com/p/wicketforge/issues/detail?id=162

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[wicke...@googlecode.com]

Comment #2 on issue 162 by minas.ma...@gmail.com: NoSuchMethodError in

IntelliJ 14 EAP
http://code.google.com/p/wicketforge/issues/detail?id=162

FYI: I will start the 5.x branch in a few days.

[wicke...@googlecode.com]

Comment #3 on issue 162 by minas.ma...@gmail.com: NoSuchMethodError in
IntelliJ 14 EAP
https://code.google.com/p/wicketforge/issues/detail?id=162

Issue 165 has been merged into this issue.

[wicke...@googlecode.com]

Updates:
Status: Fixed

Comment #4 on issue 162 by minas.ma...@gmail.com: NoSuchMethodError in

IntelliJ 14 EAP
https://code.google.com/p/wicketforge/issues/detail?id=162

This issue was closed by revision e658acf3a694.

[wicke...@googlecode.com]

Comment #5 on issue 162 by vojta.kr...@gmail.com: NoSuchMethodError in

IntelliJ 14 EAP
https://code.google.com/p/wicketforge/issues/detail?id=162

Have you thought about using reflections for these small incompatibilities?
Maybe you would not need a new branch.

[wicke...@googlecode.com]

Comment #6 on issue 162 by minas.ma...@gmail.com: NoSuchMethodError in

IntelliJ 14 EAP
https://code.google.com/p/wicketforge/issues/detail?id=162

Well, many roads lead to Rome. ;-)

I had a lot of API break from 12 to EAP 13 (and 13.1) so I decided to
create a new major version for each new IDEA version.

WicketForge uses a lot of open api functionalities and meanwhile I find
it's easier to merge changes between branches (if needed). So I can compile
against corresponding IDEA version, my code stays up to date with open api
(and will run into compile time errors), rather than build one version and
test against multiple IDEA (and run into a ReflectiveOperationException at
run time).

Agree, this small change could have been done with reflection, but for the
user it doesn't make any difference. If someone have a issue with an older
version or is missing a feature, I still can solve or merge if possible.
Build and deploy is done quickly. ;-)