[
https://issues.apache.org/jira/browse/CAUSEWAY-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054882#comment-18054882
]
Andi Huber commented on CAUSEWAY-3959:
--------------------------------------
For static weaving even to work, we need to satisfy some requirements, that is,
entities and their relations (including abstract classes) must be in the same
artifact. Or one needs to do the static weaving process in one blow over the
entire multi-module project between COMPILE and PACKAGING phases of the Maven
build.
For SecMan entities and their abstract super classes (ApplicationUser,
ApplicationRole, ...) are not in the same module. If by any chance we can
convert those 4 abstract super classes into interfaces, static weaving could
work, in a standard build process using
https://github.com/ethlo/eclipselink-maven-plugin
> [JPA] Build framework-provided Entities using Static Weaving
> ------------------------------------------------------------
>
> Key: CAUSEWAY-3959
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3959
> Project: Causeway
> Issue Type: New Feature
> Components: Persistence JPA
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 3.6.0, 4.0.0
>
>
> We could perhaps provide additional Maven artifacts distinguished by a
> classifier (in terms of Maven coordinates).
> Alternatively just figure out how corresponding build instructions look like
> and then document the build process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
