You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2010/03/24 18:47:27 UTC
[jira] Resolved: (ARIES-266) JPA module has dependencies on
Application modules
[ https://issues.apache.org/jira/browse/ARIES-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor resolved ARIES-266.
-------------------------------
Resolution: Fixed
> JPA module has dependencies on Application modules
> --------------------------------------------------
>
> Key: ARIES-266
> URL: https://issues.apache.org/jira/browse/ARIES-266
> Project: Aries
> Issue Type: Improvement
> Components: Application, JPA
> Affects Versions: 0.1
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Fix For: 0.1
>
>
> Some of the JPA code uses VersionRange code from the Application module. Since VersionRage is an interface in the application api module, JPA ends up pulling two application bundles: api (for the interface) and utils (for the implementation).
> These dependencies should be completely unnecessary. To break this dependency, the VersionRange class can be moved to the "util" module which JPA already uses.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.