You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2013/11/17 10:55:20 UTC
[jira] [Closed] (CAY-1883) Clean up Cayenne maven structure
[ https://issues.apache.org/jira/browse/CAY-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrus Adamchik closed CAY-1883.
--------------------------------
Resolution: Fixed
For now we ended up with very clean maven structure, no more hacks. End user picture looks like this:
1. normal app: cayenne-server.jar => cayenne-di.jar
2. ROP client: cayenne-client.jar => cayenne-server.jar => cayenne-di.jar
> Clean up Cayenne maven structure
> --------------------------------
>
> Key: CAY-1883
> URL: https://issues.apache.org/jira/browse/CAY-1883
> Project: Cayenne
> Issue Type: Task
> Affects Versions: 3.2M2
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
> Fix For: 3.2M2
>
>
> Reorg Cayenne Maven structure, 1. aligning module folder structure with Maven groups and 2. making cayenne-server and cayenne-client real Maven modules instead of aggregates. Use <optional> and “provided” dependencies to exclude the extras like JGroups and keep it clean. Immediate motivation is OSGi integration that is not possible to achieve cleanly without this reorg.
> Backwards compatibility promise for end users is this:
> * No maven coordinates of previously published modules should change. I.e. for a Maven project upgrade should be transparent.
> * Bigger published modules will be broken up into smaller ones, so non-Maven projects will need to add extra jars to their CLASSPATH. Most likely newly published cayenne-di and cayenne-core.
--
This message was sent by Atlassian JIRA
(v6.1#6144)