You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2006/04/20 08:37:35 UTC
[jira] Created: (GERONIMO-1874) synthetic ears should allow use of
modules outside the g repository
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: Bug
Security: public (Regular issues)
Components: deployment
Versions: 1.1
Reporter: David Jencks
Assigned to: David Jencks
Fix For: 1.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.
-
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
[jira] Commented: (GERONIMO-1874) synthetic ears should allow use
of modules outside the g repository
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1874?page=comments#action_12415943 ]
Matt Hogstrom commented on GERONIMO-1874:
-----------------------------------------
David,
I think this can be closed but wanted to confirm that
> 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: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.1
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.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.
-
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
[jira] Assigned: (GERONIMO-1874) synthetic ears should allow use of
modules outside the g repository
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned GERONIMO-1874:
--------------------------------------
Assignee: David Jencks
> 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: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1874) synthetic ears should allow use of
modules outside the g repository
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMO-1874) synthetic ears should allow use of
modules outside the g repository
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ 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