[
https://issues.apache.org/jira/browse/FINERACT-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103637#comment-17103637
]
Petri Tuomola commented on FINERACT-918:
----------------------------------------
[~vorburger] I think the simplest solution could be to run the enhance task as
part of Eclipse build - either through a custom task (as suggested here
[https://openjpa.apache.org/enhancement-with-eclipse.html)|https://openjpa.apache.org/enhancement-with-eclipse.html]
or by simply triggering our enhance gradle task as part of the Eclipse build.
Has someone tried this? Shouldn't be that difficult I hope...
Another possibility could be to switch OpenJPA to runtime enhancement when
running from Eclipse. That would mean the enhancement is not required at
compile time. But that's probably not a good idea, as then the behaviour could
be different between running out to Eclipse vs within Eclipse.
> Run Fineract on Spring Boot in (Eclipse) IDE - 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)
