You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org> on 2009/09/01 21:56:32 UTC
[jira] Created: (GERONIMO-4834) artifact aliasing does not seem to
work for configuration id's
artifact aliasing does not seem to work for configuration id's
--------------------------------------------------------------
Key: GERONIMO-4834
URL: https://issues.apache.org/jira/browse/GERONIMO-4834
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: core
Affects Versions: 2.1.4
Reporter: Vamsavardhana Reddy
Fix For: 2.1.5, 2.2
Artifact aliasing does not seem to work for configuration ids. I have encountered the following problem while trying to change the JPA provider from OpenJPA to TopLink.
I have created a configuration o.a.g.configs/toplink/2.1.4/car to replace openjpa car. I have added the following line in artifact_aliases.properties:
org.apache.geronimo.configs/openjpa//car=org.apache.geronimo.configs/toplink/2.1.4/car
But when I start the server, openjpa//car is getting started as openejb//car has a dependency on openjpa//car. Ideally I would expect toplink//car to be used by openejb//car because of the aliasing above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4834) artifact aliasing does not seem
to work for configuration id's
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758075#action_12758075 ]
David Jencks commented on GERONIMO-4834:
----------------------------------------
I think vamsi told me that the problem was that you may need to include two lines for each alias, with and without the version in the left hand side. I think this is explained in the comment at the top of artifact-aliases.properties, but not in every pom you may write :-).
Vamsi, could you verify this and close the issue if appropriate?
> artifact aliasing does not seem to work for configuration id's
> --------------------------------------------------------------
>
> Key: GERONIMO-4834
> URL: https://issues.apache.org/jira/browse/GERONIMO-4834
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 2.1.4
> Reporter: Vamsavardhana Reddy
> Fix For: 2.1.5, 2.2
>
>
> Artifact aliasing does not seem to work for configuration ids. I have encountered the following problem while trying to change the JPA provider from OpenJPA to TopLink.
> I have created a configuration o.a.g.configs/toplink/2.1.4/car to replace openjpa car. I have added the following line in artifact_aliases.properties:
> org.apache.geronimo.configs/openjpa//car=org.apache.geronimo.configs/toplink/2.1.4/car
> But when I start the server, openjpa//car is getting started as openejb//car has a dependency on openjpa//car. Ideally I would expect toplink//car to be used by openejb//car because of the aliasing above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4834) artifact aliasing does not seem to
work for configuration id's
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-4834.
----------------------------------
Resolution: Cannot Reproduce
AFAICT this was a misunderstanding of what you need to do for artifact aliases.
> artifact aliasing does not seem to work for configuration id's
> --------------------------------------------------------------
>
> Key: GERONIMO-4834
> URL: https://issues.apache.org/jira/browse/GERONIMO-4834
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 2.1.4
> Reporter: Vamsavardhana Reddy
> Assignee: Vamsavardhana Reddy
> Fix For: 2.1.5, 2.2
>
>
> Artifact aliasing does not seem to work for configuration ids. I have encountered the following problem while trying to change the JPA provider from OpenJPA to TopLink.
> I have created a configuration o.a.g.configs/toplink/2.1.4/car to replace openjpa car. I have added the following line in artifact_aliases.properties:
> org.apache.geronimo.configs/openjpa//car=org.apache.geronimo.configs/toplink/2.1.4/car
> But when I start the server, openjpa//car is getting started as openejb//car has a dependency on openjpa//car. Ideally I would expect toplink//car to be used by openejb//car because of the aliasing above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4834) artifact aliasing does not seem to
work for configuration id's
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned GERONIMO-4834:
--------------------------------------
Assignee: Vamsavardhana Reddy
> artifact aliasing does not seem to work for configuration id's
> --------------------------------------------------------------
>
> Key: GERONIMO-4834
> URL: https://issues.apache.org/jira/browse/GERONIMO-4834
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 2.1.4
> Reporter: Vamsavardhana Reddy
> Assignee: Vamsavardhana Reddy
> Fix For: 2.1.5, 2.2
>
>
> Artifact aliasing does not seem to work for configuration ids. I have encountered the following problem while trying to change the JPA provider from OpenJPA to TopLink.
> I have created a configuration o.a.g.configs/toplink/2.1.4/car to replace openjpa car. I have added the following line in artifact_aliases.properties:
> org.apache.geronimo.configs/openjpa//car=org.apache.geronimo.configs/toplink/2.1.4/car
> But when I start the server, openjpa//car is getting started as openejb//car has a dependency on openjpa//car. Ideally I would expect toplink//car to be used by openejb//car because of the aliasing above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.