karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Seth Leger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4774) Remove gemini-blueprint support
Date Wed, 18 Jan 2017 17:28:26 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828434#comment-15828434
] 

Seth Leger commented on KARAF-4774:
-----------------------------------

I understand its removal from Karaf. I'm not sure that it's Karaf's responsibility to provide
gemini-blueprint compatibility out-of-the-box anyway. The gemini-blueprint project could (and
probably should) provide and maintain a Karaf features.xml artifact to make it easy to use
with Karaf (just like Camel, ActiveMQ, etc do).

> Remove gemini-blueprint support
> -------------------------------
>
>                 Key: KARAF-4774
>                 URL: https://issues.apache.org/jira/browse/KARAF-4774
>             Project: Karaf
>          Issue Type: Task
>          Components: karaf-feature
>            Reporter: Grzegorz Grzybek
>            Assignee: Grzegorz Grzybek
>             Fix For: 4.1.0
>
>
> Gemini Blueprint's latest version is from 2012. The [only repository|http://ebr.springsource.com/repository/app/faq]
that contains these artifacts has the following FAQ entry:
> {quote}
> *What is the current status of the repository?*
> The repository is frozen but will remain accessible until at least 1 September 2014.
See http://www.eclipse.org/ebr/ for information regarding the Eclipse Bundle Recipes project
to which users of the SpringSource Enterprise Bundle Repository should transition. 
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message