[jira] [Updated] (KARAF-6620) Remove the spring-boot-starter-decanter module

2020-02-18 Thread Jira


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

Jean-Baptiste Onofré updated KARAF-6620:

Labels: spring-boot  (was: )

> Remove the spring-boot-starter-decanter module
> --
>
> Key: KARAF-6620
> URL: https://issues.apache.org/jira/browse/KARAF-6620
> Project: Karaf
>  Issue Type: Task
>  Components: decanter
>Reporter: Francois Papon
>Assignee: Francois Papon
>Priority: Minor
>  Labels: spring-boot
> Fix For: decanter-2.3.0
>
>
> The spring-boot-starter-decanter module is not used anymore and we could 
> remove it.
> It will still be available on older versions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (KARAF-6615) Make karaf installable via SDKMan

2020-02-18 Thread Jira


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

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

Anyway, there's an important refactoring of the tools on the way, so maybe 
better to wait a little bit.

> Make karaf installable via SDKMan
> -
>
> Key: KARAF-6615
> URL: https://issues.apache.org/jira/browse/KARAF-6615
> Project: Karaf
>  Issue Type: New Feature
>  Components: karaf
>Reporter: Toni Menzel
>Priority: Minor
>
> SDKMan ([https://sdkman.io/]) is a quite nice package manager for unix-ish 
> OSs and it lets you install all kinds of java sdk flavours, switch between 
> them etc. It also has other "SDKs" like Springboot, Micronaut etc.
> I thought, it would be nice to have karaf installable like this:
> sdk install karaf
> This also supports upgrading, (sdk update karaf) and managing different 
> flavours (say in karaf there is standard and minimal). 
> There is a PR at SDKMan to get this started. 
> [https://github.com/sdkman/sdkman-db-migrations/pull/216]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (KARAF-6615) Make karaf installable via SDKMan

2020-02-18 Thread Jira


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

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

I was thinking more extending the tooling to generate the package (as I did for 
DockerFile/Docker image).

> Make karaf installable via SDKMan
> -
>
> Key: KARAF-6615
> URL: https://issues.apache.org/jira/browse/KARAF-6615
> Project: Karaf
>  Issue Type: New Feature
>  Components: karaf
>Reporter: Toni Menzel
>Priority: Minor
>
> SDKMan ([https://sdkman.io/]) is a quite nice package manager for unix-ish 
> OSs and it lets you install all kinds of java sdk flavours, switch between 
> them etc. It also has other "SDKs" like Springboot, Micronaut etc.
> I thought, it would be nice to have karaf installable like this:
> sdk install karaf
> This also supports upgrading, (sdk update karaf) and managing different 
> flavours (say in karaf there is standard and minimal). 
> There is a PR at SDKMan to get this started. 
> [https://github.com/sdkman/sdkman-db-migrations/pull/216]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (KARAF-6618) Version-check of karaf-instance and features

2020-02-18 Thread Jira


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

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

Are you extending {{KarafTestSupport}} in your test ? It should come out of the 
box.

> Version-check of karaf-instance and features
> 
>
> Key: KARAF-6618
> URL: https://issues.apache.org/jira/browse/KARAF-6618
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf
>Affects Versions: 4.2.8
>Reporter: Matthias Wegner
>Assignee: Jean-Baptiste Onofré
>Priority: Trivial
>  Labels: integration-tests
>
> Some of my integrations-test fail again. I think i found my error. I not 
> corrected the karaf-version from the feature-build and the karaf-instance and 
> it seems to work a while. Now i solved it with on unit-test-side with
> String karafVersion = System.getProperty("karaf.version");
> MavenArtifactUrlReference karafUrl = 
> maven().groupId("org.apache.karaf").artifactId("apache-karaf").version(karafVersion).type("tar.gz");
> and on pom-side
>  
>  org.apache.maven.plugins
>  maven-surefire-plugin
>  
>  
>  
>  
>  karaf.version
>  ${karaf.version}
>  
>  
>  
>  
> Is there a validation which tests if the karaf-instance is the same as the 
> loaded features?
> If not it would be nice, because there was no error. My integration-tests 
> stuck and freeze if i load a feature with "higher" version as the 
> karaf-instance in the test.
> Maybe i am wrong, but the correct version match in my project solved the 
> problem.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (KARAF-6618) Version-check of karaf-instance and features

2020-02-18 Thread Jira


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

Jean-Baptiste Onofré reassigned KARAF-6618:
---

Assignee: Jean-Baptiste Onofré

> Version-check of karaf-instance and features
> 
>
> Key: KARAF-6618
> URL: https://issues.apache.org/jira/browse/KARAF-6618
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf
>Affects Versions: 4.2.8
>Reporter: Matthias Wegner
>Assignee: Jean-Baptiste Onofré
>Priority: Trivial
>  Labels: integration-tests
>
> Some of my integrations-test fail again. I think i found my error. I not 
> corrected the karaf-version from the feature-build and the karaf-instance and 
> it seems to work a while. Now i solved it with on unit-test-side with
> String karafVersion = System.getProperty("karaf.version");
> MavenArtifactUrlReference karafUrl = 
> maven().groupId("org.apache.karaf").artifactId("apache-karaf").version(karafVersion).type("tar.gz");
> and on pom-side
>  
>  org.apache.maven.plugins
>  maven-surefire-plugin
>  
>  
>  
>  
>  karaf.version
>  ${karaf.version}
>  
>  
>  
>  
> Is there a validation which tests if the karaf-instance is the same as the 
> loaded features?
> If not it would be nice, because there was no error. My integration-tests 
> stuck and freeze if i load a feature with "higher" version as the 
> karaf-instance in the test.
> Maybe i am wrong, but the correct version match in my project solved the 
> problem.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (KARAF-6619) Keycloak jetty adapter cannot be installed

2020-02-18 Thread Jira


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

Jean-Baptiste Onofré reassigned KARAF-6619:
---

Assignee: Jean-Baptiste Onofré

> Keycloak jetty adapter cannot be installed
> --
>
> Key: KARAF-6619
> URL: https://issues.apache.org/jira/browse/KARAF-6619
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.2.8
>Reporter: Farid Guliyev
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> I use Apache Karaf 4.2.8. I installed keycloak osgi features. I could 
> configure authentication for karaf shell with keycloak using *keycloak-jaas* 
> feature.
> Now I want to configure authentication for my services under /cxf context.
> I configured pax-web context so login-method is KEYCLOAK.
> But I have to install keycloak-jetty-adapter as well, so it could be 
> integrated. But when I try to install that feature I receive an error.
> *trun()> feature:install keycloak-jetty9-adapter*
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: 
> missing requirement [root] osgi.identity; 
> osgi.identity=keycloak-jetty9-adapter; type=karaf.feature; 
> version="[8.0.1,8.0.1]"; 
> filter:="(&(osgi.identity=keycloak-jetty9-adapter)(type=karaf.feature)(version>=8.0.1)(version<=8.0.1))"
>  [caused by: Unable to resolve keycloak-jetty9-adapter/8.0.1: missing 
> requirement [keycloak-jetty9-adapter/8.0.1] osgi.identity; 
> osgi.identity=jetty; type=karaf.feature; version="[9.2.0,9.3.0)"]
>  at 
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
>  at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
>  at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378)
>  at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332)
>  at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
>  at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
>  at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1058)
>  at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:994)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to 
> resolve keycloak-jetty9-adapter/8.0.1: missing requirement 
> [keycloak-jetty9-adapter/8.0.1] osgi.identity; osgi.identity=jetty; 
> type=karaf.feature; version="[9.2.0,9.3.0)"
>  at 
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
>  ... 12 more
> {color:#FF}Error executing command: Unable to resolve root: missing 
> requirement [root] osgi.identity; osgi.identity=keycloak-jetty9-adapter; 
> type=karaf.feature; version="[8.0.1,8.0.1]"; 
> filter:="(&(osgi.identity=keycloak-jetty9-adapter)(type=karaf.feature)(version>=8.0.1)(version<=8.0.1))"
>  [caused by: Unable to resolve keycloak-jetty9-adapter/8.0.1: missing 
> requirement [keycloak-jetty9-adapter/8.0.1] osgi.identity; 
> osgi.identity=jetty; type=karaf.feature; version="[9.2.0,9.3.0)"]{color}
> =
> If not to install that adapter, then I cannot reach my service as it is 
> protected via pax-web but authentication is impossible.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (KARAF-6619) Keycloak jetty adapter cannot be installed

2020-02-18 Thread Jira


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

Jean-Baptiste Onofré updated KARAF-6619:

Fix Version/s: 4.2.9
   4.3.0

> Keycloak jetty adapter cannot be installed
> --
>
> Key: KARAF-6619
> URL: https://issues.apache.org/jira/browse/KARAF-6619
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.2.8
>Reporter: Farid Guliyev
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.9
>
>
> I use Apache Karaf 4.2.8. I installed keycloak osgi features. I could 
> configure authentication for karaf shell with keycloak using *keycloak-jaas* 
> feature.
> Now I want to configure authentication for my services under /cxf context.
> I configured pax-web context so login-method is KEYCLOAK.
> But I have to install keycloak-jetty-adapter as well, so it could be 
> integrated. But when I try to install that feature I receive an error.
> *trun()> feature:install keycloak-jetty9-adapter*
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: 
> missing requirement [root] osgi.identity; 
> osgi.identity=keycloak-jetty9-adapter; type=karaf.feature; 
> version="[8.0.1,8.0.1]"; 
> filter:="(&(osgi.identity=keycloak-jetty9-adapter)(type=karaf.feature)(version>=8.0.1)(version<=8.0.1))"
>  [caused by: Unable to resolve keycloak-jetty9-adapter/8.0.1: missing 
> requirement [keycloak-jetty9-adapter/8.0.1] osgi.identity; 
> osgi.identity=jetty; type=karaf.feature; version="[9.2.0,9.3.0)"]
>  at 
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
>  at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
>  at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378)
>  at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332)
>  at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
>  at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
>  at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1058)
>  at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:994)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to 
> resolve keycloak-jetty9-adapter/8.0.1: missing requirement 
> [keycloak-jetty9-adapter/8.0.1] osgi.identity; osgi.identity=jetty; 
> type=karaf.feature; version="[9.2.0,9.3.0)"
>  at 
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
>  ... 12 more
> {color:#FF}Error executing command: Unable to resolve root: missing 
> requirement [root] osgi.identity; osgi.identity=keycloak-jetty9-adapter; 
> type=karaf.feature; version="[8.0.1,8.0.1]"; 
> filter:="(&(osgi.identity=keycloak-jetty9-adapter)(type=karaf.feature)(version>=8.0.1)(version<=8.0.1))"
>  [caused by: Unable to resolve keycloak-jetty9-adapter/8.0.1: missing 
> requirement [keycloak-jetty9-adapter/8.0.1] osgi.identity; 
> osgi.identity=jetty; type=karaf.feature; version="[9.2.0,9.3.0)"]{color}
> =
> If not to install that adapter, then I cannot reach my service as it is 
> protected via pax-web but authentication is impossible.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (KARAF-6616) Karaf in offline mode w/ pre-installed features shows maven access errors

2020-02-18 Thread Gerald Kallas (Jira)


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

Gerald Kallas commented on KARAF-6616:
--

Hi [~jbonofre], did you have time in between to recreate the described 
behaviour w/ the maven repositories? Many thanks for a reply.

> Karaf in offline mode w/ pre-installed features shows maven access errors
> -
>
> Key: KARAF-6616
> URL: https://issues.apache.org/jira/browse/KARAF-6616
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.7
>Reporter: Gerald Kallas
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Attachments: Dockerfile, docker-compose.yml, org.ops4j.pax.url.mvn.cfg
>
>
> I started a vanilla Karaf 4.2.7 at
> /opt/apache-karaf-4.2.7
> /opt/apache-karaf (symbolic link to the folder above)
> and installed some features with Karaf client as following
> {code:java}
> feature:repo-add hawtio 2.9.0
> feature:repo-add activemq 5.15.11
> feature:repo-add camel 3.0.1
> feature:install webconsole hawtio activemq-broker-noweb camel camel-jms jms 
> camel-http camel-servlet camel-swagger-java camel-ftp camel-jackson 
> camel-jsonpath camel-zipfile camel-velocity
> {code}
> After the installation I've stopped Karaf and packed the folder into a .tgz 
> file. This I'm using for a docker container creation. See Dockerfile and 
> docker-compose.yml attached.
> I copied the relevant folders to the host directory and changed the 
> org.ops4j.pax.url.mvn.cfg (see attached as well). Afterwards I started the 
> container.
> After the docker container startup the Karaf log shows entries like
> {code:java}
> 2020-02-09T02:20:24,286 | WARN  | FelixStartLevel  | AetherBasedResolver  
> | 4 - org.ops4j.pax.url.mvn - 2.6.1 | Error resolving artifact 
> org.apache.camel.karaf:apache-camel:xml:features:3.0.1: [Could not find 
> artifact org.apache.camel.karaf:apache-camel:xml:features:3.0.1]
> java.io.IOException: Error resolving artifact 
> org.apache.camel.karaf:apache-camel:xml:features:3.0.1: [Could not find 
> artifact org.apache.camel.karaf:apache-camel:xml:features:3.0.1]
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.configureIOException(AetherBasedResolver.java:803)
>  [!/:?]
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:774)
>  [!/:?]
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:657)
>  [!/:?]
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:598)
>  [!/:?]
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:565)
>  [!/:?]
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:555)
>  [!/:?]
> at 
> org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:123) 
> [!/:?]
> at java.net.URL.openStream(URL.java:1068) [?:1.8.0_242]
> at 
> org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:113)
>  [!/:?]
> at 
> org.apache.karaf.features.internal.service.RepositoryImpl.(RepositoryImpl.java:50)
>  [!/:?]
> at 
> org.apache.karaf.features.internal.service.RepositoryCacheImpl.create(RepositoryCacheImpl.java:51)
>  [!/:?]
> at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.getFeatureCache(FeaturesServiceImpl.java:605)
>  [!/:?]
> at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.ensureCacheLoaded(FeaturesServiceImpl.java:576)
>  [!/:?]
> at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.listRequiredRepositories(FeaturesServiceImpl.java:508)
>  [!/:?]
> at 
> org.apache.karaf.deployer.features.FeatureDeploymentListener.bundleChanged(FeatureDeploymentListener.java:240)
>  [!/:?]
> at 
> org.apache.karaf.deployer.features.FeatureDeploymentListener.init(FeatureDeploymentListener.java:95)
>  [!/:?]
> at 
> org.apache.karaf.deployer.features.osgi.Activator$DeploymentFinishedListener.deploymentEvent(Activator.java:86)
>  [!/:?]
> at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.registerListener(FeaturesServiceImpl.java:295)
>  [!/:?]
> at 
> org.apache.karaf.deployer.features.osgi.Activator.doStart(Activator.java:53) 
> [!/:?]
> at 
> org.apache.karaf.util.tracker.BaseActivator.start(BaseActivator.java:92) 
> [!/:?]
> at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
>  [org.apache.felix.framework-5.6.12.jar:?]
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240) 
> 

[jira] [Commented] (KARAF-6620) Remove the sp2ing-boot-starter-decanter module

2020-02-18 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot commented on KARAF-6620:
---

fpapon commented on pull request #122: [KARAF-6620] Remove the 
spring-boot-starter-decanter module
URL: https://github.com/apache/karaf-decanter/pull/122
 
 
   
 

This is an automated message from the Apache Gi4 Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Remove the spring-boot-starter-decanter module
> --
>
> Key: KARAF-6620
> URL: https://issues.apache.org/jira/browse/KARAF-6620
> Project: Karaf
>  Issue Type: Task
>  Components: decanter
>Reporter: Francois Papon
~Assignee: Francois Papon
>Priority: Minor
> Fix For: decanter-2.3.0
>
>
> The spring-boot-starter-decanter module is not used anymore and we could 
> remove it.
> It will still be available on older versions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (KARAF-6620) Remove the spring-boot-starter-decanter module

2020-02-18 Thread Francois Papon (Jira)
Francois Papon created KARAF-6620:
-

 Summary: Remove the spring-boot-starter-decanter module
 Key: KARAF-6620
 URL: https://issues.apache.org/jira/browse/KARAF-6620
 Project: Karaf
  Issue Type: Task
  Components: decanter
Reporter: Francois Papon
Assignee: Francois Papon
 Fix For: decanter-2.3.0


The spring-boot-starter-decanter module is not used anymore and we could remove 
it.

It will still be available on older versions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)