[jira] [Assigned] (KARAF-1674) Abnormal Timeout with multiple maven repositories in pax-url
[ https://issues.apache.org/jira/browse/KARAF-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reassigned KARAF-1674: --- Assignee: Grzegorz Grzybek > Abnormal Timeout with multiple maven repositories in pax-url > > > Key: KARAF-1674 > URL: https://issues.apache.org/jira/browse/KARAF-1674 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.2.8 > Environment: karaf 2.2.8 with equinox running on debian with java > 1.7.0_03 >Reporter: Sammy Ramareddy >Assignee: Grzegorz Grzybek > > I'm having a strange issue where karaf needs a lot of time (around > 5-10minutes) to generate for the first time the "features" tab in the > webconsole or give some feedback to a "features:list" command in the ssh > console. > I currently have the following urls configured in > $KARAF_HOME/etc/org.ops4j.pax.url.mvn.cfg: > org.ops4j.pax.url.mvn.repositories= \ > http://192.168.2.224:8080/artifactory/repo@snapshots, \ > http://i0019231.subdomain.domain.tld:8080/artifactory/repo@snapshots > The second url is actually pointing to the same artifactory repository as the > first one, just running with another IP (within our VPN subnet). > Once in production, karaf will run outside our network and will need to reach > our artifactory server through a VPN connection, hence the need for two urls. > The problem is the following: when the VPN connection is *not* running, and > thus "i0019231.subdomain.domain.tld" is not reachable (its IP is 172.21.x.x), > karaf needs 5-10 minutes to be able to start the features-plugin. > When this is happening, the following entry is in the Karaf log: > "failed to open bundleresource://78.fwk10937487/" > where bundle 78 is org.apache.karaf.webconsole.features > This issue happens only when the VPN client is not running and thus the > second repository is not reachable. When the second url is reachable, then > everything runs fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4100) [karaf-3.0.x] Error resolving artifact of feature due to org.ops4j.pax.url.mvn.cfg not loaded yet
[
https://issues.apache.org/jira/browse/KARAF-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736193#comment-15736193
]
Grzegorz Grzybek commented on KARAF-4100:
-
Fixed by upgrading to pax-url-2.5.2, which handles
{{org.ops4j.pax.url.mvn.requireConfigAdminConfig}} correctly - if this option
is set in {{etc/config.properties}} (it's a _framework property_), then
pax-url-aether *won't* register MavenResolver and mvn: handler services. The
registration will be performed *only* after proper update via ConfigAdmin.
Tests:
https://github.com/apache/karaf/commit/307846d5c7d95308dacce2531bf2a91f0950a8be
> [karaf-3.0.x] Error resolving artifact of feature due to
> org.ops4j.pax.url.mvn.cfg not loaded yet
> -
>
> Key: KARAF-4100
> URL: https://issues.apache.org/jira/browse/KARAF-4100
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.5
> Environment: Karaf 3.0.4, Windows 7
>Reporter: Jerry Meng
>Assignee: Grzegorz Grzybek
> Fix For: 4.1.0
>
>
> I set the mvn repository to the karaf_home/system directory in
> org.ops4j.pax.url.mvn.cfg.
> However, I found there is a chance that Karaf was trying to access the
> Internet and threw an exception since it's in a closed environment.
> {code}
> Error resolving artifact
> org.apache.karaf.features:enterprise:xml:features:3.0.4: Could not transfer
> artifact org.apache.karaf.features:enterprise:xml:features:3.0.4 from/to
> (http://mvn.mycompany.net/content/groups/public): Not authorized ,
> ReasonPhrase:Unauthorized.
> {code}
> Root Cause
> =
> Through further tracking, the root cause may happen in
> org.ops4j.pax.url.mvn.internal.Activator (pax-url-aether). The pax url fails
> to load org.ops4j.pax.url.mvn.cfg before Karaf connects the feature url.
> Therefore Karaf ignores my settings in the configuration file but tries to
> access default remote repository. Here are some logs to describe the
> situation...
> {code}
> 1. activator.updated.dictionary: null
> 2. updated directory from safeRegisterService: null
> 3. activator.openConnection:
> mvn:org.apache.karaf.features/enterprise/3.0.4/xml/features
> 4. Unable to add features repository
> mvn:org.apache.karaf.features/enterprise/3.0.4/xml/features at startup
> 5. updated directory from safeRegisterService:
> {felix.fileinstall.filename={file:/D:/karaf/etc/org.ops4j.pax.url.mvn.cfg... }
> 6. activator.updated.dictionary:
> {felix.fileinstall.filename={file:/D:/karaf/etc/org.ops4j.pax.url.mvn.cfg... }
> {code}
> Workaround
> =
> I'm not sure if I should call this a bug, but in my case I can assume
> org.ops4j.pax.url.mvn.cfg is existent definitely.
> Therefore, I make Activator.openConnection to wait if the Dictionary is not
> set.
> Then invoke notifyAll in Activator.updated after receiving an non-null
> Dictionary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4100) [karaf-3.0.x] Error resolving artifact of feature due to org.ops4j.pax.url.mvn.cfg not loaded yet
[
https://issues.apache.org/jira/browse/KARAF-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736173#comment-15736173
]
ASF subversion and git services commented on KARAF-4100:
Commit 307846d5c7d95308dacce2531bf2a91f0950a8be in karaf's branch
refs/heads/master from [~gzres]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=307846d ]
[KARAF-4100] Tests after pax-url-2.5.2 update - only one MavenResolver
registered
> [karaf-3.0.x] Error resolving artifact of feature due to
> org.ops4j.pax.url.mvn.cfg not loaded yet
> -
>
> Key: KARAF-4100
> URL: https://issues.apache.org/jira/browse/KARAF-4100
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.5
> Environment: Karaf 3.0.4, Windows 7
>Reporter: Jerry Meng
>Assignee: Grzegorz Grzybek
> Fix For: 4.1.0
>
>
> I set the mvn repository to the karaf_home/system directory in
> org.ops4j.pax.url.mvn.cfg.
> However, I found there is a chance that Karaf was trying to access the
> Internet and threw an exception since it's in a closed environment.
> {code}
> Error resolving artifact
> org.apache.karaf.features:enterprise:xml:features:3.0.4: Could not transfer
> artifact org.apache.karaf.features:enterprise:xml:features:3.0.4 from/to
> (http://mvn.mycompany.net/content/groups/public): Not authorized ,
> ReasonPhrase:Unauthorized.
> {code}
> Root Cause
> =
> Through further tracking, the root cause may happen in
> org.ops4j.pax.url.mvn.internal.Activator (pax-url-aether). The pax url fails
> to load org.ops4j.pax.url.mvn.cfg before Karaf connects the feature url.
> Therefore Karaf ignores my settings in the configuration file but tries to
> access default remote repository. Here are some logs to describe the
> situation...
> {code}
> 1. activator.updated.dictionary: null
> 2. updated directory from safeRegisterService: null
> 3. activator.openConnection:
> mvn:org.apache.karaf.features/enterprise/3.0.4/xml/features
> 4. Unable to add features repository
> mvn:org.apache.karaf.features/enterprise/3.0.4/xml/features at startup
> 5. updated directory from safeRegisterService:
> {felix.fileinstall.filename={file:/D:/karaf/etc/org.ops4j.pax.url.mvn.cfg... }
> 6. activator.updated.dictionary:
> {felix.fileinstall.filename={file:/D:/karaf/etc/org.ops4j.pax.url.mvn.cfg... }
> {code}
> Workaround
> =
> I'm not sure if I should call this a bug, but in my case I can assume
> org.ops4j.pax.url.mvn.cfg is existent definitely.
> Therefore, I make Activator.openConnection to wait if the Dictionary is not
> set.
> Then invoke notifyAll in Activator.updated after receiving an non-null
> Dictionary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4104) NPE in Felix FileInstall
[
https://issues.apache.org/jira/browse/KARAF-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-4104.
-
Resolution: Cannot Reproduce
It would be great to have some details how to reproduce it (especially the
custom distribution specifics).
> NPE in Felix FileInstall
>
>
> Key: KARAF-4104
> URL: https://issues.apache.org/jira/browse/KARAF-4104
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Claus Ibsen
>Priority: Minor
>
> Got this from a custom karaf assembly (using the karaf maven plugin)
> {code}
> 2015-11-12 09:54:15,019 | INFO | nd.bundle.watch) | fileinstall
> | 6 - org.apache.felix.fileinstall - 3.5.0 | Unable to save
> configuration
> java.lang.NullPointerException
> at
> org.apache.felix.fileinstall.internal.ConfigInstaller.configurationEvent(ConfigInstaller.java:106)[6:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.sendEvent(ConfigurationManager.java:2036)[5:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:2005)[5:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)[5:org.apache.felix.configadmin:1.8.4]
> at java.lang.Thread.run(Thread.java:744)[:1.7.0_45]
> {code}
> That is all there is in the log and its repeated endless.
> I guess its the felix file watcher that fails somehow. But nevertheless would
> be good to get the felix guys to fix a potential NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4104) NPE in Felix FileInstall
[
https://issues.apache.org/jira/browse/KARAF-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4104:
Fix Version/s: (was: 4.0.8)
(was: 4.1.0)
> NPE in Felix FileInstall
>
>
> Key: KARAF-4104
> URL: https://issues.apache.org/jira/browse/KARAF-4104
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Claus Ibsen
>Priority: Minor
>
> Got this from a custom karaf assembly (using the karaf maven plugin)
> {code}
> 2015-11-12 09:54:15,019 | INFO | nd.bundle.watch) | fileinstall
> | 6 - org.apache.felix.fileinstall - 3.5.0 | Unable to save
> configuration
> java.lang.NullPointerException
> at
> org.apache.felix.fileinstall.internal.ConfigInstaller.configurationEvent(ConfigInstaller.java:106)[6:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.sendEvent(ConfigurationManager.java:2036)[5:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:2005)[5:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)[5:org.apache.felix.configadmin:1.8.4]
> at java.lang.Thread.run(Thread.java:744)[:1.7.0_45]
> {code}
> That is all there is in the log and its repeated endless.
> I guess its the felix file watcher that fails somehow. But nevertheless would
> be good to get the felix guys to fix a potential NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (KARAF-4861) Upgrade to sshd 1.3.0
[
https://issues.apache.org/jira/browse/KARAF-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reopened KARAF-4861:
-
The sshd upgrade is causing two issues:
* the itest {{SshKeyFormatTest}} itest changes the {{test.pem}} key by emptying
it.
* even with a clean key, the {{SshKeyFormatTest}} is failing with {{Server key
did not validate}}
> Upgrade to sshd 1.3.0
> -
>
> Key: KARAF-4861
> URL: https://issues.apache.org/jira/browse/KARAF-4861
> Project: Karaf
> Issue Type: Dependency upgrade
> Components: karaf-shell
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4092) feature.xml to support SystemProperties
[ https://issues.apache.org/jira/browse/KARAF-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4092: Fix Version/s: (was: 4.0.8) 4.0.9 > feature.xml to support SystemProperties > --- > > Key: KARAF-4092 > URL: https://issues.apache.org/jira/browse/KARAF-4092 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Amit Patel >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.9 > > > We need feature.xml file to have access to systemProperty. For example we are > using feature in below format and it has and > define in SystemProperty file. so we can externalized the jar file location > and it can be specified at runtime though SystemProperties > > start="true">file:/ajsc-jars/osgiservice1//-.jar > - > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4861) Upgrade to sshd 1.3.0
[ https://issues.apache.org/jira/browse/KARAF-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735567#comment-15735567 ] ASF subversion and git services commented on KARAF-4861: Commit 08d0c386f94200e128e71d6c9a527c14d27003cf in karaf's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=08d0c38 ] Revert "[KARAF-4861] Upgrade to sshd 1.3.0" This reverts commit 0ee2e638f62dd6bc8bcbb171555ab4f787ced4de. > Upgrade to sshd 1.3.0 > - > > Key: KARAF-4861 > URL: https://issues.apache.org/jira/browse/KARAF-4861 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4889) Support role based access to web console
[ https://issues.apache.org/jira/browse/KARAF-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735557#comment-15735557 ] Jean-Baptiste Onofré commented on KARAF-4889: - I think so, it's what we use most of the time with the ActiveMQ admin console. > Support role based access to web console > > > Key: KARAF-4889 > URL: https://issues.apache.org/jira/browse/KARAF-4889 > Project: Karaf > Issue Type: Improvement > Components: karaf-security, webconsole >Reporter: Paul McCulloch > > Currently a user must be in the admin role to access the web console. Once > connected they have total control over the karaf instance. > See https://github.com/hawtio/hawtio/issues/465 for an equivalent kind of > feature. > It should be possible to grant limited permissions to a user so that they > can, for example: > * Read logs > * View (some of?) the configuration > * Edit (some of?) the configuration > But not: > * Stop a bundle > * Modify all the configuration > In the same way that the shell offers fine grained control. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4889) Support role based access to web console
[ https://issues.apache.org/jira/browse/KARAF-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735497#comment-15735497 ] Guillaume Nodet commented on KARAF-4889: Can we use a servlet filter for that ? > Support role based access to web console > > > Key: KARAF-4889 > URL: https://issues.apache.org/jira/browse/KARAF-4889 > Project: Karaf > Issue Type: Improvement > Components: karaf-security, webconsole >Reporter: Paul McCulloch > > Currently a user must be in the admin role to access the web console. Once > connected they have total control over the karaf instance. > See https://github.com/hawtio/hawtio/issues/465 for an equivalent kind of > feature. > It should be possible to grant limited permissions to a user so that they > can, for example: > * Read logs > * View (some of?) the configuration > * Edit (some of?) the configuration > But not: > * Stop a bundle > * Modify all the configuration > In the same way that the shell offers fine grained control. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4878) Cellar Hazelcast unresponsive when ETH Down
[
https://issues.apache.org/jira/browse/KARAF-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735463#comment-15735463
]
Suresh Perumal commented on KARAF-4878:
---
Any update?
> Cellar Hazelcast unresponsive when ETH Down
> ---
>
> Key: KARAF-4878
> URL: https://issues.apache.org/jira/browse/KARAF-4878
> Project: Karaf
> Issue Type: Bug
> Components: cellar-hazelcast
>Affects Versions: 4.0.5
> Environment: Redhat Linux 7.2, CentOS 7.2
>Reporter: Suresh Perumal
>Assignee: Jean-Baptiste Onofré
>Priority: Blocker
>
> Cluster is configured with 2 Nodes. They are up and running.
> As part of fail-over scenario simulation. We are trying to test "ETHERNET
> down scenario" by running "/etc/sysconfig/network-scripts/ifdown eth0"
> command on the first node.
> During this scenario we are shutting down the first node where the ETH is
> down by using monitoring scripts(in-house scripts). The second node(Among
> those two nodes) is kept alive.
> Second Node's Hazelcast is not accessible for more than 15 minutes. We are
> getting bellow exception and no operation related to Hazelcast is working.
> Applications whichever uses hazelcast kept frozen.
> Invocation | 52 - com.hazelcast - 3.5.2 |
> [10.249.50.80]:5701 [cellar] [3.5.2] While asking 'is-executing': Invocation{
> serviceName='hz:impl:mapService', op=PutOperation{unacknowledged-alarm},
> partitionId=165, replicaIndex=0, tryCount=250, tryPauseMillis=500,
> invokeCount=1, callTimeout=6, target=Address[10.249.50.79]:5701,
> backupsExpected=0, backupsCompleted=0}
> java.util.concurrent.TimeoutException: Call Invocation{
> serviceName='hz:impl:mapService',
> op=com.hazelcast.spi.impl.operationservice.impl.operations.IsStillExecutingOperation{serviceName='hz:impl:mapService',
> partitionId=-1, callId=2114, invocationTime=1480511190143, waitTimeout=-1,
> callTimeout=5000}, partitionId=-1, replicaIndex=0, tryCount=0,
> tryPauseMillis=0, invokeCount=1, callTimeout=5000,
> target=Address[10.249.50.79]:5701, backupsExpected=0, backupsCompleted=0}
> encountered a timeout
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponse(InvocationFuture.java:366)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponseOrThrowException(InvocationFuture.java:334)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:225)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.IsStillRunningService.isOperationExecuting(IsStillRunningService.java:85)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.waitForResponse(InvocationFuture.java:275)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:224)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:204)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(MapProxySupport.java:456)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxySupport.putInternal(MapProxySupport.java:417)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxyImpl.put(MapProxyImpl.java:97)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxyImpl.put(MapProxyImpl.java:87)[52:com.hazelcast:3.5.2]
> at
> com.fujitsu.fnc.emf.fpmplatform.cachemanager.HazelcastCacheManagerMapServiceImpl.addToMap(HazelcastCacheManagerMapServiceImpl.java:87)[209:FPMHazelcastCache:4.1.0.SNAPSHOT]
> at Proxy1897a82c_c032_4a5c_9839_e71cb2af452a.addToMap(Unknown
> Source)[:]
> at
> com.fujitsu.fnc.ngemf.fm.server.impl.FpmConsumerTask.prepareJSON(FpmConsumerTask.java:151)[235:com.fujitsu.fnc.ngemf.fm.server.impl:4.1.0.SNAPSHOT]
> at
> com.fujitsu.fnc.ngemf.fm.server.impl.FpmConsumerTask.run(FpmConsumerTask.java:244)[235:com.fujitsu.fnc.ngemf.fm.server.impl:4.1.0.SNAPSHOT]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_66]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3989) Manual broken because images can't be loaded.
[ https://issues.apache.org/jira/browse/KARAF-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3989: Fix Version/s: (was: 4.0.8) 4.0.9 > Manual broken because images can't be loaded. > - > > Key: KARAF-3989 > URL: https://issues.apache.org/jira/browse/KARAF-3989 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation >Affects Versions: 4.0.1 >Reporter: Tobias Hochgürtel >Priority: Minor > Labels: documentation > Fix For: 4.1.0, 4.0.9 > > Attachments: 2015-09-13 12_31_20-Greenshot.png > > > Webpage: http://karaf.apache.org/index/community/download.html > - HTML Version of the Manuel can't load the images. > - PDF Version has also no images. > I think that the PDF Version is generated from the HTML Version and so this > affects also to pdf. > I reported this as first to Karaf User Mailing List [Karaf 4.0.1 Manual > HTML/PDF can not be accessed. (404 > Error)|http://karaf.922171.n3.nabble.com/Karaf-4-0-1-Manual-HTML-PDF-can-not-be-accessed-404-Error-td4042543.html]. > !2015-09-13 12_31_20-Greenshot.png|title=Screenshot shows the Issue side by > side for PDF and HTML Version, width=800! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3976) Broken compatibility with 3.x jdbc DataSources
[
https://issues.apache.org/jira/browse/KARAF-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3976:
Fix Version/s: (was: 4.0.8)
4.0.9
> Broken compatibility with 3.x jdbc DataSources
> --
>
> Key: KARAF-3976
> URL: https://issues.apache.org/jira/browse/KARAF-3976
> Project: Karaf
> Issue Type: Bug
> Components: karaf-jdbc
>Affects Versions: 4.0.1
>Reporter: Sergey
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.9
>
>
> 1st of all, current documentaion is wrong, because command names was changed
> to jdbc:ds-info, for example, but
> http://karaf.apache.org/manual/latest/users-guide/jdbc.html still contains
> jdbc:info command names.
> Most important compatibility breaking change was another one: in karaf 3.x I
> was able to deploy DataSource using spring-dm xml or blueprint, and it was
> registered as a service and in jndi, and was listed using jdbc:datasources
> command. Right now no datasources are listed.
> {code}
> karaf@root()> jndi:names
> JNDI Name | Class Name
> --
> osgi:service/jdbc/zeusDataSource |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/arenaDS |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/tomsDS |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/cofDS |
> com.sybase.jdbc3.jdbc.SybDataSource
> osgi:service/jdbc/fidbDataSource |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/murexDS |
> com.sybase.jdbc3.jdbc.SybDataSource
> osgi:service/jdbc/gpDataSource|
> org.postgresql.ds.PGPoolingDataSource
> karaf@root()> jdbc:ds-info jdbc/fidbDataSource
> Property | Value
> -
> driver.version | 1.2.2
> db.version | 10.50.4000
> db.product | Microsoft SQL Server
> url| jdbc:jtds:sqlserver:
> driver.name| jTDS Type 4 JDBC Driver for MS SQL Server and Sybase
> username | ...
> karaf@root()> jdbc:ds-list
> Name | Product | Version | URL | Status
> ---
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3825) Add ability to shutdown Karaf with a disabled shutdown port
[ https://issues.apache.org/jira/browse/KARAF-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3825: Fix Version/s: (was: 4.0.8) 4.0.9 > Add ability to shutdown Karaf with a disabled shutdown port > --- > > Key: KARAF-3825 > URL: https://issues.apache.org/jira/browse/KARAF-3825 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Affects Versions: 3.0.3, 4.0.0 >Reporter: Dmitry Konstantinov >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.9 > > > Sometimes by security reasons listen ports are asked to disable. It would be > nice to provide an alternative way to trigger Karaf shutdown by touching a > special file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3810) Feature verify goal fail on Windows (for standard features)
[ https://issues.apache.org/jira/browse/KARAF-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3810: Fix Version/s: (was: 4.0.8) 4.0.9 > Feature verify goal fail on Windows (for standard features) > --- > > Key: KARAF-3810 > URL: https://issues.apache.org/jira/browse/KARAF-3810 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.0 >Reporter: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.9 > > > On Windows, the verify goal fails on some standard features. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4889) Support role based access to web console
Paul McCulloch created KARAF-4889: - Summary: Support role based access to web console Key: KARAF-4889 URL: https://issues.apache.org/jira/browse/KARAF-4889 Project: Karaf Issue Type: Improvement Components: karaf-security, webconsole Reporter: Paul McCulloch Currently a user must be in the admin role to access the web console. Once connected they have total control over the karaf instance. See https://github.com/hawtio/hawtio/issues/465 for an equivalent kind of feature. It should be possible to grant limited permissions to a user so that they can, for example: * Read logs * View (some of?) the configuration * Edit (some of?) the configuration But not: * Stop a bundle * Modify all the configuration In the same way that the shell offers fine grained control. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KARAF-4887) GSSAPILdapLoginModule no longer builds in Karaf 4.0
[ https://issues.apache.org/jira/browse/KARAF-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Kitt closed KARAF-4887. --- > GSSAPILdapLoginModule no longer builds in Karaf 4.0 > --- > > Key: KARAF-4887 > URL: https://issues.apache.org/jira/browse/KARAF-4887 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.8 >Reporter: Stephen Kitt >Priority: Blocker > Attachments: > 0001-KARAF-4887-use-an-anonymous-class-instead-of-a-lambd.patch > > > Since 3ea2830ead794ea065dab39090c5a8cbea85fb07, karaf-4.0.x no longer builds > because GSSAPILdapLoginModule uses a lambda. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4888) Upgrade to Pax-Web 6.0.0
[ https://issues.apache.org/jira/browse/KARAF-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735306#comment-15735306 ] ASF subversion and git services commented on KARAF-4888: Commit d557db7554e6ed056a19c20cb359308798e5d573 in karaf's branch refs/heads/master from [~achim_nierbeck] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=d557db7 ] [KARAF-4888] - Upgrade to Pax-Web 6.0.0 upgrade to latest snapshot for now, should be moved to the released version asap > Upgrade to Pax-Web 6.0.0 > > > Key: KARAF-4888 > URL: https://issues.apache.org/jira/browse/KARAF-4888 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > The latest SNAPSHOT dependency should be added, and changed to the release > version as soon as it's available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4888) Upgrade to Pax-Web 6.0.0
[ https://issues.apache.org/jira/browse/KARAF-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4888 started by Achim Nierbeck. - > Upgrade to Pax-Web 6.0.0 > > > Key: KARAF-4888 > URL: https://issues.apache.org/jira/browse/KARAF-4888 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > The latest SNAPSHOT dependency should be added, and changed to the release > version as soon as it's available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4888) Upgrade to Pax-Web 6.0.0
[ https://issues.apache.org/jira/browse/KARAF-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-4888: -- Fix Version/s: 4.1.0 > Upgrade to Pax-Web 6.0.0 > > > Key: KARAF-4888 > URL: https://issues.apache.org/jira/browse/KARAF-4888 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > The latest SNAPSHOT dependency should be added, and changed to the release > version as soon as it's available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4888) Upgrade to Pax-Web 6.0.0
Achim Nierbeck created KARAF-4888: - Summary: Upgrade to Pax-Web 6.0.0 Key: KARAF-4888 URL: https://issues.apache.org/jira/browse/KARAF-4888 Project: Karaf Issue Type: Dependency upgrade Reporter: Achim Nierbeck Assignee: Achim Nierbeck The latest SNAPSHOT dependency should be added, and changed to the release version as soon as it's available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4888) Upgrade to Pax-Web 6.0.0
[ https://issues.apache.org/jira/browse/KARAF-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-4888: -- Component/s: karaf-webcontainer > Upgrade to Pax-Web 6.0.0 > > > Key: KARAF-4888 > URL: https://issues.apache.org/jira/browse/KARAF-4888 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > The latest SNAPSHOT dependency should be added, and changed to the release > version as soon as it's available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-3748) Installing activemq-blueprint feature sometimes fails with uses constraint violation
[
https://issues.apache.org/jira/browse/KARAF-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-3748.
-
Resolution: Cannot Reproduce
It works fine using 4.0.8-SNAPSHOT and ActiveMQ 5.14.1.
> Installing activemq-blueprint feature sometimes fails with uses constraint
> violation
>
>
> Key: KARAF-3748
> URL: https://issues.apache.org/jira/browse/KARAF-3748
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.0.0.M3
>Reporter: Achim Finke
>
> From time to time you get the following exception when installing
> activemq-blueprint feature.
> {code}
> org.osgi.service.resolver.ResolutionException: Uses constraint violation.
> Unable to resolve resource org.apache.activemq.activemq-blueprint
> [org.apache.activemq.activemq-blueprint/5.11.1] because it is exposed to
> package 'org.apache.aries.blueprint' from resources
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] and
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] via
> two dependency chains.
> Chain 1:
> org.apache.activemq.activemq-blueprint
> [org.apache.activemq.activemq-blueprint/5.11.1]
> import:
> (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package: org.apache.aries.blueprint
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3]
> Chain 2:
> org.apache.activemq.activemq-blueprint
> [org.apache.activemq.activemq-blueprint/5.11.1]
> import:
> (&(osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version>=3.13.0)(!(version>=4.0.0)))
> |
> export: osgi.wiring.package=org.apache.xbean.blueprint.context.impl;
> uses:=org.apache.aries.blueprint
> org.apache.xbean.blueprint [org.apache.xbean.blueprint/3.18.0]
> import:
> (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package: org.apache.aries.blueprint
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3]
> at
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1410)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:289)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:185)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:261)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1061)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:960)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_31]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_31]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_31]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]
> {code}
> The behaviour is not predictable. Installation worked x times, afterwards
> installation failed y times so you may need some trys to reproduce.
> To reproduce execute:
> {code}
> feature:repo-add activemq 5.11.1
> feature:install activemq-blueprint
> {code}
> if you don't get the exception stop the container, delete data folder and try
> again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3770) Add support for installing libraries from the features service
[ https://issues.apache.org/jira/browse/KARAF-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3770: Fix Version/s: (was: 4.0.8) 4.0.9 > Add support for installing libraries from the features service > -- > > Key: KARAF-3770 > URL: https://issues.apache.org/jira/browse/KARAF-3770 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.0.M3 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0, 4.0.9 > > > Libraries are currently only supported by the assembly builder. > CXF in particular requires quite a few libraries to work properly (those are > added in the apache-karaf distribution, but not in the minimal one). > Those libraries should be referenced in the CXF features instead, and the > features service should support installing the libraries and restarting the > framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-3779) Be able to define the copied location of the kar files
[ https://issues.apache.org/jira/browse/KARAF-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-3779: --- Assignee: Jean-Baptiste Onofré > Be able to define the copied location of the kar files > -- > > Key: KARAF-3779 > URL: https://issues.apache.org/jira/browse/KARAF-3779 > Project: Karaf > Issue Type: Improvement > Components: karaf-kar >Affects Versions: 2.3.8, 3.0.4, 4.0.0, 2.4.3 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > On Karaf 2.3.x, the kar files are copied into the system folder. It would be > great to configure where Karaf copies the kar files (in the kar service > blueprint xml) using a property in etc/org.apache.karaf.kar.cfg. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3748) Installing activemq-blueprint feature sometimes fails with uses constraint violation
[
https://issues.apache.org/jira/browse/KARAF-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3748:
Fix Version/s: (was: 4.0.8)
(was: 4.1.0)
> Installing activemq-blueprint feature sometimes fails with uses constraint
> violation
>
>
> Key: KARAF-3748
> URL: https://issues.apache.org/jira/browse/KARAF-3748
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.0.0.M3
>Reporter: Achim Finke
>
> From time to time you get the following exception when installing
> activemq-blueprint feature.
> {code}
> org.osgi.service.resolver.ResolutionException: Uses constraint violation.
> Unable to resolve resource org.apache.activemq.activemq-blueprint
> [org.apache.activemq.activemq-blueprint/5.11.1] because it is exposed to
> package 'org.apache.aries.blueprint' from resources
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] and
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] via
> two dependency chains.
> Chain 1:
> org.apache.activemq.activemq-blueprint
> [org.apache.activemq.activemq-blueprint/5.11.1]
> import:
> (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package: org.apache.aries.blueprint
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3]
> Chain 2:
> org.apache.activemq.activemq-blueprint
> [org.apache.activemq.activemq-blueprint/5.11.1]
> import:
> (&(osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version>=3.13.0)(!(version>=4.0.0)))
> |
> export: osgi.wiring.package=org.apache.xbean.blueprint.context.impl;
> uses:=org.apache.aries.blueprint
> org.apache.xbean.blueprint [org.apache.xbean.blueprint/3.18.0]
> import:
> (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package: org.apache.aries.blueprint
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3]
> at
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1410)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:289)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:185)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:261)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1061)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:960)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_31]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_31]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_31]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]
> {code}
> The behaviour is not predictable. Installation worked x times, afterwards
> installation failed y times so you may need some trys to reproduce.
> To reproduce execute:
> {code}
> feature:repo-add activemq 5.11.1
> feature:install activemq-blueprint
> {code}
> if you don't get the exception stop the container, delete data folder and try
> again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4887) GSSAPILdapLoginModule no longer builds in Karaf 4.0
[ https://issues.apache.org/jira/browse/KARAF-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4887. - Resolution: Not A Problem > GSSAPILdapLoginModule no longer builds in Karaf 4.0 > --- > > Key: KARAF-4887 > URL: https://issues.apache.org/jira/browse/KARAF-4887 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.8 >Reporter: Stephen Kitt >Priority: Blocker > Attachments: > 0001-KARAF-4887-use-an-anonymous-class-instead-of-a-lambd.patch > > > Since 3ea2830ead794ea065dab39090c5a8cbea85fb07, karaf-4.0.x no longer builds > because GSSAPILdapLoginModule uses a lambda. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4887) GSSAPILdapLoginModule no longer builds in Karaf 4.0
[
https://issues.apache.org/jira/browse/KARAF-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735262#comment-15735262
]
Jean-Baptiste Onofré commented on KARAF-4887:
-
Too late ;) I already fixed it:
{code}
commit b0f66443bb0c27f08d2d6923d326cd9bbff06f47
Author: Jean-Baptiste Onofré
Date: Fri Dec 9 13:57:18 2016 +0100
[KARAF-4487] Doesn't use lamba to be Java7 compliant
{code}
> GSSAPILdapLoginModule no longer builds in Karaf 4.0
> ---
>
> Key: KARAF-4887
> URL: https://issues.apache.org/jira/browse/KARAF-4887
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.8
>Reporter: Stephen Kitt
>Priority: Blocker
> Attachments:
> 0001-KARAF-4887-use-an-anonymous-class-instead-of-a-lambd.patch
>
>
> Since 3ea2830ead794ea065dab39090c5a8cbea85fb07, karaf-4.0.x no longer builds
> because GSSAPILdapLoginModule uses a lambda.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4887) GSSAPILdapLoginModule no longer builds in Karaf 4.0
[ https://issues.apache.org/jira/browse/KARAF-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Kitt updated KARAF-4887: Attachment: 0001-KARAF-4887-use-an-anonymous-class-instead-of-a-lambd.patch This patch fixes the issue. > GSSAPILdapLoginModule no longer builds in Karaf 4.0 > --- > > Key: KARAF-4887 > URL: https://issues.apache.org/jira/browse/KARAF-4887 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.8 >Reporter: Stephen Kitt >Priority: Blocker > Attachments: > 0001-KARAF-4887-use-an-anonymous-class-instead-of-a-lambd.patch > > > Since 3ea2830ead794ea065dab39090c5a8cbea85fb07, karaf-4.0.x no longer builds > because GSSAPILdapLoginModule uses a lambda. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4887) GSSAPILdapLoginModule no longer builds in Karaf 4.0
Stephen Kitt created KARAF-4887: --- Summary: GSSAPILdapLoginModule no longer builds in Karaf 4.0 Key: KARAF-4887 URL: https://issues.apache.org/jira/browse/KARAF-4887 Project: Karaf Issue Type: Bug Affects Versions: 4.0.8 Reporter: Stephen Kitt Priority: Blocker Since 3ea2830ead794ea065dab39090c5a8cbea85fb07, karaf-4.0.x no longer builds because GSSAPILdapLoginModule uses a lambda. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4487) LDAPLoginModule and GSSAPI
[ https://issues.apache.org/jira/browse/KARAF-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735245#comment-15735245 ] ASF subversion and git services commented on KARAF-4487: Commit b0f66443bb0c27f08d2d6923d326cd9bbff06f47 in karaf's branch refs/heads/karaf-4.0.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=b0f6644 ] [KARAF-4487] Doesn't use lamba to be Java7 compliant > LDAPLoginModule and GSSAPI > -- > > Key: KARAF-4487 > URL: https://issues.apache.org/jira/browse/KARAF-4487 > Project: Karaf > Issue Type: Improvement > Components: karaf-security >Affects Versions: 4.0.4 >Reporter: Alexandre Cartapanis >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > LDAPLoginModule is restricted to "simple" or "none" authentication. A support > for other method like GSSAPI would be great. > Note that it is a common enterprise context : access to LDAP directory is not > made with username/password but through an other realm (a kerberos one for > exemple) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2511) Review and update documentation
[ https://issues.apache.org/jira/browse/KARAF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2511: Fix Version/s: (was: 4.0.8) 4.0.9 > Review and update documentation > --- > > Key: KARAF-2511 > URL: https://issues.apache.org/jira/browse/KARAF-2511 > Project: Karaf > Issue Type: Task > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.9, 4.0.9 > > > The documentation (manual) should be reviewed: > - The subshell part should be described (usage and configuration). > - The "code samples"/screenshots have to be updated with Karaf 3.0.0 use cases > - a global polishing, double read -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3572) Override resources for instance:create in custom distributions
[
https://issues.apache.org/jira/browse/KARAF-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3572:
Fix Version/s: (was: 4.0.8)
4.0.9
> Override resources for instance:create in custom distributions
> --
>
> Key: KARAF-3572
> URL: https://issues.apache.org/jira/browse/KARAF-3572
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-instance
>Affects Versions: 3.0.3, 2.4.1, 4.0.0.M2
>Reporter: Krzysztof Sobkowiak
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.9
>
>
> Currently the command {{instance:create}} creates a new instance using the
> resources included in {{org.apache.karaf.instance.core}} bundle. It would be
> resonable to allow people to override the resources in custom distributions,
> e.g. in the same way like branding bundles.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4886) Upgrade Hibernate Validator to version 5.3.4.Final
[ https://issues.apache.org/jira/browse/KARAF-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved KARAF-4886. - Resolution: Fixed > Upgrade Hibernate Validator to version 5.3.4.Final > -- > > Key: KARAF-4886 > URL: https://issues.apache.org/jira/browse/KARAF-4886 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
