[ http://issues.apache.org/jira/browse/GERONIMO-2409?page=all ]
David Jencks updated GERONIMO-2409:
-----------------------------------
Attachment: GERONIMO-2409-v1.patch
Change the explicit version resolution to do module aliasing as well. This
removes the ability to have a version for an entire groupId. I originally
included this only because I was too lazy to write up an entire
explicit_versions.properties for the entire server. Since Jason has made the
car plugin automatically generate a complete explicit_versions file for each
car, I think removing this functionality is a step forward.
> Provide config/module aliasing ability
> --------------------------------------
>
> Key: GERONIMO-2409
> URL: http://issues.apache.org/jira/browse/GERONIMO-2409
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 1.2
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 1.2
>
> Attachments: GERONIMO-2409-v1.patch
>
>
> It's sort of impossible to swap a basic configuration such as transaction
> with a substitute such as transaction-jta11: there are too many modules that
> depend on it that all have to be rebuilt just because you changed one name.
> To fix this we need some way to substitute one module (configuration) for
> another. We might aim for a function-based registry rather than a name based
> one, but that is more that I want to think about right now.
> I've done some simple experiments and it looks like some trivial changes in
> DefaultArtifactResolver, the car maven plugin, and an additional properties
> file in the server at least let you swap modules and get the server started.
> I expected that changes in the kernel gbean lookups and Configuration gbean
> lookups would be necessary as well, but I haven't needed them yet.
> I think the changes so far should be applied since they clarify the explicit
> version resolution code and enable at least some module swapping. I suspect
> we'll find out soon if more work is needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
