You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/08/24 10:01:33 UTC

[jira] [Commented] (KARAF-822) Consider bringing PAX-* and other OPS4J related projects into Karaf, or as sub-projects

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

Jean-Baptiste Onofré commented on KARAF-822:
--------------------------------------------

I'm going to discuss with the OPS4J guys about that. I would prefer a ASF release tag on the OPS4J projects, more than a copy in our SVN.

> Consider bringing PAX-* and other OPS4J related projects into Karaf, or as sub-projects
> ---------------------------------------------------------------------------------------
>
>                 Key: KARAF-822
>                 URL: https://issues.apache.org/jira/browse/KARAF-822
>             Project: Karaf
>          Issue Type: Task
>          Components: karaf-core
>    Affects Versions: 2.2.2
>         Environment: All
>            Reporter: Matt Pavlovich
>            Assignee: Jean-Baptiste Onofré
>              Labels: security
>
> OPS4J projects may pose an issue for organizations looking for tight controls around source code modification.  Consider bringing in OPS4J projects into Karaf, or as other sub-projects to resolve.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira