[
https://issues.apache.org/jira/browse/FINERACT-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120936#comment-17120936
]
Michael Vorburger commented on FINERACT-918:
--------------------------------------------
[~ptuomola] I've noticed while using it a little more, for "real" (not test)
dev on a PR, that it doesn't actually work that great - Eclipse seems to get
itself into a "loop" wherein it constantly keeps running the Enhancer Gradle
task, and never "settles". The effect of that is the console annoyingly keeps
"popping up". I actually very vaguely remember having hit this exact same
condition many many years, and have a very vague memory of back then even
having spent too much time debugging through Eclipse Builders to see if this
could be fixed! (But did not, of course.)
Perhaps this is a slightly different approach that may work better in
practice.. what if we do the Enhancement, for the Eclipse output path, is still
done through an explicit invocation of that Gradle task, with the profile? In
practice, Domain classes which need enhancement are modified really rarely,
compared to all other classes. I'll see if I can try that out some time.
> 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
> Components: Build
> Reporter: Michael Vorburger
> Assignee: Petri Tuomola
> Priority: Major
> Labels: technical
> Fix For: 1.4.0
>
>
> 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)
