You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2012/05/25 18:30:23 UTC
[jira] [Created] (GERONIMO-6357) Gemini Blueprint on Geronimo
Jarek Gawor created GERONIMO-6357:
-------------------------------------
Summary: Gemini Blueprint on Geronimo
Key: GERONIMO-6357
URL: https://issues.apache.org/jira/browse/GERONIMO-6357
Project: Geronimo
Issue Type: New Feature
Security Level: public (Regular issues)
Components: Aries, osgi
Affects Versions: 3.0-beta-2
Reporter: Jarek Gawor
Assignee: Jarek Gawor
It is not possible to install & use Gemini Blueprint on Geronimo since bundles can get cross-wired and processed twice, etc. because Geronimo already has a Blueprint implementation from the Aries project.
KARAF-928 provides a solution to this issue by updating each Blueprint bundle manifest to have an explicit import on some standard Blueprint API. That should cause the bundles to be processes only by one extender.
In Geronimo, we have a bunch of Blueprint bundles that we would have to update in such a way. Including bundles from Aries, Yoko, Geronimo itself, Karaf, and maybe XBean. And this is provided we either update Geronimo to Karaf 3.0 or back-port the changes in KARAF-928 to version of Karaf we currently use in Geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6357) Gemini Blueprint on Geronimo
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283594#comment-13283594 ]
Jarek Gawor commented on GERONIMO-6357:
---------------------------------------
Btw, to install Gemini extender on Geronimo beta 2 do:
1) Add the following to $GERONIMO_HOME/etc/org.ops4j.pax.url.mvn.cfg:
org.ops4j.pax.url.mvn.repositories= \
http://zodiac.springsource.com/maven/bundles/release, \
http://repo1.maven.org/maven2
2. Install the following bundles:
install mvn:org.springframework/spring-core/3.0.7.RELEASE
install mvn:org.springframework/spring-beans/3.0.7.RELEASE
install mvn:org.springframework/spring-aop/3.0.7.RELEASE
install mvn:org.springframework/spring-context/3.0.7.RELEASE
install mvn:org.springframework/spring-context-support/3.0.7.RELEASE
install mvn:org.springframework/spring-asm/3.0.7.RELEASE
install mvn:org.springframework/spring-expression/3.0.7.RELEASE
install mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aopalliance/1.0_6
install mvn:org.eclipse.gemini.blueprint/gemini-blueprint-io/1.0.0.RELEASE
install mvn:org.eclipse.gemini.blueprint/gemini-blueprint-core/1.0.0.RELEASE
install mvn:org.eclipse.gemini.blueprint/gemini-blueprint-extender/1.0.0.RELEASE
> Gemini Blueprint on Geronimo
> ----------------------------
>
> Key: GERONIMO-6357
> URL: https://issues.apache.org/jira/browse/GERONIMO-6357
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Aries, osgi
> Affects Versions: 3.0-beta-2
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Attachments: geronimo-gemini.zip
>
>
> It is not possible to install & use Gemini Blueprint on Geronimo since Blueprint bundles can get cross-wired and processed twice, etc. because Geronimo already has a Blueprint implementation from the Aries project.
> KARAF-928 provides a solution to this issue by updating each Blueprint bundle manifest to have an explicit import on some standard Blueprint API. That should cause the bundles to be processes only by one extender.
> In Geronimo, we have a bunch of Blueprint bundles that we would have to update in such a way. Including bundles from Aries, Yoko, Geronimo itself, Karaf, and maybe XBean. And this is provided we either update Geronimo to Karaf 3.0 or back-port the changes in KARAF-928 to version of Karaf we currently use in Geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6357) Gemini Blueprint on Geronimo
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor updated GERONIMO-6357:
----------------------------------
Description:
It is not possible to install & use Gemini Blueprint on Geronimo since Blueprint bundles can get cross-wired and processed twice, etc. because Geronimo already has a Blueprint implementation from the Aries project.
KARAF-928 provides a solution to this issue by updating each Blueprint bundle manifest to have an explicit import on some standard Blueprint API. That should cause the bundles to be processes only by one extender.
In Geronimo, we have a bunch of Blueprint bundles that we would have to update in such a way. Including bundles from Aries, Yoko, Geronimo itself, Karaf, and maybe XBean. And this is provided we either update Geronimo to Karaf 3.0 or back-port the changes in KARAF-928 to version of Karaf we currently use in Geronimo.
was:
It is not possible to install & use Gemini Blueprint on Geronimo since bundles can get cross-wired and processed twice, etc. because Geronimo already has a Blueprint implementation from the Aries project.
KARAF-928 provides a solution to this issue by updating each Blueprint bundle manifest to have an explicit import on some standard Blueprint API. That should cause the bundles to be processes only by one extender.
In Geronimo, we have a bunch of Blueprint bundles that we would have to update in such a way. Including bundles from Aries, Yoko, Geronimo itself, Karaf, and maybe XBean. And this is provided we either update Geronimo to Karaf 3.0 or back-port the changes in KARAF-928 to version of Karaf we currently use in Geronimo.
> Gemini Blueprint on Geronimo
> ----------------------------
>
> Key: GERONIMO-6357
> URL: https://issues.apache.org/jira/browse/GERONIMO-6357
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Aries, osgi
> Affects Versions: 3.0-beta-2
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
>
> It is not possible to install & use Gemini Blueprint on Geronimo since Blueprint bundles can get cross-wired and processed twice, etc. because Geronimo already has a Blueprint implementation from the Aries project.
> KARAF-928 provides a solution to this issue by updating each Blueprint bundle manifest to have an explicit import on some standard Blueprint API. That should cause the bundles to be processes only by one extender.
> In Geronimo, we have a bunch of Blueprint bundles that we would have to update in such a way. Including bundles from Aries, Yoko, Geronimo itself, Karaf, and maybe XBean. And this is provided we either update Geronimo to Karaf 3.0 or back-port the changes in KARAF-928 to version of Karaf we currently use in Geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6357) Gemini Blueprint on Geronimo
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor updated GERONIMO-6357:
----------------------------------
Attachment: geronimo-gemini.zip
Another possible solution for this issue is to use various OSGi hooks to hide the Geronimo (and Geronimo-related) Blueprint bundles from the Gemini extender. I'm attaching a bundle that tries to do just that.
> Gemini Blueprint on Geronimo
> ----------------------------
>
> Key: GERONIMO-6357
> URL: https://issues.apache.org/jira/browse/GERONIMO-6357
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Aries, osgi
> Affects Versions: 3.0-beta-2
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Attachments: geronimo-gemini.zip
>
>
> It is not possible to install & use Gemini Blueprint on Geronimo since Blueprint bundles can get cross-wired and processed twice, etc. because Geronimo already has a Blueprint implementation from the Aries project.
> KARAF-928 provides a solution to this issue by updating each Blueprint bundle manifest to have an explicit import on some standard Blueprint API. That should cause the bundles to be processes only by one extender.
> In Geronimo, we have a bunch of Blueprint bundles that we would have to update in such a way. Including bundles from Aries, Yoko, Geronimo itself, Karaf, and maybe XBean. And this is provided we either update Geronimo to Karaf 3.0 or back-port the changes in KARAF-928 to version of Karaf we currently use in Geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira