Re: [VOTE] Release Felix Utils 1.8.2, FileInstall 3.5.2, EventAdmin 1.4.6

2016-01-19 Thread Jean-Baptiste Onofré

+1 (non binding)

Regards
JB

On 01/19/2016 08:55 AM, Guillaume Nodet wrote:

+1

2016-01-15 11:27 GMT+01:00 Guillaume Nodet :


I'd like to call a vote for those 3 artifacts :
   - Felix Utils 1.8.2
   - FileInstall 3.5.2
   - EventAdmin 1.4.6

Release notes:
https://issues.apache.org/jira/browse/FELIX/fixforversion/12329700/
https://issues.apache.org/jira/browse/FELIX/fixforversion/12329699/
https://issues.apache.org/jira/browse/FELIX/fixforversion/12333240/

Staging repositories:
   https://repository.apache.org/content/repositories/orgapachefelix-/
   https://repository.apache.org/content/repositories/orgapachefelix-1112/

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh  /tmp/felix-staging
sh check_staged_release.sh 1112 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

Regards
Guillaume Nodet






--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com


[jira] [Commented] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Oliver Lietz (JIRA)

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

Oliver Lietz commented on FELIX-5148:
-

It's the {{config}} directory of Felix Configuration Admin. If not configured 
explicitly by setting {{felix.cm.dir}} it's inside the bundle's data directory, 
e.g. {{$KARAF_DATA/cache/bundle7/data/config}}.

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Updated] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Oliver Lietz (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated FELIX-5148:

Attachment: FELIX-5148.site.patch

patch added for 
http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
> Attachments: FELIX-5148.site.patch
>
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Assigned] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Karl Pauls (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls reassigned FELIX-5148:
-

Assignee: Karl Pauls

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
>Assignee: Karl Pauls
> Attachments: FELIX-5148.site.patch
>
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Commented] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Karl Pauls (JIRA)

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

Karl Pauls commented on FELIX-5148:
---

Ok, I'm willing to look into it but you would have to give me the failing 
set-up. Can you get me something that fails or if not, describe to me what i 
need to do to create a failing set-up for this issue please?

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
>Assignee: Karl Pauls
> Attachments: FELIX-5148.site.patch
>
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Commented] (FELIX-1184) maven-bundle-plugin does not play well with maven-shade-plugin relocate

2016-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on FELIX-1184:
---

Github user gdelafosse commented on the pull request:


https://github.com/apache/incubator-tinkerpop/pull/186#issuecomment-172799284
  
You should enjoy this update : 
- I simplify the gremlin-shaded pom thanks to the solution explained 
[here](https://issues.apache.org/jira/browse/FELIX-1184)
The idea is to call sequentially the maven-shade-plugin to shade the 
dependencies, the maven-jar-plugin to unpack the shaded jar, and eventually the 
maven-bundle-plugin to compute the OSGI MANIFEST entries and repack the jar.
- I implemented an integration test to test that germlin-core is a valid 
OSGI bundle.
Unfortunately I don't manage to implement the same test for 
tinkerpop-gremlin because when I add my test dependencies it breaks the 
existing test (hamcrest Matchers classes are not found). I don't understand for 
the moment how the tinkerpop-gremlin tests work...


> maven-bundle-plugin does not play well with maven-shade-plugin relocate
> ---
>
> Key: FELIX-1184
> URL: https://issues.apache.org/jira/browse/FELIX-1184
> Project: Felix
>  Issue Type: Bug
>  Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-2.0.0
>Reporter: David Jencks
>Assignee: Stuart McCulloch
>
> maven-shade-plugin v 1.2.1
> If your build runs shade to relocate some classes from a preexisting jar and 
> the maven-bundle-plugin to geinerate osgi metadata the bundle plugin refuses 
> to generate any Export-Package, Import-Package or Private-Package headers. I 
> assume it doesn't find any classes.
> I don't know whose fault this is.
> To see this in action check out 
> https://svn.apache.org/repos/asf/geronimo/xbean/trunk/xbean-asm-shaded rev 
> 778992 and uncomment the bundle plugin and comment the transformers section 
> of the shade plugin config.
> This is also reported as http://jira.codehaus.org/browse/MSHADE-51



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


[jira] [Updated] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Oliver Lietz (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated FELIX-5148:

Attachment: FELIX-5148.sling-launchpad-builder.patch

Sure.

Sling Launchpad:

* apply the attached patch to 
{{[launchpad/builder|https://github.com/apache/sling/tree/trunk/launchpad/builder]}}
 (it will replace all snapshots with releases, disables OSGi Subsystems and 
adds Framework Security bundle)
* build project with {{mvn clean install}}
* run with {{java -Djava.security.manager -Djava.security.policy="all.policy" 
-Dorg.osgi.framework.security="osgi" -jar 
org.apache.sling.launchpad-9-SNAPSHOT.jar}}

Karaf:

* start Karaf with {{./bin/start}}
* install {{framework-security}} feature 
(http://localhost:8181/system/console/features)
* stop Karaf with {{./bin/stop}}
* edit {{./etc/system.properties}}, enable
  ** {{java.security.policy=$\{karaf.etc\}/all.policy}}
  ** {{org.osgi.framework.security=osgi}}
* start Karaf again with {{./bin/start}}

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
>Assignee: Karl Pauls
> Attachments: FELIX-5148.site.patch, 
> FELIX-5148.sling-launchpad-builder.patch
>
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Commented] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Karl Pauls (JIRA)

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

Karl Pauls commented on FELIX-5148:
---

Ok, I'll try to get to it. For now, karaf doesn't seem to start for me on my 
mac. Just to make sure, you are not trying to use the standard java security 
policy to give permissions, right? 

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
>Assignee: Karl Pauls
> Attachments: FELIX-5148.site.patch, 
> FELIX-5148.sling-launchpad-builder.patch
>
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Commented] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Oliver Lietz (JIRA)

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

Oliver Lietz commented on FELIX-5148:
-

Do you mean {{jre/lib/security/java.policy}}? No, but it is used implicitly 
when running with {{-Djava.security.policy="all.policy"}} instead of 
{{-Djava.security.policy=="all.policy"}} (double equals).

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
>Assignee: Karl Pauls
> Attachments: FELIX-5148.site.patch, 
> FELIX-5148.sling-launchpad-builder.patch
>
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Commented] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Oliver Lietz (JIRA)

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

Oliver Lietz commented on FELIX-5148:
-

As Web Console is not installed in default Karaf distribution, login over ssh 
and install {{framework-security}} with shell command:
* {{ssh -p 8101 karaf@localhost}}
* {{karaf@root()> feature:install framework-security}}

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
>Assignee: Karl Pauls
> Attachments: FELIX-5148.site.patch, 
> FELIX-5148.sling-launchpad-builder.patch
>
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Commented] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Karl Pauls (JIRA)

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

Karl Pauls commented on FELIX-5148:
---

Well, i did that - what now?

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
>Assignee: Karl Pauls
> Attachments: FELIX-5148.site.patch, 
> FELIX-5148.sling-launchpad-builder.patch
>
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Commented] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Karl Pauls (JIRA)

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

Karl Pauls commented on FELIX-5148:
---

Well, i did that - what now?

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
>Assignee: Karl Pauls
> Attachments: FELIX-5148.site.patch, 
> FELIX-5148.sling-launchpad-builder.patch
>
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Resolved] (FELIX-5148) Framework Security unusable

2016-01-19 Thread Oliver Lietz (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz resolved FELIX-5148.
-
Resolution: Invalid

Solved with [~karlpauls], thanks!

{{-Djava.security.manager}} (taken from outdated documentation) *must not* be 
used with Framework Security. Without Sling starts up fine. KARAF-3400 is still 
an issue.

> Framework Security unusable
> ---
>
> Key: FELIX-5148
> URL: https://issues.apache.org/jira/browse/FELIX-5148
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Framework Security
>Affects Versions: framework.security-2.4.0, configadmin-1.8.0
>Reporter: Oliver Lietz
>Assignee: Karl Pauls
> Attachments: FELIX-5148.site.patch, 
> FELIX-5148.sling-launchpad-builder.patch
>
>
> While fixing an issue with Sling and RMI (SLING-5375) reported by an user I 
> came across an issue (KARAF-3400) reported by [~achim_nierbeck] for Karaf 
> related to framework security.
> There is also an issue with [Sling's own OSGi launcher 
> Launchpad|https://svn.apache.org/viewvc/sling/trunk/launchpad/builder/] and 
> framework security when using {{org.apache.felix.configadmin}} >= {{1.8.0}}.
> {{all.policy}}:
> {noformat}
> grant {
>permission java.security.AllPermission;
> };
> {noformat}
> Adding {{org.apache.felix/org.apache.felix.framework.security/2.4.0}} to 
> {{boot.txt}} and starting with arguments described on [Framework Security's 
> page|http://felix.apache.org/documentation/subprojects/apache-felix-framework-security.html]
>  (which looks broken) and 
> [{{-Djava.security.manager}}|http://docs.oracle.com/javase/8/docs/technotes/guides/security/spec/security-spec.doc6.html]
>  ([Building Secure OSGi 
> Applications|http://de.slideshare.net/marrs/building-secure-osgi-applications])
>  throws a {{java.security.AccessControlException}}:
> {noformat}
> java -Djava.security.manager -Djava.security.policy="all.policy" 
> -Dorg.osgi.framework.security="osgi" -jar 
> org.apache.sling.launchpad-9-SNAPSHOT.jar
> {noformat}
> {noformat}
> [...]
> [...] *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.felix.configadmin-1.8.0.jar 
> (java.security.AccessControlException: access denied 
> ("java.io.FilePermission" "/[...]/sling/config" "read"))
> java.security.AccessControlException: access denied ("java.io.FilePermission" 
> "/[...]/sling/config" "read")
>   at 
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>   at 
> java.security.AccessController.checkPermission(AccessController.java:884)
>   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
>   at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
>   at java.io.File.isDirectory(File.java:844)
>   at 
> org.apache.felix.cm.file.FilePersistenceManager.(FilePersistenceManager.java:342)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:244)
>   at 
> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1709)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:688)
>   at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.lang.Thread.run(Thread.java:745)
> [...]
> {noformat}
> I had to remove OSGi Subsystems support from {{boot.txt}} when using 
> {{org.apache.felix.configadmin}} {{1.6}}:
> {noformat}
> org.apache.felix/org.apache.felix.coordinator/1.0.0
> org.eclipse.equinox/org.eclipse.equinox.region/1.2.101.v20150831-1342
> org.apache.aries.subsystem/org.apache.aries.subsystem.api/2.0.6
> org.apache.aries.subsystem/org.apache.aries.subsystem.core/2.0.6
> {noformat}



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


[jira] [Resolved] (FELIX-5077) Gogo shell prints out nasty error on shutdown

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen resolved FELIX-5077.
-
Resolution: Fixed

Fixed in rev #1725510.


> Gogo shell prints out nasty error on shutdown
> -
>
> Key: FELIX-5077
> URL: https://issues.apache.org/jira/browse/FELIX-5077
> Project: Felix
>  Issue Type: Bug
>  Components: Gogo Shell
>Affects Versions: gogo.shell-0.12.0
>Reporter: David Bosschaert
>Assignee: J.W. Janssen
>
> The gogo shell always prints out a nasty error to the System.err stream on 
> framework shutdown:
> {code}$ java -jar bin/felix.jar
> 
> Welcome to Apache Felix Gogo
> g! stop 0
> g! !!! FAILED TO STOP EXECUTOR !!!{code}



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


[jira] [Resolved] (FELIX-3331) [gogo] Calling Activator.stop after Activator.start throws an exception

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen resolved FELIX-3331.
-
Resolution: Fixed

Fixed in rev #1725510.

> [gogo] Calling Activator.stop after Activator.start throws an exception
> ---
>
> Key: FELIX-3331
> URL: https://issues.apache.org/jira/browse/FELIX-3331
> Project: Felix
>  Issue Type: Bug
>  Components: Gogo Shell
>Reporter: Krzysztof Daniel
> Attachments: ignoreActivatorException.patch
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=786041
> gogo: InterruptedException: sleep interrupted
> java.lang.InterruptedException: sleep interrupted
> at java.lang.Thread.sleep(Native Method)
> at org.apache.felix.gogo.shell.Activator.run(Activator.java:72)
> at java.lang.Thread.run(Thread.java:722)
> Thread.sleep() could be try catched and handle interrupted exception as a 
> proper workflow.



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


[jira] [Updated] (FELIX-3331) [gogo] Calling Activator.stop after Activator.start throws an exception

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen updated FELIX-3331:

Component/s: Gogo Shell

> [gogo] Calling Activator.stop after Activator.start throws an exception
> ---
>
> Key: FELIX-3331
> URL: https://issues.apache.org/jira/browse/FELIX-3331
> Project: Felix
>  Issue Type: Bug
>  Components: Gogo Shell
>Reporter: Krzysztof Daniel
> Attachments: ignoreActivatorException.patch
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=786041
> gogo: InterruptedException: sleep interrupted
> java.lang.InterruptedException: sleep interrupted
> at java.lang.Thread.sleep(Native Method)
> at org.apache.felix.gogo.shell.Activator.run(Activator.java:72)
> at java.lang.Thread.run(Thread.java:722)
> Thread.sleep() could be try catched and handle interrupted exception as a 
> proper workflow.



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


[jira] [Resolved] (FELIX-3354) InterruptedException with uninformative message

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen resolved FELIX-3354.
-
Resolution: Fixed

No longer an issue with the fixes for FELIX-5077 / FELIX-3331. The 
InterruptedException is caught and properly handled.

> InterruptedException with uninformative message
> ---
>
> Key: FELIX-3354
> URL: https://issues.apache.org/jira/browse/FELIX-3354
> Project: Felix
>  Issue Type: Improvement
>  Components: Gogo Shell
>Affects Versions: gogo.shell-0.8.0
>Reporter: Lazar Kirchev
>Priority: Minor
>
> When the OSGi framework, in which the Gogo shell is started, is stopped 
> before the Gogo shell has finished initializing, the following exception 
> occurs:
> gogo: InterruptedException: sleep interrupted
> java.lang.InterruptedException: sleep interrupted
>   at java.lang.Thread.sleep(Native Method)
>   at org.apache.felix.gogo.shell.Activator.run(Activator.java:72)
>   at java.lang.Thread.run(Unknown Source)
> gogo.shell calls Thread.sleep(100) to wait for the gosh command to be 
> registered. The exception occurs when this wait gets interrupted by the 
> stopping of the framework. 
> Since the framework is stopping this interruption does not cause any errors, 
> but the message is not informative and users are getting confused that it is 
> caused by an error in their code.



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


[jira] [Resolved] (FELIX-4375) Error when reading gosh_profile from stream

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen resolved FELIX-4375.
-
Resolution: Fixed

Applied a slightly different version of your proposed patch in rev #1725519.

> Error when reading gosh_profile from stream
> ---
>
> Key: FELIX-4375
> URL: https://issues.apache.org/jira/browse/FELIX-4375
> Project: Felix
>  Issue Type: Bug
>  Components: Gogo Shell
>Affects Versions: gogo.shell-0.10.0
> Environment: Error occurred using Gogo shell on top op Concierge OSGi 
> runtime.
>Reporter: Tim Verbelen
>Priority: Minor
>
> An error occurs when "gosh_profile" is read from a stream without knowing the 
> lenght upfront. In that case, method `CharSequence readScript(URI script)` 
> from `Shell.java` causes an error, since it does not correctly handle the 
> case when the length is -1. In that case, a large size buffer is allocated 
> (fixed on 10240 atm), and thus as the buffer will not be completely filled, 
> one cannot use `cbuf.rewind()`, but use `cbuf.flip()` instead.



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


[jira] [Resolved] (FELIX-4024) Refreshing Gogo shell bundle leaves running daemon thread

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen resolved FELIX-4024.
-
Resolution: Fixed

I think this issue is solved with the fixes for FELIX-5077 / FELIX-3331. That 
is: I cannot reproduce this issue with these changes...

> Refreshing Gogo shell bundle leaves running daemon thread
> -
>
> Key: FELIX-4024
> URL: https://issues.apache.org/jira/browse/FELIX-4024
> Project: Felix
>  Issue Type: Bug
>  Components: Gogo Shell
>Affects Versions: gogo.shell-0.8.0, gogo.shell-0.10.0
>Reporter: Lazar Kirchev
>
> In the Activator of the Gogo shell bundle a new thread is created (line 122) 
> and started (line 123). The thread instance is stored and upon bundle stop it 
> is interrupted (line 54). 
> However, the thread which is created on line 122 is daemon, so after 
> interruption on line 54 it does not go away. So each time the bundle is 
> refreshed a new thread is created and started, but the old one continues to 
> live. In this way a bunch of "Gogo shell" threads get created. These compete 
> for input from the std in and the commands are not read correctly.
> The line nubmers are valid for 0.8.0 and 0.10.0 versions.



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


[jira] [Resolved] (FELIX-4208) The Gogo shell thread doesn't stop when Gogo Shell bundle is stopped.

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen resolved FELIX-4208.
-
Resolution: Fixed

> The Gogo shell thread doesn't stop when Gogo Shell bundle is stopped.
> -
>
> Key: FELIX-4208
> URL: https://issues.apache.org/jira/browse/FELIX-4208
> Project: Felix
>  Issue Type: Bug
>  Components: Gogo Shell
>Affects Versions: gogo.shell-0.10.0
> Environment: Equinox
>Reporter: Radoslaw Stachowiak
>Priority: Critical
>
> The Gogo shell thread doesn't stop when Gogo Shell bundle is stopped.
> This is  problem when using Gogo shell with Equinox.
> In Felix, the bundle starting thread is a daemon thread, so Gogo shell thread 
> is also a daemon thread and when Felix is shutdown, the virtual machine 
> closes.
> However in Equinox the bundle starting thread is a normal thread, so Gogo 
> shell thread is also a normal thread and when Equinox is shutdown, the 
> virtual machine doesn't close, because Gogo shell thread doesn't close (hangs 
> on blocking I/O trying to read from InputStream).



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


[jira] [Closed] (FELIX-2536) Gogo Shell should export org.apache.felix.gogo.options package

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen closed FELIX-2536.
---
Resolution: Fixed

I agree with [~rickhall] on this: you're welcome to reuse the `Options` class 
for your own use cases, but I don't see the value of having it to be exported 
by default.

> Gogo Shell should export org.apache.felix.gogo.options package
> --
>
> Key: FELIX-2536
> URL: https://issues.apache.org/jira/browse/FELIX-2536
> Project: Felix
>  Issue Type: Improvement
>  Components: Gogo Shell
>Reporter: David Savage
>Priority: Minor
> Fix For: gogo.shell-0.14.0
>
>
> The Gogo shell bundle includes a helpful utility class to handle Options 
> parsing in the gogo environment.
> org.apache.felix.gogo.options.Options
> final String[] usage = {
> "test - test Options usage",
> "  text before Usage: is displayed when usage() is called and no 
> error has occurred.",
> "  so can be used as a simple help message.",
> "",
> "Usage: testOptions [OPTION]... PATTERN [FILES]...",
> "  Output control: arbitary non-option text can be included.",
> "  -? --helpshow help",
> "  -c --count=COUNT   show COUNT lines",
> "  -h --no-filename suppress the prefixing filename on 
> output",
> "  -q --quiet, --silent suppress all normal output",
> " --binary-files=TYPE   assume that binary files are TYPE",
> "   TYPE is 'binary', 'text', or 
> 'without-match'",
> "  -I   equivalent to 
> --binary-files=without-match",
> "  -d --directories=ACTION  how to handle directories 
> (default=skip)",
> "   ACTION is 'read', 'recurse', or 
> 'skip'",
> "  -D --devices=ACTION  how to handle devices, FIFOs and 
> sockets",
> "   ACTION is 'read' or 'skip'",
> "  -R, -r --recursive   equivalent to --directories=recurse" 
> };
> Option opt = Options.compile(usage).parse(args);
> if (opt.isSet("help")) {
> opt.usage(); // includes text before Usage:
> return;
> }
> if (opt.args().size() == 0)
> throw opt.usageError("PATTERN not specified");
> System.out.println(opt);
> if (opt.isSet("count"))
> System.out.println("count = " + opt.getNumber("count"));
> System.out.println("--directories specified: " + 
> opt.isSet("directories"));
> System.out.println("directories=" + opt.get("directories"));
> However the package containing this class is not exported from this bundle so 
> it cannot be used by client code



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


[jira] [Resolved] (FELIX-4345) Add support for IPv4 and IPv6 addresses for console

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen resolved FELIX-4345.
-
Resolution: Fixed

Fixed in rev #1725532.

> Add support for IPv4 and IPv6 addresses for console
> ---
>
> Key: FELIX-4345
> URL: https://issues.apache.org/jira/browse/FELIX-4345
> Project: Felix
>  Issue Type: Improvement
>  Components: Gogo Shell
>Affects Versions: gogo.shell-0.10.0
>Reporter: Alex Blewitt
>Priority: Trivial
>
> The telnetd server only listens to IPv4 or IPv6 because the default value for 
> the --ip parameter is "".
> Even though 'localhost' resolves to both ::1 and 127.0.0.1, passing in "" for 
> the address results in it picking one of them.
> If the value is 'null' for the IP address then it will resolve and bind to 
> both network addresses.
> The bug is here:
> 118   server = new ServerSocket(port, 0, InetAddress.getByName(ip));
> This should be:
> InetAddress address = "".equals(ip) ?  null : 
> InetAddress.getByName(p);
> 118   server = new ServerSocket(port, 0, address);



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


[jira] [Closed] (FELIX-4375) Error when reading gosh_profile from stream

2016-01-19 Thread Tim Verbelen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Verbelen closed FELIX-4375.
---

Thanks for fixing

> Error when reading gosh_profile from stream
> ---
>
> Key: FELIX-4375
> URL: https://issues.apache.org/jira/browse/FELIX-4375
> Project: Felix
>  Issue Type: Bug
>  Components: Gogo Shell
>Affects Versions: gogo.shell-0.10.0
> Environment: Error occurred using Gogo shell on top op Concierge OSGi 
> runtime.
>Reporter: Tim Verbelen
>Priority: Minor
>
> An error occurs when "gosh_profile" is read from a stream without knowing the 
> lenght upfront. In that case, method `CharSequence readScript(URI script)` 
> from `Shell.java` causes an error, since it does not correctly handle the 
> case when the length is -1. In that case, a large size buffer is allocated 
> (fixed on 10240 atm), and thus as the buffer will not be completely filled, 
> one cannot use `cbuf.rewind()`, but use `cbuf.flip()` instead.



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


[jira] [Closed] (FELIX-1582) [gogo] the commands bundle include a class from the blueprint api (ReifiedType) which would be better located in a org.osgi.service.blueprint.converter private package

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen closed FELIX-1582.
---
Resolution: Fixed

Closing as requested.

> [gogo] the commands bundle include a class from the blueprint api 
> (ReifiedType) which would be better located in a 
> org.osgi.service.blueprint.converter private package
> ---
>
> Key: FELIX-1582
> URL: https://issues.apache.org/jira/browse/FELIX-1582
> Project: Felix
>  Issue Type: Task
>  Components: Gogo Runtime
>Reporter: Guillaume Nodet
>




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


[jira] [Resolved] (FELIX-3494) Missing motd should not produce error message

2016-01-19 Thread J.W. Janssen (JIRA)

 [ 
https://issues.apache.org/jira/browse/FELIX-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen resolved FELIX-3494.
-
Resolution: Fixed

> Missing motd should not produce error message
> -
>
> Key: FELIX-3494
> URL: https://issues.apache.org/jira/browse/FELIX-3494
> Project: Felix
>  Issue Type: Improvement
>  Components: Gogo Shell
> Environment: Mac OS X, Java 6, Virgo kernel, Gogo 0.10.0
>Reporter: Glyn Normington
>Priority: Minor
>
> After upgrading from Gogo 0.8.0.v201105062003 to 0.10.0, an error message is 
> displayed when logging in to the shell. It would be nice if no error message 
> was produced if no motd is provided as the documentation 
> (http://felix.apache.org/site/apache-felix-gogo.html) does not say how to 
> disable the motd.
> The error message is, for example:
> jar:file:/Users/glynnormington/eclipse/virgo/org.eclipse.virgo.kernel/build-kernel/target/package-expanded/virgo-kernel-3.5.0.BUILD-20120430124155/plugins/org.apache.felix.gogo.shell_0.10.0.jar!/gosh_profile:
> ERROR: java.io.FileNotFoundException:
> /Users/glynnormington/eclipse/virgo/org.eclipse.virgo.kernel/build-kernel/target/package-expanded/virgo-kernel-3.5.0.BUILD-20120430124155/motd
> (No such file or directory)
> See the related bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=378076



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


[jira] [Commented] (FELIX-3494) Missing motd should not produce error message

2016-01-19 Thread J.W. Janssen (JIRA)

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

J.W. Janssen commented on FELIX-3494:
-

Actually, the idea is that you include your own gosh_profile in case you want 
custom behaviour. However, it could be handy that you sometimes want to 
suppress the printing of the motd when starting Gogo.
I've added an option (`-q` or `--quiet`) to suppress printing the motd in rev 
#1725549. 

> Missing motd should not produce error message
> -
>
> Key: FELIX-3494
> URL: https://issues.apache.org/jira/browse/FELIX-3494
> Project: Felix
>  Issue Type: Improvement
>  Components: Gogo Shell
> Environment: Mac OS X, Java 6, Virgo kernel, Gogo 0.10.0
>Reporter: Glyn Normington
>Priority: Minor
>
> After upgrading from Gogo 0.8.0.v201105062003 to 0.10.0, an error message is 
> displayed when logging in to the shell. It would be nice if no error message 
> was produced if no motd is provided as the documentation 
> (http://felix.apache.org/site/apache-felix-gogo.html) does not say how to 
> disable the motd.
> The error message is, for example:
> jar:file:/Users/glynnormington/eclipse/virgo/org.eclipse.virgo.kernel/build-kernel/target/package-expanded/virgo-kernel-3.5.0.BUILD-20120430124155/plugins/org.apache.felix.gogo.shell_0.10.0.jar!/gosh_profile:
> ERROR: java.io.FileNotFoundException:
> /Users/glynnormington/eclipse/virgo/org.eclipse.virgo.kernel/build-kernel/target/package-expanded/virgo-kernel-3.5.0.BUILD-20120430124155/motd
> (No such file or directory)
> See the related bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=378076



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


Re: [VOTE] Release Felix Utils 1.8.2, FileInstall 3.5.2, EventAdmin 1.4.6

2016-01-19 Thread Jamie G.
+1 (non-binding)

On Tue, Jan 19, 2016 at 5:15 AM, Jean-Baptiste Onofré  wrote:
> +1 (non binding)
>
> Regards
> JB
>
>
> On 01/19/2016 08:55 AM, Guillaume Nodet wrote:
>>
>> +1
>>
>> 2016-01-15 11:27 GMT+01:00 Guillaume Nodet :
>>
>>> I'd like to call a vote for those 3 artifacts :
>>>- Felix Utils 1.8.2
>>>- FileInstall 3.5.2
>>>- EventAdmin 1.4.6
>>>
>>> Release notes:
>>> https://issues.apache.org/jira/browse/FELIX/fixforversion/12329700/
>>> https://issues.apache.org/jira/browse/FELIX/fixforversion/12329699/
>>> https://issues.apache.org/jira/browse/FELIX/fixforversion/12333240/
>>>
>>> Staging repositories:
>>>
>>> https://repository.apache.org/content/repositories/orgapachefelix-/
>>>
>>> https://repository.apache.org/content/repositories/orgapachefelix-1112/
>>>
>>> You can use this UNIX script to download the release and verify the
>>> signatures:
>>> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>>>
>>> Usage:
>>> sh check_staged_release.sh  /tmp/felix-staging
>>> sh check_staged_release.sh 1112 /tmp/felix-staging
>>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] -1 Veto the release (please provide specific comments)
>>>
>>> Regards
>>> Guillaume Nodet
>>>
>>>
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com


[jira] [Created] (FELIX-5170) Missing toString in FelixRequirementAdapter makes missing dep error impossible to solve

2016-01-19 Thread Alexandre Roman (JIRA)
Alexandre Roman created FELIX-5170:
--

 Summary: Missing toString in FelixRequirementAdapter makes missing 
dep error impossible to solve
 Key: FELIX-5170
 URL: https://issues.apache.org/jira/browse/FELIX-5170
 Project: Felix
  Issue Type: Bug
  Components: Bundle Repository (OBR)
Affects Versions: bundlerepository-2.0.6
Reporter: Alexandre Roman


While using OBR, a missing dependency will raise this error in logs:

org.osgi.service.subsystem.SubsystemException: 
org.osgi.service.resolver.ResolutionException: Unable to resolve 
XXX;osgi.bundle: missing requirement 
org.apache.felix.bundlerepository.impl.FelixRequirementAdapter@ee869b56 [caused 
by: Unable to resolve XXX;osgi.bundle: missing requirement 
org.apache.felix.bundlerepository.impl.FelixRequirementAdapter@863065e7]
at 
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:395)
 ~[na:na]
at 
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:356)
 ~[na:na]
at 
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:98)
 ~[na:na]
at 
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:90)
 ~[na:na]
at 
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:54)
 ~[na:na]
at 
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:30)
 ~[na:na]
at java.security.AccessController.doPrivileged(Native Method) 
~[na:1.8.0_66]
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:646)
 ~[na:na]
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:690)
 ~[na:na]
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:278)
 ~[na:na]
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:65)
 ~[na:na]
...
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[na:1.8.0_66]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
~[na:1.8.0_66]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[na:1.8.0_66]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_66]
at 
org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:222) 
[2.0.2:na]
at 
org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:37) 
[2.0.2:na]
at 
org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:615)
 [2.0.2:na]
at 
org.apache.felix.scr.impl.helper.BaseMethod.invoke(BaseMethod.java:499) 
[2.0.2:na]
at 
org.apache.felix.scr.impl.helper.ActivateMethod.invoke(ActivateMethod.java:295) 
[2.0.2:na]
at 
org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:302)
 [2.0.2:na]
at 
org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:113)
 [2.0.2:na]
at 
org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:866)
 [2.0.2:na]
at 
org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:833)
 [2.0.2:na]
at 
org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:724)
 [2.0.2:na]
at 
org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:399)
 [2.0.2:na]
at 
org.apache.felix.scr.impl.config.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:676)
 [2.0.2:na]
at 
org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:339)
 [2.0.2:na]
at 
org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:360) 
[2.0.2:na]
at org.apache.felix.scr.impl.Activator.access$000(Activator.java:53) 
[2.0.2:na]
at 
org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:260) 
[2.0.2:na]
at 
org.apache.felix.utils.extender.AbstractExtender.createExtension(AbstractExtender.java:259)
 [2.0.2:na]
at 
org.apache.felix.utils.extender.AbstractExtender.modifiedBundle(AbstractExtender.java:232)
 [2.0.2:na]
at 
org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:482)
 [org.apache.felix.framework-5.4.0.jar:na]
at 
org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:415)
 [org.apache.felix.framework-5.4.0.jar:na]
at 
org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:232) 
[org.apache.felix.framework-5.4.0.jar:na