[ http://issues.apache.org/jira/browse/GERONIMO-1874?page=all ]
David Jencks updated GERONIMO-1874:
-----------------------------------
type: Improvement (was: Bug)
Fix Version: Wish List
(was: 1.1)
Assign To: (was: David Jencks)
AFAIK no work has been done on this and Dain had some reservations about
implementing it. Synthetic ears are a peculiar construction and it might be
worth considering just how much we want to support them. Generally an exploded
ear deployed in place is a more standard simpler easier to understand option
with nearly the same capabilities.
> synthetic ears should allow use of modules outside the g repository
> -------------------------------------------------------------------
>
> Key: GERONIMO-1874
> URL: http://issues.apache.org/jira/browse/GERONIMO-1874
> Project: Geronimo
> Type: Improvement
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.1
> Reporter: David Jencks
> Fix For: Wish List
>
> Currently synthetic ears or external modules in an ear only accept external
> artifacts that are in the geronimo repo, identified by an Artifact. We
> should also allow specification of a path that is not in the repository.
> Perhaps this could be resolved using ServerInfo if the path is not absolute.
> I think that changing the meaning of the current <external-path> to actually
> mean a path and introducing a new element such as <artifact> perhaps with all
> the parts to indicate an artifact in the repo would be a good idea.
--
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
