[
https://issues.apache.org/jira/browse/SYNCOPE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SYNCOPE-241:
----------------------------------------
Attachment: SYNCOPE-241-6.patch
I have given up to move the persistence tests into the persistence module for
now. It is too difficult to do with our current build without creating a lot of
duplicated pom content and resources.
On the other hand I succeeded in moving at least the production persistence
classes into a separate persistence module.
There are at least two advantage compared to the current state:
- It is impossible to accidently create new dependencies from persistence
classes to other parts of core. So persistence is guaranteed to be a inner core
of syncope that can be understood on its own
- The jpa enhancement happens in persistence. So when you work at core you can
leave the persistence project closed and this way eclipse will not accidently
overwrite the enhanced classes with the original classes and make your tests
fail
> Move persistence and persistence impl into separate modules
> -----------------------------------------------------------
>
> Key: SYNCOPE-241
> URL: https://issues.apache.org/jira/browse/SYNCOPE-241
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.0.3-incubating
> Reporter: Christian Schneider
> Fix For: 1.1.0
>
> Attachments: SYNCOPE-241-2.patch, SYNCOPE-241-3.patch,
> SYNCOPE-241-4.patch, SYNCOPE-241-5.patch, SYNCOPE-241-6.patch,
> SYNCOPE-241.patch
>
>
> The core module currently contains many parts of syncope. This makes it
> bigger and more complex than necessary.
> A possible modularization is to move the internal model
> (org.apache.syncope.core.persistence*) and the persistence impl
> (org.apache.syncope.core.persistence.impl) out of core and into separate
> modules.
> One big advantage would be that the jpa code enhancements would then run in
> the model module only. Currently we run into some problems in the cxf
> migration when running the rest itests in core that may be caused by eclipse
> overwriting the enhanced classes with plain classes. If the model
> (peristence) classes are in a separate module we could leave it out of
> eclipse and so this would be no issue anymore.
> Another advantage would be that the persistence tests could run in the
> persistence impl module so when working on the core they would not have to
> run each time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
