[
https://issues.apache.org/jira/browse/FINERACT-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104781#comment-17104781
]
Petri Tuomola commented on FINERACT-918:
----------------------------------------
[~vorburger] I tried this out today: configured a new builder in Eclipse that
runs the Gradle enhance task only, and made it run as part of the Eclipse
build. After some hacking to get the Gradle classpath to point to the class
files used by Eclipse, it worked.
So I can now run and debug Fineract within Eclipse IDE. Hot swapping also seems
to also simply just work, which is pretty neat...
I think the next challenge is how to package this in a way that could be easily
shared with others. Ideally would be great to somehow export the Eclipse
builder configuration so that others can import it, but need to find out if
that's possible...
> Document how to run Fineract in IDEs like Eclipse & IntelliJ - great for easy
> debugging!
> ----------------------------------------------------------------------------------------
>
> Key: FINERACT-918
> URL: https://issues.apache.org/jira/browse/FINERACT-918
> Project: Apache Fineract
> Issue Type: New Feature
> Reporter: Michael Vorburger
> Priority: Major
>
> The goal of this issue is to be able to easily run (something like)
> {{org.apache.fineract.ServerApplication}} directly within the IDE.
> While Spring Boot itself will launch just fine in-IDE, the main issue in
> Fineract is that it fails due to (missing) OpenJPA Enhancement. ({{Caused by:
> org.apache.openjpa.util.MetaDataException: The type "class
> org.apache.fineract.infrastructure.core.domain.AbstractPersistableCustom" has
> not been enhanced.}})
> One solution would be that I resurrect my (very!!) old OPENJPA-1412 (with
> OPENJPA-1879 and OPENJPA-1887, see
> [https://openjpa.apache.org/enhancement-with-eclipse.html|https://openjpa.apache.org/enhancement-with-eclipse.html)]
> ... I'm JOKING!
> Another much easier and perhaps more feasible approach could be to make the
> IDE use the same classes produced by and already enhanced during the Gradle
> build on the CLI?
> PS: Once we have FINERACT-764, it would also be great of all ITs (first the
> SpringBootLoginTest and then others) could be run directly within the IDE,
> instead of only via Gradle on the CLI. That should, in theory, "just work" -
> when we resolve this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
