[
https://issues.apache.org/jira/browse/LABS-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jan iversen closed LABS-466.
----------------------------
Resolution: Won't Fix
outdated and closed, if not correct please reopen.
> [build] Optimize speed by limiting JPA schema creation inspection
> -----------------------------------------------------------------
>
> Key: LABS-466
> URL: https://issues.apache.org/jira/browse/LABS-466
> Project: Labs
> Issue Type: Improvement
> Components: Magma
> Affects Versions: Current
> Reporter: Simone Gianni
> Fix For: Next
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Currently the Magma build scans all classes to find which ones needs JPA
> enhancements, and then delegate to the proper enhancer. This task is really
> time consuming, expecially when running in developer environment where it has
> to be carried out at each redeploy.
> It would be easier to identify entity classes and limit the scope, still not
> requiring the user to mantain a persistence.xml file.
> The hard part will be to avoid including classes explicitly "unmanaged" by
> the user. That is, if the user has 10 entity beans, and explicitly writes a
> persistence.xml file including only 9 of those classes. Proper check during
> build must be placed to avoid reporting all the 10 classes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
