geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-1874) synthetic ears should allow use of modules outside the g repository
Date Tue, 31 Jul 2007 09:48:52 GMT

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

David Jencks closed GERONIMO-1874.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Wish List)
                   2.1
                   2.0

Fixed in trunk rev 561259
Fixed in 2.0 rev 561286
Fixed in daytrader (schema mods) rev 561287.

Use PatternType element for external rars, and external paths,  and cook up an ArtifactResolver
so you can leave bits out.  This means client_artifact_aliases.properties will be used when
available to help with app client deployment.

As noted in previous comment, I don't think allowing pointers to arbitrary stuff is very useful,
use an exploded ear instead.

> synthetic ears should allow use of modules outside the g repository
> -------------------------------------------------------------------
>
>                 Key: GERONIMO-1874
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-1874
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.1
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.0, 2.1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message