On Friday, July 21, 2006, at 10:55AM, Andrus Adamchik <andru..bjectstyle.org> wrote:
>
>On Jul 21, 2006, at 7:19 AM, Bill Dudney wrote:
>
>>
>> When would cayenne-core-java-1.5 be a required dependency? Just
>> thinking out loud on how this module is used...
>>
>> So if I'm deploying Cayenne into my web app I'd always want cayenne-
>> core-java-1.5 to go into the war/WEB-INF/lib dir?
>
>correct.
>
>> I think that means as you say a 'runtime' dependency but to keep
>> the user to only have to import one dependency we would have to
>> introduce something that tied the two together. This is not
>> absolutely necessary, its just that without something that ties
>> them together users would have to specify cayenne-core and cayenne-
>> core-java-1.5 both as dependencies instead of just one dependency.
>> Or we would have to document when to include both.
>>
>> Thoughts?
>
>Yeah, it would be nice to make it transparent to the users, so that
>they'd only include cayenne-core (and/or cayenne-server) without
>having to think of *-1.5. The only reason those two modules are
>separate is to avoid accidentally adding 1.5 code in 1.4 module (and
>to be able to set correct build preferences in Eclipse).
>
>Maybe a solution to that is an extra module that ties 1.4 and 1.5
>together? I.e. we can move "cayenne-core" to "cayenne-core-1.4" and
>use a dummy "cayenne-core" that depends on "cayenne-core-1.4" and
>"cayenne-core-1.5" (same for cayenne-server)
>
That sounds OK to me, only problem is additional complexity for us but its better to add complexity for us than for the users.
TTFN,
-bd-
>Andrus
>
>
This archive was generated by hypermail 2.0.0 : Fri Jul 21 2006 - 11:03:19 EDT