[
https://issues.apache.org/jira/browse/KARAF-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090108#comment-13090108
]
Achim Nierbeck edited comment on KARAF-822 at 8/24/11 11:32 AM:
----------------------------------------------------------------
right now I don't see any benefit from it, it's also a Apache License so what
would be the benefit of sub-projecting it?
Which Projects would be effected?
- Pax Web
- Pax Logging
- Pax URL
- Pax Exam
- ....
sounds like the complete currently still developed Modules stack.
-1 from me right now. I don't see any benefits in this.
TBH I consider this request to be ignorant of what people provide at OPS4J and
it's like a slap in the face.
was (Author: achim_nierbeck):
right now I don't see any benefit from it, it's also a Apache License so
what would be the benefit of sub-projecting it?
Which Projects would be effected?
- Pax Web
- Pax Logging
- Pax URL
- Pax Exam
- ....
sounds like the complete currently still developed Modules stack.
-1 from me right now. I don't see any benefits in this.
> 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
