cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAY-1883) Clean up Cayenne maven structure - get rid of aggregate modules
Date Sat, 16 Nov 2013 08:05:22 GMT

     [ https://issues.apache.org/jira/browse/CAY-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrus Adamchik updated CAY-1883:
---------------------------------

    Description: 
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.

  was:
Reorg Cayenne Maven structure, 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.


> Clean up Cayenne maven structure - get rid of aggregate modules
> ---------------------------------------------------------------
>
>                 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)

Mime
View raw message