[jira] [Commented] (KARAF-6422) karaf client sometimes hang when executing command
[
https://issues.apache.org/jira/browse/KARAF-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934690#comment-16934690
]
Freeman Fang commented on KARAF-6422:
-
Hi [~wenjie_sun1979],
Is it easy for you to reproduce it? What's your env?
I've tried 100 times on my machine but can't reproduce this issue anyway.
Thanks
Freeman
> karaf client sometimes hang when executing command
> --
>
> Key: KARAF-6422
> URL: https://issues.apache.org/jira/browse/KARAF-6422
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.6
> Environment: redhat7.6
> jdk1.8.0_221
> newly installed latest karaf runtime version 4.2.6, no any changes to it.
> just start it by bin/start
>Reporter: wenjie sun
>Assignee: Freeman Fang
>Priority: Major
>
> when my script invoke below command after karaf started:
> "/opt/apache/karaf/bin/client -u karaf -p karaf version 2>&1"
> sometimes it will hang for ever.
>
> workaround:
> just recompile the karaf client main source code by removing below code:
> org.apache.karaf.client.Main
> line 194~211
> //
> if (!config.isBatch()) {
> new Thread() {
> public void run() {
> while (true) {
> try {
> int a = System.in.read();
> if (a == -1) {
> channel.close(true);
> break;
> }
> Thread.sleep(1000);
> } catch (Exception e) {
> //ignore
> }
> }
> }
> }.start();
> }
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (KARAF-6422) karaf client sometimes hang when executing command
[
https://issues.apache.org/jira/browse/KARAF-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned KARAF-6422:
---
Assignee: Freeman Fang
> karaf client sometimes hang when executing command
> --
>
> Key: KARAF-6422
> URL: https://issues.apache.org/jira/browse/KARAF-6422
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.6
> Environment: redhat7.6
> jdk1.8.0_221
> newly installed latest karaf runtime version 4.2.6, no any changes to it.
> just start it by bin/start
>Reporter: wenjie sun
>Assignee: Freeman Fang
>Priority: Major
>
> when my script invoke below command after karaf started:
> "/opt/apache/karaf/bin/client -u karaf -p karaf version 2>&1"
> sometimes it will hang for ever.
>
> workaround:
> just recompile the karaf client main source code by removing below code:
> org.apache.karaf.client.Main
> line 194~211
> //
> if (!config.isBatch()) {
> new Thread() {
> public void run() {
> while (true) {
> try {
> int a = System.in.read();
> if (a == -1) {
> channel.close(true);
> break;
> }
> Thread.sleep(1000);
> } catch (Exception e) {
> //ignore
> }
> }
> }
> }.start();
> }
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (KARAF-6419) How to add more jars to /lib/jdk9plus folder in karaf4.2.6
[ https://issues.apache.org/jira/browse/KARAF-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6419. - Resolution: Information Provided > How to add more jars to /lib/jdk9plus folder in karaf4.2.6 > -- > > Key: KARAF-6419 > URL: https://issues.apache.org/jira/browse/KARAF-6419 > Project: Karaf > Issue Type: Question > Components: karaf >Affects Versions: 4.2.6 >Reporter: Aditya Kancherla >Assignee: Freeman Fang >Priority: Major > > Hi Team, > > we are migrating karaf 4.0.9 to 4.2.6 as we are migrating jdk1.8 to jdk11. > Can you please let me know how to add jaxb-api.jar and jaxws-api.jar into > karaf 4.2.6 /lib/jdk9plus folder. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (KARAF-6419) How to add more jars to /lib/jdk9plus folder in karaf4.2.6
[ https://issues.apache.org/jira/browse/KARAF-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931478#comment-16931478 ] Freeman Fang commented on KARAF-6419: - Hi [~akancherla], You don't need to do it by yourself. For jaxb, it's already in this folder, but it's here because launch karaf itself needs jaxb. For the jaxws, you should install it as normal OSGi bundle, just same as other bundles needed(and we do this in cxf karaf features.xml). Best Regards Freeman > How to add more jars to /lib/jdk9plus folder in karaf4.2.6 > -- > > Key: KARAF-6419 > URL: https://issues.apache.org/jira/browse/KARAF-6419 > Project: Karaf > Issue Type: Question > Components: karaf >Affects Versions: 4.2.6 >Reporter: Aditya Kancherla >Assignee: Freeman Fang >Priority: Major > > Hi Team, > > we are migrating karaf 4.0.9 to 4.2.6 as we are migrating jdk1.8 to jdk11. > Can you please let me know how to add jaxb-api.jar and jaxws-api.jar into > karaf 4.2.6 /lib/jdk9plus folder. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (KARAF-6419) How to add more jars to /lib/jdk9plus folder in karaf4.2.6
[ https://issues.apache.org/jira/browse/KARAF-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6419: --- Assignee: Freeman Fang > How to add more jars to /lib/jdk9plus folder in karaf4.2.6 > -- > > Key: KARAF-6419 > URL: https://issues.apache.org/jira/browse/KARAF-6419 > Project: Karaf > Issue Type: Question > Components: karaf >Affects Versions: 4.2.6 >Reporter: Aditya Kancherla >Assignee: Freeman Fang >Priority: Major > > Hi Team, > > we are migrating karaf 4.0.9 to 4.2.6 as we are migrating jdk1.8 to jdk11. > Can you please let me know how to add jaxb-api.jar and jaxws-api.jar into > karaf 4.2.6 /lib/jdk9plus folder. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (KARAF-6413) Windows Service fails to start initially
[ https://issues.apache.org/jira/browse/KARAF-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6413. - Fix Version/s: 4.2.7 4.3.0 Resolution: Fixed > Windows Service fails to start initially > > > Key: KARAF-6413 > URL: https://issues.apache.org/jira/browse/KARAF-6413 > Project: Karaf > Issue Type: Bug > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.7 > > > When run karaf-service-win.exe, the cmd prompt console starts and closes > without any errors, but the service does not start. > The problem seems to be that, when initially starting the windows service, > the data folder is not created. If I manually run `bin\karaf.bat start`, then > the data folder is created and the service starts to work. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (KARAF-6413) Windows Service fails to start initially
[ https://issues.apache.org/jira/browse/KARAF-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926828#comment-16926828 ] Freeman Fang commented on KARAF-6413: - This is a winsw bug which already get resolved a long time ago The winsw version we currently use is 1.18, this is way too old, we should upgrade to the latest version to pick this fix > Windows Service fails to start initially > > > Key: KARAF-6413 > URL: https://issues.apache.org/jira/browse/KARAF-6413 > Project: Karaf > Issue Type: Bug > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > When run karaf-service-win.exe, the cmd prompt console starts and closes > without any errors, but the service does not start. > The problem seems to be that, when initially starting the windows service, > the data folder is not created. If I manually run `bin\karaf.bat start`, then > the data folder is created and the service starts to work. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (KARAF-6413) Windows Service fails to start initially
Freeman Fang created KARAF-6413: --- Summary: Windows Service fails to start initially Key: KARAF-6413 URL: https://issues.apache.org/jira/browse/KARAF-6413 Project: Karaf Issue Type: Bug Components: karaf Reporter: Freeman Fang When run karaf-service-win.exe, the cmd prompt console starts and closes without any errors, but the service does not start. The problem seems to be that, when initially starting the windows service, the data folder is not created. If I manually run `bin\karaf.bat start`, then the data folder is created and the service starts to work. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work started] (KARAF-6413) Windows Service fails to start initially
[ https://issues.apache.org/jira/browse/KARAF-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6413 started by Freeman Fang. --- > Windows Service fails to start initially > > > Key: KARAF-6413 > URL: https://issues.apache.org/jira/browse/KARAF-6413 > Project: Karaf > Issue Type: Bug > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > When run karaf-service-win.exe, the cmd prompt console starts and closes > without any errors, but the service does not start. > The problem seems to be that, when initially starting the windows service, > the data folder is not created. If I manually run `bin\karaf.bat start`, then > the data folder is created and the service starts to work. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (KARAF-6413) Windows Service fails to start initially
[ https://issues.apache.org/jira/browse/KARAF-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6413: --- Assignee: Freeman Fang > Windows Service fails to start initially > > > Key: KARAF-6413 > URL: https://issues.apache.org/jira/browse/KARAF-6413 > Project: Karaf > Issue Type: Bug > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > When run karaf-service-win.exe, the cmd prompt console starts and closes > without any errors, but the service does not start. > The problem seems to be that, when initially starting the windows service, > the data folder is not created. If I manually run `bin\karaf.bat start`, then > the data folder is created and the service starts to work. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (KARAF-6380) Karaf does not pass configs with dashes to ManagedService
[
https://issues.apache.org/jira/browse/KARAF-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved KARAF-6380.
-
Resolution: Information Provided
> Karaf does not pass configs with dashes to ManagedService
> -
>
> Key: KARAF-6380
> URL: https://issues.apache.org/jira/browse/KARAF-6380
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.6
>Reporter: Kamil
>Assignee: Freeman Fang
>Priority: Major
>
> I have a bundle with this code in activator:
>
> {code:java}
> @Override
> public final void start(final BundleContext bundleContext) throws
> InterruptedException {
> // final String pid = "foo.bar.e35a73c8-f720-4652-83bb-2b9ed79ea51e"; //does
> not work!
> final String pid = "foo.bar.e35a73c8f720465283bb2b9ed79ea51e";
> ServiceRegistration serviceReg =
> bundleContext.registerService(ManagedService.class, new ConfigUpdater(), new
> Hashtable<>(singletonMap(Constants.SERVICE_PID, pid)));
> }
> {code}
> where:
> {code:java}
> private final class ConfigUpdater implements ManagedService {
> @Override
> public void updated(final Dictionary config) throws
> ConfigurationException {
> if (config == null) {
> System.out.println("The config is null!");
> return;
> }
> }
> }
> {code}
> and two files in $KARAF_HOME/etc:
> * foo.bar.e35a73c8-f720-4652-83bb-2b9ed79ea51e.cfg
> * foo.bar.e35a73c8f720465283bb2b9ed79ea51e.cfg
> the first pid gives null as a config, while the second works
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (KARAF-6380) Karaf does not pass configs with dashes to ManagedService
[
https://issues.apache.org/jira/browse/KARAF-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907410#comment-16907410
]
Freeman Fang commented on KARAF-6380:
-
Hi [~eximius],
This is a known behavior, and it lies in Apache Felix.
{code}
PID strings (symbolic-name syntax) allow hyphens in the OSGI specification.
However, hyphens are interpreted by Apache Felix.fileinstall and config:edit
shell commands to differentiate a "managed service" and "managed service
factory". Therefore, it is recommended to not use hyphens elsewhere in a PID
string.
{code}
So it's not a Karaf problem.
Cheers
Freeman
> Karaf does not pass configs with dashes to ManagedService
> -
>
> Key: KARAF-6380
> URL: https://issues.apache.org/jira/browse/KARAF-6380
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.6
>Reporter: Kamil
>Assignee: Freeman Fang
>Priority: Major
>
> I have a bundle with this code in activator:
>
> {code:java}
> @Override
> public final void start(final BundleContext bundleContext) throws
> InterruptedException {
> // final String pid = "foo.bar.e35a73c8-f720-4652-83bb-2b9ed79ea51e"; //does
> not work!
> final String pid = "foo.bar.e35a73c8f720465283bb2b9ed79ea51e";
> ServiceRegistration serviceReg =
> bundleContext.registerService(ManagedService.class, new ConfigUpdater(), new
> Hashtable<>(singletonMap(Constants.SERVICE_PID, pid)));
> }
> {code}
> where:
> {code:java}
> private final class ConfigUpdater implements ManagedService {
> @Override
> public void updated(final Dictionary config) throws
> ConfigurationException {
> if (config == null) {
> System.out.println("The config is null!");
> return;
> }
> }
> }
> {code}
> and two files in $KARAF_HOME/etc:
> * foo.bar.e35a73c8-f720-4652-83bb-2b9ed79ea51e.cfg
> * foo.bar.e35a73c8f720465283bb2b9ed79ea51e.cfg
> the first pid gives null as a config, while the second works
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (KARAF-6380) Karaf does not pass configs with dashes to ManagedService
[
https://issues.apache.org/jira/browse/KARAF-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned KARAF-6380:
---
Assignee: Freeman Fang
> Karaf does not pass configs with dashes to ManagedService
> -
>
> Key: KARAF-6380
> URL: https://issues.apache.org/jira/browse/KARAF-6380
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.6
>Reporter: Kamil
>Assignee: Freeman Fang
>Priority: Major
>
> I have a bundle with this code in activator:
>
> {code:java}
> @Override
> public final void start(final BundleContext bundleContext) throws
> InterruptedException {
> // final String pid = "foo.bar.e35a73c8-f720-4652-83bb-2b9ed79ea51e"; //does
> not work!
> final String pid = "foo.bar.e35a73c8f720465283bb2b9ed79ea51e";
> ServiceRegistration serviceReg =
> bundleContext.registerService(ManagedService.class, new ConfigUpdater(), new
> Hashtable<>(singletonMap(Constants.SERVICE_PID, pid)));
> }
> {code}
> where:
> {code:java}
> private final class ConfigUpdater implements ManagedService {
> @Override
> public void updated(final Dictionary config) throws
> ConfigurationException {
> if (config == null) {
> System.out.println("The config is null!");
> return;
> }
> }
> }
> {code}
> and two files in $KARAF_HOME/etc:
> * foo.bar.e35a73c8-f720-4652-83bb-2b9ed79ea51e.cfg
> * foo.bar.e35a73c8f720465283bb2b9ed79ea51e.cfg
> the first pid gives null as a config, while the second works
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (KARAF-6361) jre.properties lists CORBA packages for jre-11
[ https://issues.apache.org/jira/browse/KARAF-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897053#comment-16897053 ] Freeman Fang edited comment on KARAF-6361 at 7/31/19 11:16 AM: --- CXF 3.3 is the first version to support JDK11, so I think we should upgrade SoapExampleTest to use CXF 3.3.x. I will take care of it was (Author: ffang): CXF 3.3 is the first version to support JDK11, so I think we should disable SoapExampleTest when build Karaf with JDK11. I will take care of it > jre.properties lists CORBA packages for jre-11 > -- > > Key: KARAF-6361 > URL: https://issues.apache.org/jira/browse/KARAF-6361 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.0, 4.2.6 >Reporter: Robert Varga >Assignee: Freeman Fang >Priority: Minor > Fix For: 4.3.0, 4.2.7 > > > [https://openjdk.java.net/jeps/320] removed Corba (and others), so the list > of JRE-provided packages is different between jre-9 and jre-11, but jre-11 is > an alias for jre-9. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (KARAF-6361) jre.properties lists CORBA packages for jre-11
[ https://issues.apache.org/jira/browse/KARAF-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897053#comment-16897053 ] Freeman Fang edited comment on KARAF-6361 at 7/31/19 11:12 AM: --- CXF 3.3 is the first version to support JDK11, so I think we should disable SoapExampleTest when build Karaf with JDK11. I will take care of it was (Author: ffang): CXF 3.3 is the first version to support JDK11, so I think we should disable SoapExampleTest when build Karaf with JDK11 > jre.properties lists CORBA packages for jre-11 > -- > > Key: KARAF-6361 > URL: https://issues.apache.org/jira/browse/KARAF-6361 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.0, 4.2.6 >Reporter: Robert Varga >Assignee: Freeman Fang >Priority: Minor > Fix For: 4.3.0, 4.2.7 > > > [https://openjdk.java.net/jeps/320] removed Corba (and others), so the list > of JRE-provided packages is different between jre-9 and jre-11, but jre-11 is > an alias for jre-9. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (KARAF-6361) jre.properties lists CORBA packages for jre-11
[ https://issues.apache.org/jira/browse/KARAF-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6361: --- Assignee: Freeman Fang (was: Jean-Baptiste Onofré) > jre.properties lists CORBA packages for jre-11 > -- > > Key: KARAF-6361 > URL: https://issues.apache.org/jira/browse/KARAF-6361 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.0, 4.2.6 >Reporter: Robert Varga >Assignee: Freeman Fang >Priority: Minor > Fix For: 4.3.0, 4.2.7 > > > [https://openjdk.java.net/jeps/320] removed Corba (and others), so the list > of JRE-provided packages is different between jre-9 and jre-11, but jre-11 is > an alias for jre-9. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (KARAF-6361) jre.properties lists CORBA packages for jre-11
[ https://issues.apache.org/jira/browse/KARAF-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897053#comment-16897053 ] Freeman Fang commented on KARAF-6361: - CXF 3.3 is the first version to support JDK11, so I think we should disable SoapExampleTest when build Karaf with JDK11 > jre.properties lists CORBA packages for jre-11 > -- > > Key: KARAF-6361 > URL: https://issues.apache.org/jira/browse/KARAF-6361 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.0, 4.2.6 >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.3.0, 4.2.7 > > > [https://openjdk.java.net/jeps/320] removed Corba (and others), so the list > of JRE-provided packages is different between jre-9 and jre-11, but jre-11 is > an alias for jre-9. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (KARAF-6361) jre.properties lists CORBA packages for jre-11
[ https://issues.apache.org/jira/browse/KARAF-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6361. - Resolution: Fixed Fix Version/s: 4.2.7 4.3.0 > jre.properties lists CORBA packages for jre-11 > -- > > Key: KARAF-6361 > URL: https://issues.apache.org/jira/browse/KARAF-6361 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.0, 4.2.6 >Reporter: Robert Varga >Assignee: Freeman Fang >Priority: Minor > Fix For: 4.3.0, 4.2.7 > > > [https://openjdk.java.net/jeps/320] removed Corba (and others), so the list > of JRE-provided packages is different between jre-9 and jre-11, but jre-11 is > an alias for jre-9. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Work started] (KARAF-6362) [karaf-maven-plugin] client goal:only the fist command in script file could be executed
[ https://issues.apache.org/jira/browse/KARAF-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6362 started by Freeman Fang. --- > [karaf-maven-plugin] client goal:only the fist command in script file could > be executed > --- > > Key: KARAF-6362 > URL: https://issues.apache.org/jira/browse/KARAF-6362 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > All commands from script are evaluated with same rank and because we have a > Set with Rank as comparator so only one command from the script file is > stored, others are ignored. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KARAF-6362) [karaf-maven-plugin] client goal:only the fist command in script file could be executed
Freeman Fang created KARAF-6362: --- Summary: [karaf-maven-plugin] client goal:only the fist command in script file could be executed Key: KARAF-6362 URL: https://issues.apache.org/jira/browse/KARAF-6362 Project: Karaf Issue Type: Bug Reporter: Freeman Fang All commands from script are evaluated with same rank and because we have a Set with Rank as comparator so only one command from the script file is stored, others are ignored. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (KARAF-6362) [karaf-maven-plugin] client goal:only the fist command in script file could be executed
[ https://issues.apache.org/jira/browse/KARAF-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6362: --- Assignee: Freeman Fang > [karaf-maven-plugin] client goal:only the fist command in script file could > be executed > --- > > Key: KARAF-6362 > URL: https://issues.apache.org/jira/browse/KARAF-6362 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > All commands from script are evaluated with same rank and because we have a > Set with Rank as comparator so only one command from the script file is > stored, others are ignored. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (KARAF-6361) jre.properties lists CORBA packages for jre-11
[ https://issues.apache.org/jira/browse/KARAF-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16889024#comment-16889024 ] Freeman Fang commented on KARAF-6361: - As java11 is the LTS version and I believe no one really use JDK9&10 now, I will remove those corba package from jre-9 onwards > jre.properties lists CORBA packages for jre-11 > -- > > Key: KARAF-6361 > URL: https://issues.apache.org/jira/browse/KARAF-6361 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.0, 4.2.6 >Reporter: Robert Varga >Assignee: Freeman Fang >Priority: Minor > > [https://openjdk.java.net/jeps/320] removed Corba (and others), so the list > of JRE-provided packages is different between jre-9 and jre-11, but jre-11 is > an alias for jre-9. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Work started] (KARAF-6361) jre.properties lists CORBA packages for jre-11
[ https://issues.apache.org/jira/browse/KARAF-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6361 started by Freeman Fang. --- > jre.properties lists CORBA packages for jre-11 > -- > > Key: KARAF-6361 > URL: https://issues.apache.org/jira/browse/KARAF-6361 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.0, 4.2.6 >Reporter: Robert Varga >Assignee: Freeman Fang >Priority: Minor > > [https://openjdk.java.net/jeps/320] removed Corba (and others), so the list > of JRE-provided packages is different between jre-9 and jre-11, but jre-11 is > an alias for jre-9. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (KARAF-6361) jre.properties lists CORBA packages for jre-11
[ https://issues.apache.org/jira/browse/KARAF-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6361: --- Assignee: Freeman Fang > jre.properties lists CORBA packages for jre-11 > -- > > Key: KARAF-6361 > URL: https://issues.apache.org/jira/browse/KARAF-6361 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.0, 4.2.6 >Reporter: Robert Varga >Assignee: Freeman Fang >Priority: Minor > > [https://openjdk.java.net/jeps/320] removed Corba (and others), so the list > of JRE-provided packages is different between jre-9 and jre-11, but jre-11 is > an alias for jre-9. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (KARAF-6359) Clients can log in with encrypted passwords
[ https://issues.apache.org/jira/browse/KARAF-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16887146#comment-16887146 ] Freeman Fang commented on KARAF-6359: - patch applied on behalf of [~coheigea] with thanks! > Clients can log in with encrypted passwords > --- > > Key: KARAF-6359 > URL: https://issues.apache.org/jira/browse/KARAF-6359 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.6 >Reporter: Colm O hEigeartaigh >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.7 > > > https://issues.apache.org/jira/browse/KARAF-5316 introduced a regression in > Karaf 4.2.0, that clients could log in using encrypted passwords. So for > example, if you enable JAAS encryption, and run bin/client it logs in without > prompting for a password - as the JAAS code falls back to comparing the > received (encrypted) password directly against the stored value. In 4.1.x, it > always prompted for a password when encryption as enabled. IMO the 4.1.x > behavior was the correct one. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (KARAF-6359) Clients can log in with encrypted passwords
[ https://issues.apache.org/jira/browse/KARAF-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6359. - Resolution: Fixed > Clients can log in with encrypted passwords > --- > > Key: KARAF-6359 > URL: https://issues.apache.org/jira/browse/KARAF-6359 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.6 >Reporter: Colm O hEigeartaigh >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.7 > > > https://issues.apache.org/jira/browse/KARAF-5316 introduced a regression in > Karaf 4.2.0, that clients could log in using encrypted passwords. So for > example, if you enable JAAS encryption, and run bin/client it logs in without > prompting for a password - as the JAAS code falls back to comparing the > received (encrypted) password directly against the stored value. In 4.1.x, it > always prompted for a password when encryption as enabled. IMO the 4.1.x > behavior was the correct one. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Work started] (KARAF-6359) Clients can log in with encrypted passwords
[ https://issues.apache.org/jira/browse/KARAF-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6359 started by Freeman Fang. --- > Clients can log in with encrypted passwords > --- > > Key: KARAF-6359 > URL: https://issues.apache.org/jira/browse/KARAF-6359 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.6 >Reporter: Colm O hEigeartaigh >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.7 > > > https://issues.apache.org/jira/browse/KARAF-5316 introduced a regression in > Karaf 4.2.0, that clients could log in using encrypted passwords. So for > example, if you enable JAAS encryption, and run bin/client it logs in without > prompting for a password - as the JAAS code falls back to comparing the > received (encrypted) password directly against the stored value. In 4.1.x, it > always prompted for a password when encryption as enabled. IMO the 4.1.x > behavior was the correct one. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (KARAF-6359) Clients can log in with encrypted passwords
[ https://issues.apache.org/jira/browse/KARAF-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6359: --- Assignee: Freeman Fang > Clients can log in with encrypted passwords > --- > > Key: KARAF-6359 > URL: https://issues.apache.org/jira/browse/KARAF-6359 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.6 >Reporter: Colm O hEigeartaigh >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.7 > > > https://issues.apache.org/jira/browse/KARAF-5316 introduced a regression in > Karaf 4.2.0, that clients could log in using encrypted passwords. So for > example, if you enable JAAS encryption, and run bin/client it logs in without > prompting for a password - as the JAAS code falls back to comparing the > received (encrypted) password directly against the stored value. In 4.1.x, it > always prompted for a password when encryption as enabled. IMO the 4.1.x > behavior was the correct one. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (KARAF-6358) jre.properties exports javax.annotation packages as 1.0 vs 1.3
[ https://issues.apache.org/jira/browse/KARAF-6358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6358. - Resolution: Fixed Fix Version/s: 4.2.7 4.3.0 > jre.properties exports javax.annotation packages as 1.0 vs 1.3 > -- > > Key: KARAF-6358 > URL: https://issues.apache.org/jira/browse/KARAF-6358 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.5, 4.2.6 > Environment: Karaf 4.2.5 on Java 9. >Reporter: Jim Ziesig >Assignee: Freeman Fang >Priority: Minor > Fix For: 4.3.0, 4.2.7 > > > KARAF-6128 updated the version of javax.annotation to 1.3, but the > etc/jre.properties file is still exporting the javax.annotation and > javax.annotation.processing packages as version 1.0. This leads features > such as CXF 3.3.2 to install a javax.annotation-api 1.3 bundle when it > shouldn't need to do so. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Work started] (KARAF-6358) jre.properties exports javax.annotation packages as 1.0 vs 1.3
[ https://issues.apache.org/jira/browse/KARAF-6358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6358 started by Freeman Fang. --- > jre.properties exports javax.annotation packages as 1.0 vs 1.3 > -- > > Key: KARAF-6358 > URL: https://issues.apache.org/jira/browse/KARAF-6358 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.5, 4.2.6 > Environment: Karaf 4.2.5 on Java 9. >Reporter: Jim Ziesig >Assignee: Freeman Fang >Priority: Minor > > KARAF-6128 updated the version of javax.annotation to 1.3, but the > etc/jre.properties file is still exporting the javax.annotation and > javax.annotation.processing packages as version 1.0. This leads features > such as CXF 3.3.2 to install a javax.annotation-api 1.3 bundle when it > shouldn't need to do so. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (KARAF-6358) jre.properties exports javax.annotation packages as 1.0 vs 1.3
[ https://issues.apache.org/jira/browse/KARAF-6358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6358: --- Assignee: Freeman Fang > jre.properties exports javax.annotation packages as 1.0 vs 1.3 > -- > > Key: KARAF-6358 > URL: https://issues.apache.org/jira/browse/KARAF-6358 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.5, 4.2.6 > Environment: Karaf 4.2.5 on Java 9. >Reporter: Jim Ziesig >Assignee: Freeman Fang >Priority: Minor > > KARAF-6128 updated the version of javax.annotation to 1.3, but the > etc/jre.properties file is still exporting the javax.annotation and > javax.annotation.processing packages as version 1.0. This leads features > such as CXF 3.3.2 to install a javax.annotation-api 1.3 bundle when it > shouldn't need to do so. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (KARAF-6346) Support FATAL level for log console commands
[ https://issues.apache.org/jira/browse/KARAF-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6346. - Resolution: Fixed Fix Version/s: 4.2.7 4.3.0 > Support FATAL level for log console commands > > > Key: KARAF-6346 > URL: https://issues.apache.org/jira/browse/KARAF-6346 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.2.6 >Reporter: Emily Berk >Assignee: Freeman Fang >Priority: Trivial > Fix For: 4.3.0, 4.2.7 > > > My project uses log4j2. I would like to be able to execute the command > `log:set FATAL `. > * > https://github.com/apache/karaf/blob/karaf-4.2.6/log/src/main/java/org/apache/karaf/log/command/SetLogLevel.java > * > https://github.com/apache/karaf/blob/karaf-4.2.6/log/src/main/java/org/apache/karaf/log/core/Level.java > * > https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/Level.html > A work-around is manually editing the org.ops4j.pax.logging.cfg or > "org.ops4j.pax.logging.log4j2.config.file". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-6346) Support FATAL level for log console commands
[ https://issues.apache.org/jira/browse/KARAF-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6346 started by Freeman Fang. --- > Support FATAL level for log console commands > > > Key: KARAF-6346 > URL: https://issues.apache.org/jira/browse/KARAF-6346 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.2.6 >Reporter: Emily Berk >Assignee: Freeman Fang >Priority: Trivial > > My project uses log4j2. I would like to be able to execute the command > `log:set FATAL `. > * > https://github.com/apache/karaf/blob/karaf-4.2.6/log/src/main/java/org/apache/karaf/log/command/SetLogLevel.java > * > https://github.com/apache/karaf/blob/karaf-4.2.6/log/src/main/java/org/apache/karaf/log/core/Level.java > * > https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/Level.html > A work-around is manually editing the org.ops4j.pax.logging.cfg or > "org.ops4j.pax.logging.log4j2.config.file". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6346) Support FATAL level for log console commands
[ https://issues.apache.org/jira/browse/KARAF-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6346: --- Assignee: Freeman Fang > Support FATAL level for log console commands > > > Key: KARAF-6346 > URL: https://issues.apache.org/jira/browse/KARAF-6346 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.2.6 >Reporter: Emily Berk >Assignee: Freeman Fang >Priority: Trivial > > My project uses log4j2. I would like to be able to execute the command > `log:set FATAL `. > * > https://github.com/apache/karaf/blob/karaf-4.2.6/log/src/main/java/org/apache/karaf/log/command/SetLogLevel.java > * > https://github.com/apache/karaf/blob/karaf-4.2.6/log/src/main/java/org/apache/karaf/log/core/Level.java > * > https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/Level.html > A work-around is manually editing the org.ops4j.pax.logging.cfg or > "org.ops4j.pax.logging.log4j2.config.file". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6328) Karaf MBeanServer doesn't full start with JDK 11
[
https://issues.apache.org/jira/browse/KARAF-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861355#comment-16861355
]
Freeman Fang commented on KARAF-6328:
-
Hi [~jbonofre],
How I can reproduce this?
I just tried with Karaf 4.2.6 kit on OpenJDK11 and it works for me.
Cheers
Freeman
> Karaf MBeanServer doesn't full start with JDK 11
>
>
> Key: KARAF-6328
> URL: https://issues.apache.org/jira/browse/KARAF-6328
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.7
>
>
> When starting Karaf with JDK 11, I notice:
> {code}
> Exception in thread "JMX Connector Thread
> [service:jmx:rmi://0.0.0.0:4/jndi/rmi://:1099/karaf-root]"
> java.lang.RuntimeException:
> Port already in use: 4;
> You may have started two containers. If you need to start a second container
> or the default ports are already in use update the config file
> etc/org.apache.karaf.management.cfg and change the Registry Port and Server
> Port to unused ports
> at
> org.apache.karaf.management.ConnectorServerFactory.lambda$init$0(ConnectorServerFactory.java:276)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Exception in thread "JMX Connector Thread
> [service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root]"
> java.lang.RuntimeException:
> Port already in use: 4;
> You may have started two containers. If you need to start a second container
> or the default ports are already in use update the config file
> etc/org.apache.karaf.management.cfg and change the Registry Port and Server
> Port to unused ports
> at
> org.apache.karaf.management.ConnectorServerFactory.lambda$init$0(ConnectorServerFactory.java:276)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
> even if I don't have any other Karaf instances running. The MBeanServer is
> not actually started and the user can't connect (with {{jconsole}} for
> instance).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6327) Build using JDK 12
[ https://issues.apache.org/jira/browse/KARAF-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861124#comment-16861124 ] Freeman Fang commented on KARAF-6327: - I'd like to close this one, using KARAF-6203 to track it. Thanks! Freeman > Build using JDK 12 > -- > > Key: KARAF-6327 > URL: https://issues.apache.org/jira/browse/KARAF-6327 > Project: Karaf > Issue Type: Task > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6327) Build using JDK 12
[ https://issues.apache.org/jira/browse/KARAF-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6327: --- Assignee: Freeman Fang (was: Jean-Baptiste Onofré) > Build using JDK 12 > -- > > Key: KARAF-6327 > URL: https://issues.apache.org/jira/browse/KARAF-6327 > Project: Karaf > Issue Type: Task > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6327) Build using JDK 12
[ https://issues.apache.org/jira/browse/KARAF-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6327. - Resolution: Duplicate > Build using JDK 12 > -- > > Key: KARAF-6327 > URL: https://issues.apache.org/jira/browse/KARAF-6327 > Project: Karaf > Issue Type: Task > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-2211) Command aliases don't show completers on
[ https://issues.apache.org/jira/browse/KARAF-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861051#comment-16861051 ] Freeman Fang commented on KARAF-2211: - completers works for alias for a long time > Command aliases don't show completers on > -- > > Key: KARAF-2211 > URL: https://issues.apache.org/jira/browse/KARAF-2211 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 2.2.10 > Environment: ServiceMix 4.5.0 > Java 1.6.0_31 > Windows XP >Reporter: Serge Starovoitenkov >Assignee: Freeman Fang >Priority: Major > > Command completers aren't accessible on when using command alias. Found > with commands: > 1. "features:*" - show completers; "feature:*" - no completers > 2. "shell:command-watch" - show completer; "watch" - no completers -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-2211) Command aliases don't show completers on
[ https://issues.apache.org/jira/browse/KARAF-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-2211. - Resolution: Implemented > Command aliases don't show completers on > -- > > Key: KARAF-2211 > URL: https://issues.apache.org/jira/browse/KARAF-2211 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 2.2.10 > Environment: ServiceMix 4.5.0 > Java 1.6.0_31 > Windows XP >Reporter: Serge Starovoitenkov >Assignee: Freeman Fang >Priority: Major > > Command completers aren't accessible on when using command alias. Found > with commands: > 1. "features:*" - show completers; "feature:*" - no completers > 2. "shell:command-watch" - show completer; "watch" - no completers -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6296) Upgrade to Jasypt 1.9.3
[ https://issues.apache.org/jira/browse/KARAF-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated KARAF-6296: Summary: Upgrade to Jasypt 1.9.3 (was: Upgrade to Jasypt 1.9.4) > Upgrade to Jasypt 1.9.3 > --- > > Key: KARAF-6296 > URL: https://issues.apache.org/jira/browse/KARAF-6296 > Project: Karaf > Issue Type: Improvement > Components: karaf >Affects Versions: 4.1.7 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Would be great to upgrade to Jasypt 1.9.3 > [http://www.jasypt.org/download.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6296) Upgrade to Jasypt 1.9.4
[ https://issues.apache.org/jira/browse/KARAF-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858955#comment-16858955 ] Freeman Fang commented on KARAF-6296: - No worries, I have already committed jasypt-spring31-1.9.3 and jasypt-1.9.3 bundle into servicemix, so once next batch of bundles get released we can update jasypt usage here. > Upgrade to Jasypt 1.9.4 > --- > > Key: KARAF-6296 > URL: https://issues.apache.org/jira/browse/KARAF-6296 > Project: Karaf > Issue Type: Improvement > Components: karaf >Affects Versions: 4.1.7 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Would be great to upgrade to Jasypt 1.9.3 > [http://www.jasypt.org/download.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6291) Static distribution does not work with cxf-jaxrs
[
https://issues.apache.org/jira/browse/KARAF-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved KARAF-6291.
-
Resolution: Information Provided
> Static distribution does not work with cxf-jaxrs
>
>
> Key: KARAF-6291
> URL: https://issues.apache.org/jira/browse/KARAF-6291
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Apache Karaf 4.2.5
> Apache CXF 3.3.2
> JDK 1.8.111
>Reporter: Alexander Komarov
>Assignee: Freeman Fang
>Priority: Major
> Attachments: jaxrs_static.out.gz
>
>
> Hello.
> I tried to run an example of a static distribution of karaf
> [https://github.com/apache/karaf/tree/master/examples/karaf-docker-example/karaf-docker-example-static-dist]
> and I added a cxf-jaxrs startupRepository and startupFeature .
> {code:xml}
>
>
> mvn:org.apache.cxf.karaf/apache-cxf/3.3.2/xml/features
>
> static-framework
> scr
> http-whiteboard
>
> karaf-docker-example-app
> cxf-jaxrs
>
> static
> true
> static
> 1.8
>
> {code}
> When I run the build "mnv clean install" I get an error:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.2.5:assembly
> (process-resources) on project karaf-docker-example-static-dist: Unable to
> build assembly: Unable to resolve root: missing requirement [root]
> osgi.identity; osgi.identity=wrap; type=karaf.feature; version=0;
> filter:="(&(osgi.identity=wrap)(type=karaf.feature)(version>=0.0.0))" [caused
> by: Unable to resolve wrap/2.6.1: missing requirement [wrap/2.6.1]
> osgi.identity; osgi.identity=org.ops4j.pax.url.wrap; type=osgi.bundle;
> version="[2.6.1,2.6.1]"; resolution:=mandatory [caused by: Unable to resolve
> org.ops4j.pax.url.wrap/2.6.1: missing requirement
> [org.ops4j.pax.url.wrap/2.6.1] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.slf4j)(version>=1.6.0)(!(version>=2.0.0)))"]]
> -> [Help 1]
> {noformat}
>
> See full output in attach.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KARAF-6291) Static distribution does not work with cxf-jaxrs
[
https://issues.apache.org/jira/browse/KARAF-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858779#comment-16858779
]
Freeman Fang edited comment on KARAF-6291 at 6/7/19 4:11 PM:
-
Hi [~protven],
Put everything into startupFeatures isn't a good practice IMO, the
startFeature will be turned into etc/startup.properties which has all
fundamental bundles(we can see those bundles as bootstrap bundles of karaf).
Putting cxf-jaxrs feature into bootFeatures works(everything in bootFeatures
will be loaded automatically as well when start customized karaf kit, after all
fundamental bundles and services are fully up).
Something like
{code}
+
mvn:org.apache.cxf.karaf/apache-cxf/3.3.2/xml/features
static-framework
scr
http-whiteboard
karaf-docker-example-app
+
+cxf-jaxrs
+
{code}
Freeman
was (Author: ffang):
Hi [~protven],
Put everything into startupFeatures isn't a good practice IMO, the
startFeature will be turned into etc/startup.properties which has all
fundamental bundles(we can see those bundles as bootstrap bundles of karaf).
Putting cxf-jaxrs feature into bootFeatures works.
Something like
{code}
+
mvn:org.apache.cxf.karaf/apache-cxf/3.3.2/xml/features
static-framework
scr
http-whiteboard
karaf-docker-example-app
+
+cxf-jaxrs
+
{code}
Freeman
> Static distribution does not work with cxf-jaxrs
>
>
> Key: KARAF-6291
> URL: https://issues.apache.org/jira/browse/KARAF-6291
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Apache Karaf 4.2.5
> Apache CXF 3.3.2
> JDK 1.8.111
>Reporter: Alexander Komarov
>Assignee: Freeman Fang
>Priority: Major
> Attachments: jaxrs_static.out.gz
>
>
> Hello.
> I tried to run an example of a static distribution of karaf
> [https://github.com/apache/karaf/tree/master/examples/karaf-docker-example/karaf-docker-example-static-dist]
> and I added a cxf-jaxrs startupRepository and startupFeature .
> {code:xml}
>
>
> mvn:org.apache.cxf.karaf/apache-cxf/3.3.2/xml/features
>
> static-framework
> scr
> http-whiteboard
>
> karaf-docker-example-app
> cxf-jaxrs
>
> static
> true
> static
> 1.8
>
> {code}
> When I run the build "mnv clean install" I get an error:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.2.5:assembly
> (process-resources) on project karaf-docker-example-static-dist: Unable to
> build assembly: Unable to resolve root: missing requirement [root]
> osgi.identity; osgi.identity=wrap; type=karaf.feature; version=0;
> filter:="(&(osgi.identity=wrap)(type=karaf.feature)(version>=0.0.0))" [caused
> by: Unable to resolve wrap/2.6.1: missing requirement [wrap/2.6.1]
> osgi.identity; osgi.identity=org.ops4j.pax.url.wrap; type=osgi.bundle;
> version="[2.6.1,2.6.1]"; resolution:=mandatory [caused by: Unable to resolve
> org.ops4j.pax.url.wrap/2.6.1: missing requirement
> [org.ops4j.pax.url.wrap/2.6.1] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.slf4j)(version>=1.6.0)(!(version>=2.0.0)))"]]
> -> [Help 1]
> {noformat}
>
> See full output in attach.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6291) Static distribution does not work with cxf-jaxrs
[
https://issues.apache.org/jira/browse/KARAF-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858779#comment-16858779
]
Freeman Fang commented on KARAF-6291:
-
Hi [~protven],
Put everything into startupFeatures isn't a good practice IMO, the
startFeature will be turned into etc/startup.properties which has all
fundamental bundles(we can see those bundles as bootstrap bundles of karaf).
Putting cxf-jaxrs feature into bootFeatures works.
Something like
{code}
+
mvn:org.apache.cxf.karaf/apache-cxf/3.3.2/xml/features
static-framework
scr
http-whiteboard
karaf-docker-example-app
+
+cxf-jaxrs
+
{code}
Freeman
> Static distribution does not work with cxf-jaxrs
>
>
> Key: KARAF-6291
> URL: https://issues.apache.org/jira/browse/KARAF-6291
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Apache Karaf 4.2.5
> Apache CXF 3.3.2
> JDK 1.8.111
>Reporter: Alexander Komarov
>Assignee: Freeman Fang
>Priority: Major
> Attachments: jaxrs_static.out.gz
>
>
> Hello.
> I tried to run an example of a static distribution of karaf
> [https://github.com/apache/karaf/tree/master/examples/karaf-docker-example/karaf-docker-example-static-dist]
> and I added a cxf-jaxrs startupRepository and startupFeature .
> {code:xml}
>
>
> mvn:org.apache.cxf.karaf/apache-cxf/3.3.2/xml/features
>
> static-framework
> scr
> http-whiteboard
>
> karaf-docker-example-app
> cxf-jaxrs
>
> static
> true
> static
> 1.8
>
> {code}
> When I run the build "mnv clean install" I get an error:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.2.5:assembly
> (process-resources) on project karaf-docker-example-static-dist: Unable to
> build assembly: Unable to resolve root: missing requirement [root]
> osgi.identity; osgi.identity=wrap; type=karaf.feature; version=0;
> filter:="(&(osgi.identity=wrap)(type=karaf.feature)(version>=0.0.0))" [caused
> by: Unable to resolve wrap/2.6.1: missing requirement [wrap/2.6.1]
> osgi.identity; osgi.identity=org.ops4j.pax.url.wrap; type=osgi.bundle;
> version="[2.6.1,2.6.1]"; resolution:=mandatory [caused by: Unable to resolve
> org.ops4j.pax.url.wrap/2.6.1: missing requirement
> [org.ops4j.pax.url.wrap/2.6.1] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.slf4j)(version>=1.6.0)(!(version>=2.0.0)))"]]
> -> [Help 1]
> {noformat}
>
> See full output in attach.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work started] (KARAF-6291) Static distribution does not work with cxf-jaxrs
[
https://issues.apache.org/jira/browse/KARAF-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KARAF-6291 started by Freeman Fang.
---
> Static distribution does not work with cxf-jaxrs
>
>
> Key: KARAF-6291
> URL: https://issues.apache.org/jira/browse/KARAF-6291
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Apache Karaf 4.2.5
> Apache CXF 3.3.2
> JDK 1.8.111
>Reporter: Alexander Komarov
>Assignee: Freeman Fang
>Priority: Major
> Attachments: jaxrs_static.out.gz
>
>
> Hello.
> I tried to run an example of a static distribution of karaf
> [https://github.com/apache/karaf/tree/master/examples/karaf-docker-example/karaf-docker-example-static-dist]
> and I added a cxf-jaxrs startupRepository and startupFeature .
> {code:xml}
>
>
> mvn:org.apache.cxf.karaf/apache-cxf/3.3.2/xml/features
>
> static-framework
> scr
> http-whiteboard
>
> karaf-docker-example-app
> cxf-jaxrs
>
> static
> true
> static
> 1.8
>
> {code}
> When I run the build "mnv clean install" I get an error:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.2.5:assembly
> (process-resources) on project karaf-docker-example-static-dist: Unable to
> build assembly: Unable to resolve root: missing requirement [root]
> osgi.identity; osgi.identity=wrap; type=karaf.feature; version=0;
> filter:="(&(osgi.identity=wrap)(type=karaf.feature)(version>=0.0.0))" [caused
> by: Unable to resolve wrap/2.6.1: missing requirement [wrap/2.6.1]
> osgi.identity; osgi.identity=org.ops4j.pax.url.wrap; type=osgi.bundle;
> version="[2.6.1,2.6.1]"; resolution:=mandatory [caused by: Unable to resolve
> org.ops4j.pax.url.wrap/2.6.1: missing requirement
> [org.ops4j.pax.url.wrap/2.6.1] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.slf4j)(version>=1.6.0)(!(version>=2.0.0)))"]]
> -> [Help 1]
> {noformat}
>
> See full output in attach.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6296) Upgrade to Jasypt 1.9.3
[ https://issues.apache.org/jira/browse/KARAF-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855030#comment-16855030 ] Freeman Fang commented on KARAF-6296: - Yup, seems we should > Upgrade to Jasypt 1.9.3 > --- > > Key: KARAF-6296 > URL: https://issues.apache.org/jira/browse/KARAF-6296 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.1.7 >Reporter: Martin Lichtin >Assignee: Freeman Fang >Priority: Major > > Would be great to upgrade to Jasypt 1.9.3 > [http://www.jasypt.org/download.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KARAF-6296) Upgrade to Jasypt 1.9.3
[ https://issues.apache.org/jira/browse/KARAF-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855003#comment-16855003 ] Freeman Fang edited comment on KARAF-6296 at 6/3/19 8:10 PM: - need a servicemix wrapped jasypt 1.9.3 bundle first https://issues.apache.org/jira/browse/SM-4099 was (Author: ffang): need a servicemix wrapped jasypt 1.9.3 bundle first https://issues.apache.org/jira/browse/KARAF-6296 > Upgrade to Jasypt 1.9.3 > --- > > Key: KARAF-6296 > URL: https://issues.apache.org/jira/browse/KARAF-6296 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.1.7 >Reporter: Martin Lichtin >Assignee: Freeman Fang >Priority: Major > > Would be great to upgrade to Jasypt 1.9.3 > [http://www.jasypt.org/download.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6296) Upgrade to Jasypt 1.9.3
[ https://issues.apache.org/jira/browse/KARAF-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855003#comment-16855003 ] Freeman Fang commented on KARAF-6296: - need a servicemix wrapped jasypt 1.9.3 bundle first https://issues.apache.org/jira/browse/KARAF-6296 > Upgrade to Jasypt 1.9.3 > --- > > Key: KARAF-6296 > URL: https://issues.apache.org/jira/browse/KARAF-6296 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.1.7 >Reporter: Martin Lichtin >Assignee: Freeman Fang >Priority: Major > > Would be great to upgrade to Jasypt 1.9.3 > [http://www.jasypt.org/download.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6291) Static distribution does not work with cxf-jaxrs
[
https://issues.apache.org/jira/browse/KARAF-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned KARAF-6291:
---
Assignee: Freeman Fang
> Static distribution does not work with cxf-jaxrs
>
>
> Key: KARAF-6291
> URL: https://issues.apache.org/jira/browse/KARAF-6291
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Apache Karaf 4.2.5
> Apache CXF 3.3.2
> JDK 1.8.111
>Reporter: Alexander Komarov
>Assignee: Freeman Fang
>Priority: Major
> Attachments: jaxrs_static.out.gz
>
>
> Hello.
> I tried to run an example of a static distribution of karaf
> [https://github.com/apache/karaf/tree/master/examples/karaf-docker-example/karaf-docker-example-static-dist]
> and I added a cxf-jaxrs startupRepository and startupFeature .
> {code:xml}
>
>
> mvn:org.apache.cxf.karaf/apache-cxf/3.3.2/xml/features
>
> static-framework
> scr
> http-whiteboard
>
> karaf-docker-example-app
> cxf-jaxrs
>
> static
> true
> static
> 1.8
>
> {code}
> When I run the build "mnv clean install" I get an error:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.2.5:assembly
> (process-resources) on project karaf-docker-example-static-dist: Unable to
> build assembly: Unable to resolve root: missing requirement [root]
> osgi.identity; osgi.identity=wrap; type=karaf.feature; version=0;
> filter:="(&(osgi.identity=wrap)(type=karaf.feature)(version>=0.0.0))" [caused
> by: Unable to resolve wrap/2.6.1: missing requirement [wrap/2.6.1]
> osgi.identity; osgi.identity=org.ops4j.pax.url.wrap; type=osgi.bundle;
> version="[2.6.1,2.6.1]"; resolution:=mandatory [caused by: Unable to resolve
> org.ops4j.pax.url.wrap/2.6.1: missing requirement
> [org.ops4j.pax.url.wrap/2.6.1] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.slf4j)(version>=1.6.0)(!(version>=2.0.0)))"]]
> -> [Help 1]
> {noformat}
>
> See full output in attach.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KARAF-6296) Upgrade to Jasypt 1.9.3
[ https://issues.apache.org/jira/browse/KARAF-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6296: --- Assignee: Freeman Fang > Upgrade to Jasypt 1.9.3 > --- > > Key: KARAF-6296 > URL: https://issues.apache.org/jira/browse/KARAF-6296 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.1.7 >Reporter: Martin Lichtin >Assignee: Freeman Fang >Priority: Major > > Would be great to upgrade to Jasypt 1.9.3 > [http://www.jasypt.org/download.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6298) master can't build with JDK11 again
[ https://issues.apache.org/jira/browse/KARAF-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6298. - Resolution: Fixed Fix Version/s: 4.2.6 4.3.0 > master can't build with JDK11 again > --- > > Key: KARAF-6298 > URL: https://issues.apache.org/jira/browse/KARAF-6298 > Project: Karaf > Issue Type: Task >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.6 > > > so far I ran into two issues with JDK11 > 1. > features/core/src/main/java/org/apache/karaf/features/internal/service/Deployer.java > has unused "org.omg.CORBA.DynAnyPackage.Invalid" > 2. new introduced SortedProperties class use TreeSet but can't guarantee all > elements in TreeSet implements Comparable interface -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-4154) javax.mail.Message.getContent() returns IMAPInputStream
[
https://issues.apache.org/jira/browse/KARAF-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853046#comment-16853046
]
Freeman Fang commented on KARAF-4154:
-
Hi [~eximius],
FYI, this is fixed by KARAF-6299.
Cheers
Freeman
> javax.mail.Message.getContent() returns IMAPInputStream
> ---
>
> Key: KARAF-4154
> URL: https://issues.apache.org/jira/browse/KARAF-4154
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: Linux Mint 17.2 Cinnamon
> Oracle JDK 1.7
>Reporter: Anton Johansson
>Assignee: Christian Schneider
>Priority: Critical
> Labels: javax.mail, mail
>
> I'm using JavaMail API to read emails from Gmail IMAP. The emails are of type
> multipart. I open up a Store, then I open up a Folder ("INBOX"), then I get
> the messages from that folder.
> Outside of Karaf, when doing message.getContent() I get a
> javax.mail.internet.MimeMultipart object back. Doesn't matter if I use
> version 1.4.5 (the one that Karaf provides) or 1.5.4 (the latest).
> Inside Karaf, I get an IMAPInputStream back, which isn't ideal. I'd very much
> like to get the MimeMultipart object back. I've tried not adding any JavaMail
> libraries to Karaf, and relying on the one that Karaf itself provides (which
> is 1.4.5, according to the version matrix:
> http://karaf.apache.org/index/documentation/karaf-dependencies/karaf-deps-2.4.x.html
> I've also tried adding both javax.mail/javax.mail-api/1.5.4 and
> com.sun.mail/javax.mail/1.5.4 to Karaf, but the same problem occurs. I guess
> it still chooses the JAR's that Karaf provides.
> Even in the latest version of Karaf, 1.4.5 is used, so I'd guess the same
> problem exists there, but I cannot say for sure, I haven't tested.
> Am I missing something, or is there some workaround for this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6299) JDK11: don't expose javax.activation package from system bundle 0
[ https://issues.apache.org/jira/browse/KARAF-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6299. - Resolution: Fixed Fix Version/s: 4.2.6 4.3.0 > JDK11: don't expose javax.activation package from system bundle 0 > - > > Key: KARAF-6299 > URL: https://issues.apache.org/jira/browse/KARAF-6299 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.6 > > > should use it from the installed activation bundle, to align the behavior > with JDK8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6299) JDK11: don't expose javax.activation package from system bundle 0
[ https://issues.apache.org/jira/browse/KARAF-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6299: --- Assignee: Freeman Fang > JDK11: don't expose javax.activation package from system bundle 0 > - > > Key: KARAF-6299 > URL: https://issues.apache.org/jira/browse/KARAF-6299 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > should use it from the installed activation bundle, to align the behavior > with JDK8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6299) JDK11: don't expose javax.activation package from system bundle 0
Freeman Fang created KARAF-6299: --- Summary: JDK11: don't expose javax.activation package from system bundle 0 Key: KARAF-6299 URL: https://issues.apache.org/jira/browse/KARAF-6299 Project: Karaf Issue Type: Bug Reporter: Freeman Fang should use it from the installed activation bundle, to align the behavior with JDK8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6298) master can't build with JDK11 again
[ https://issues.apache.org/jira/browse/KARAF-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852274#comment-16852274 ] Freeman Fang commented on KARAF-6298: - Thanks [~jbonofre]! > master can't build with JDK11 again > --- > > Key: KARAF-6298 > URL: https://issues.apache.org/jira/browse/KARAF-6298 > Project: Karaf > Issue Type: Task >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > so far I ran into two issues with JDK11 > 1. > features/core/src/main/java/org/apache/karaf/features/internal/service/Deployer.java > has unused "org.omg.CORBA.DynAnyPackage.Invalid" > 2. new introduced SortedProperties class use TreeSet but can't guarantee all > elements in TreeSet implements Comparable interface -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6298) master can't build with JDK11 again
[ https://issues.apache.org/jira/browse/KARAF-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6298: --- Assignee: Freeman Fang > master can't build with JDK11 again > --- > > Key: KARAF-6298 > URL: https://issues.apache.org/jira/browse/KARAF-6298 > Project: Karaf > Issue Type: Task >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > so far I ran into two issues with JDK11 > 1. > features/core/src/main/java/org/apache/karaf/features/internal/service/Deployer.java > has unused "org.omg.CORBA.DynAnyPackage.Invalid" > 2. new introduced SortedProperties class use TreeSet but can't guarantee all > elements in TreeSet implements Comparable interface -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6298) master can't build with JDK11 again
Freeman Fang created KARAF-6298: --- Summary: master can't build with JDK11 again Key: KARAF-6298 URL: https://issues.apache.org/jira/browse/KARAF-6298 Project: Karaf Issue Type: Task Reporter: Freeman Fang so far I ran into two issues with JDK11 1. features/core/src/main/java/org/apache/karaf/features/internal/service/Deployer.java has unused "org.omg.CORBA.DynAnyPackage.Invalid" 2. new introduced SortedProperties class use TreeSet but can't guarantee all elements in TreeSet implements Comparable interface -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-4154) javax.mail.Message.getContent() returns IMAPInputStream
[
https://issues.apache.org/jira/browse/KARAF-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849856#comment-16849856
]
Freeman Fang commented on KARAF-4154:
-
Hi [~eximius],
Any chance you put a testcase here?
Thanks!
Freeman
> javax.mail.Message.getContent() returns IMAPInputStream
> ---
>
> Key: KARAF-4154
> URL: https://issues.apache.org/jira/browse/KARAF-4154
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: Linux Mint 17.2 Cinnamon
> Oracle JDK 1.7
>Reporter: Anton Johansson
>Assignee: Christian Schneider
>Priority: Critical
> Labels: javax.mail, mail
>
> I'm using JavaMail API to read emails from Gmail IMAP. The emails are of type
> multipart. I open up a Store, then I open up a Folder ("INBOX"), then I get
> the messages from that folder.
> Outside of Karaf, when doing message.getContent() I get a
> javax.mail.internet.MimeMultipart object back. Doesn't matter if I use
> version 1.4.5 (the one that Karaf provides) or 1.5.4 (the latest).
> Inside Karaf, I get an IMAPInputStream back, which isn't ideal. I'd very much
> like to get the MimeMultipart object back. I've tried not adding any JavaMail
> libraries to Karaf, and relying on the one that Karaf itself provides (which
> is 1.4.5, according to the version matrix:
> http://karaf.apache.org/index/documentation/karaf-dependencies/karaf-deps-2.4.x.html
> I've also tried adding both javax.mail/javax.mail-api/1.5.4 and
> com.sun.mail/javax.mail/1.5.4 to Karaf, but the same problem occurs. I guess
> it still chooses the JAR's that Karaf provides.
> Even in the latest version of Karaf, 1.4.5 is used, so I'd guess the same
> problem exists there, but I cannot say for sure, I haven't tested.
> Am I missing something, or is there some workaround for this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6241) introduce new property EnabledProtocals for org.apache.karaf.management.cfg
[ https://issues.apache.org/jira/browse/KARAF-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6241. - Resolution: Fixed > introduce new property EnabledProtocals for org.apache.karaf.management.cfg > --- > > Key: KARAF-6241 > URL: https://issues.apache.org/jira/browse/KARAF-6241 > Project: Karaf > Issue Type: Improvement > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.5 > > > so that we can explicitly specify which TLS/SSL version we support for the > JMX security connection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-6241) introduce new property EnabledProtocals for org.apache.karaf.management.cfg
[ https://issues.apache.org/jira/browse/KARAF-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6241 started by Freeman Fang. --- > introduce new property EnabledProtocals for org.apache.karaf.management.cfg > --- > > Key: KARAF-6241 > URL: https://issues.apache.org/jira/browse/KARAF-6241 > Project: Karaf > Issue Type: Improvement >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > so that we can explicitly specify which TLS/SSL version we support for the > JMX security connection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6241) introduce new property EnabledProtocals for org.apache.karaf.management.cfg
[ https://issues.apache.org/jira/browse/KARAF-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated KARAF-6241: Fix Version/s: 4.2.5 4.3.0 Component/s: karaf > introduce new property EnabledProtocals for org.apache.karaf.management.cfg > --- > > Key: KARAF-6241 > URL: https://issues.apache.org/jira/browse/KARAF-6241 > Project: Karaf > Issue Type: Improvement > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.5 > > > so that we can explicitly specify which TLS/SSL version we support for the > JMX security connection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6241) introduce new property EnabledProtocals for org.apache.karaf.management.cfg
[ https://issues.apache.org/jira/browse/KARAF-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6241: --- Assignee: Freeman Fang > introduce new property EnabledProtocals for org.apache.karaf.management.cfg > --- > > Key: KARAF-6241 > URL: https://issues.apache.org/jira/browse/KARAF-6241 > Project: Karaf > Issue Type: Improvement >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > so that we can explicitly specify which TLS/SSL version we support for the > JMX security connection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6241) introduce new property EnabledProtocals for org.apache.karaf.management.cfg
Freeman Fang created KARAF-6241: --- Summary: introduce new property EnabledProtocals for org.apache.karaf.management.cfg Key: KARAF-6241 URL: https://issues.apache.org/jira/browse/KARAF-6241 Project: Karaf Issue Type: Improvement Reporter: Freeman Fang so that we can explicitly specify which TLS/SSL version we support for the JMX security connection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6221) ensure karaf can build and run with JDK13 EA
[ https://issues.apache.org/jira/browse/KARAF-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated KARAF-6221: Component/s: karaf > ensure karaf can build and run with JDK13 EA > > > Key: KARAF-6221 > URL: https://issues.apache.org/jira/browse/KARAF-6221 > Project: Karaf > Issue Type: Task > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6221) ensure karaf can build and run with JDK13 EA
Freeman Fang created KARAF-6221: --- Summary: ensure karaf can build and run with JDK13 EA Key: KARAF-6221 URL: https://issues.apache.org/jira/browse/KARAF-6221 Project: Karaf Issue Type: Task Reporter: Freeman Fang -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6221) ensure karaf can build and run with JDK13 EA
[ https://issues.apache.org/jira/browse/KARAF-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6221: --- Assignee: Freeman Fang > ensure karaf can build and run with JDK13 EA > > > Key: KARAF-6221 > URL: https://issues.apache.org/jira/browse/KARAF-6221 > Project: Karaf > Issue Type: Task >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6203) ensure karaf can build and run with JDK12
[ https://issues.apache.org/jira/browse/KARAF-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802476#comment-16802476 ] Freeman Fang commented on KARAF-6203: - JpaExampleTest is related to https://github.com/jboss-javassist/javassist/pull/198 > ensure karaf can build and run with JDK12 > - > > Key: KARAF-6203 > URL: https://issues.apache.org/jira/browse/KARAF-6203 > Project: Karaf > Issue Type: Task > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6203) ensure karaf can build and run with JDK12
[ https://issues.apache.org/jira/browse/KARAF-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801400#comment-16801400 ] Freeman Fang commented on KARAF-6203: - fixed Krb5LoginModuleTest.testKeytabSuccess and Krb5LoginModuleTest.testLoginSuccess This is caused by the krb5 code change since jdk12. It requires java.security.krb5.conf system property available earlier than before > ensure karaf can build and run with JDK12 > - > > Key: KARAF-6203 > URL: https://issues.apache.org/jira/browse/KARAF-6203 > Project: Karaf > Issue Type: Task > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6203) ensure karaf can build and run with JDK12
[ https://issues.apache.org/jira/browse/KARAF-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797794#comment-16797794 ] Freeman Fang commented on KARAF-6203: - JpaExampleTest and XATest is fixed > ensure karaf can build and run with JDK12 > - > > Key: KARAF-6203 > URL: https://issues.apache.org/jira/browse/KARAF-6203 > Project: Karaf > Issue Type: Task > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6203) ensure karaf can build and run with JDK12
[
https://issues.apache.org/jira/browse/KARAF-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797784#comment-16797784
]
Freeman Fang commented on KARAF-6203:
-
I pushed my initial change to jdk12 branch.
We need ARIES-1905 get fixed first(PR available).
And so far we have failures in itests as follows
{code}
Krb5LoginModuleTest.testKeytabSuccess and Krb5LoginModuleTest.testLoginSuccess
{code}
and
{code}
[ERROR] Errors:
[ERROR] InstanceTest.createStartStopDestroyCommand » IllegalArgument Instance
'itest66...
[ERROR] XATest.org.apache.karaf.itests.XATest » Runtime Cannot get the remote
bundle c...
[ERROR] JmsExampleTest.org.apache.karaf.itests.examples.JmsExampleTest »
Runtime Canno...
[ERROR] JpaExampleTest.test » CommandNotFound Command not found: booking:add
[ERROR] RestExampleTest.testWhiteboard » WrappedTestContainer
[org.apache.karaf.itests...
[ERROR] MavenResolverRegisteredBeforeConfigAdminTest.mavenResolverAvailable »
NotBound
[ERROR]
JUnit4Provider.invoke:159->executeTestSet:238->executeWithRerun:273->execute:365
» Runtime
[ERROR]
JUnit4Provider.invoke:159->executeTestSet:238->executeWithRerun:273->execute:365
» Runtime
{code}
still on it...
Freeman
> ensure karaf can build and run with JDK12
> -
>
> Key: KARAF-6203
> URL: https://issues.apache.org/jira/browse/KARAF-6203
> Project: Karaf
> Issue Type: Task
> Components: karaf
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6203) ensure karaf can build and run with JDK12
[ https://issues.apache.org/jira/browse/KARAF-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16796974#comment-16796974 ] Freeman Fang commented on KARAF-6203: - Thanks [~jbonofre]! There is some work on code to be done, I'm on it Freeman > ensure karaf can build and run with JDK12 > - > > Key: KARAF-6203 > URL: https://issues.apache.org/jira/browse/KARAF-6203 > Project: Karaf > Issue Type: Task > Components: karaf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (KARAF-6203) ensure karaf can build and run with JDK12
[ https://issues.apache.org/jira/browse/KARAF-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6203 started by Freeman Fang. --- > ensure karaf can build and run with JDK12 > - > > Key: KARAF-6203 > URL: https://issues.apache.org/jira/browse/KARAF-6203 > Project: Karaf > Issue Type: Task >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6203) ensure karaf can build and run with JDK12
Freeman Fang created KARAF-6203: --- Summary: ensure karaf can build and run with JDK12 Key: KARAF-6203 URL: https://issues.apache.org/jira/browse/KARAF-6203 Project: Karaf Issue Type: Task Reporter: Freeman Fang -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6203) ensure karaf can build and run with JDK12
[ https://issues.apache.org/jira/browse/KARAF-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6203: --- Assignee: Freeman Fang > ensure karaf can build and run with JDK12 > - > > Key: KARAF-6203 > URL: https://issues.apache.org/jira/browse/KARAF-6203 > Project: Karaf > Issue Type: Task >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6119) karaf-maven-plugin assembly goal doesn't handle locked snapshots
[
https://issues.apache.org/jira/browse/KARAF-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved KARAF-6119.
-
Resolution: Fixed
Fix Version/s: 4.2.4
4.3.0
> karaf-maven-plugin assembly goal doesn't handle locked snapshots
>
>
> Key: KARAF-6119
> URL: https://issues.apache.org/jira/browse/KARAF-6119
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Mike Mansell
>Assignee: Freeman Fang
>Priority: Major
> Labels: maven
> Fix For: 4.3.0, 4.2.4
>
>
> When using the assembly goal with the karaf-maven-plugin, and a feature has a
> bundle that has an explicit snapshot version
> (mvn:GROUPID/ARTIFACTID/0.2.0-20190111.021945-8), and that
> bundle is injected into the system maven directory layout, it incorrectly
> names the VERSION directory component.
> Currently, it creates a path like
> {{GROUPID/ARTIFACTID/0.2.0-20190111.021945-8/ARTIFACTID-0.2.0-20190111.021945-8.jar}}
> but that will not resolve when using a Maven resolver (such as the Aether
> that is used in the Karaf runtime). Instead the path needs to be
> {{GROUPID/ARTIFACTID/0.2.0-SNAPSHOT/ARTIFACTID-0.2.0-20190111.021945-8.jar}}
> It seems that the fix is to add a "base version" capability to the
> org.apache.karaf.util.maven.Parser class similar to how the
> org.apache.maven.artifact.DefaultArtifact handles it.
> I've done that in my local copy and seems fine, and I'm happy to provide a
> PR, however, I don't understand why the Parser class has a
> getArtifactPath(String) variant. Shouldn't it just use the m_version instance?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6085) karaf-maven-plugin verify mojo builds invalid repository URL on Windows
[
https://issues.apache.org/jira/browse/KARAF-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved KARAF-6085.
-
Resolution: Fixed
Fix Version/s: 4.2.4
4.3.0
> karaf-maven-plugin verify mojo builds invalid repository URL on Windows
> ---
>
> Key: KARAF-6085
> URL: https://issues.apache.org/jira/browse/KARAF-6085
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: Windows
>Reporter: Dan Berindei
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 4.3.0, 4.2.4
>
>
> [https://github.com/apache/karaf/blob/218c765d0ec389f44d27d9e837e965028aa30f15/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/VerifyMojo.java#L253]
> {code:java}
> allDescriptors.add("file:" + project.getBuild().getDirectory() +
> "/feature/feature.xml");
> {code}
> On Windows, this builds a URL like
> {{[file://C:\jenkins\workspace\InfinispanAlternateBuilds\InfinispanWindows\commons\target/classes/features.xml|file:///classes/features.xml]}},
> which is invalid because {{C:}} is interpreted as a host name:
> [https://en.wikipedia.org/wiki/File_URI_scheme#Windows_2]
> The error is reported like this:
> {noformat}
> 16:24:58 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.2.0:verify
> (validate) on project infinispan-commons: Unable to load features descriptors
> 16:24:58 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> 16:24:58 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> 16:24:58 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> 16:24:58 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> 16:24:58 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> 16:24:58 at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> 16:24:58 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> 16:24:58 at org.apache.maven.DefaultMaven.doExecute
> (DefaultMaven.java:305)
> 16:24:58 at org.apache.maven.DefaultMaven.doExecute
> (DefaultMaven.java:192)
> 16:24:58 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> 16:24:58 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> 16:24:58 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> 16:24:58 at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> 16:24:58 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 16:24:58 at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> 16:24:58 at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> 16:24:59 at java.lang.reflect.Method.invoke (Method.java:498)
> 16:24:59 at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> 16:24:59 at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> 16:24:59 at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> 16:24:59 at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> 16:24:59 Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to
> load features descriptors
> 16:24:59 at org.apache.karaf.tooling.VerifyMojo.doExecute
> (VerifyMojo.java:293)
> 16:24:59 at org.apache.karaf.tooling.VerifyMojo.execute
> (VerifyMojo.java:185)
> 16:24:59 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> 16:24:59 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> 16:24:59 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> 16:24:59 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> 16:24:59 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> 16:24:59 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> 16:24:59 at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> 16:24:59 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> 16:24:59 at
[jira] [Assigned] (KARAF-6119) karaf-maven-plugin assembly goal doesn't handle locked snapshots
[
https://issues.apache.org/jira/browse/KARAF-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned KARAF-6119:
---
Assignee: Freeman Fang
> karaf-maven-plugin assembly goal doesn't handle locked snapshots
>
>
> Key: KARAF-6119
> URL: https://issues.apache.org/jira/browse/KARAF-6119
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Mike Mansell
>Assignee: Freeman Fang
>Priority: Major
> Labels: maven
>
> When using the assembly goal with the karaf-maven-plugin, and a feature has a
> bundle that has an explicit snapshot version
> (mvn:GROUPID/ARTIFACTID/0.2.0-20190111.021945-8), and that
> bundle is injected into the system maven directory layout, it incorrectly
> names the VERSION directory component.
> Currently, it creates a path like
> {{GROUPID/ARTIFACTID/0.2.0-20190111.021945-8/ARTIFACTID-0.2.0-20190111.021945-8.jar}}
> but that will not resolve when using a Maven resolver (such as the Aether
> that is used in the Karaf runtime). Instead the path needs to be
> {{GROUPID/ARTIFACTID/0.2.0-SNAPSHOT/ARTIFACTID-0.2.0-20190111.021945-8.jar}}
> It seems that the fix is to add a "base version" capability to the
> org.apache.karaf.util.maven.Parser class similar to how the
> org.apache.maven.artifact.DefaultArtifact handles it.
> I've done that in my local copy and seems fine, and I'm happy to provide a
> PR, however, I don't understand why the Parser class has a
> getArtifactPath(String) variant. Shouldn't it just use the m_version instance?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KARAF-6085) karaf-maven-plugin verify mojo builds invalid repository URL on Windows
[
https://issues.apache.org/jira/browse/KARAF-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned KARAF-6085:
---
Assignee: Freeman Fang
> karaf-maven-plugin verify mojo builds invalid repository URL on Windows
> ---
>
> Key: KARAF-6085
> URL: https://issues.apache.org/jira/browse/KARAF-6085
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: Windows
>Reporter: Dan Berindei
>Assignee: Freeman Fang
>Priority: Minor
>
> [https://github.com/apache/karaf/blob/218c765d0ec389f44d27d9e837e965028aa30f15/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/VerifyMojo.java#L253]
> {code:java}
> allDescriptors.add("file:" + project.getBuild().getDirectory() +
> "/feature/feature.xml");
> {code}
> On Windows, this builds a URL like
> {{[file://C:\jenkins\workspace\InfinispanAlternateBuilds\InfinispanWindows\commons\target/classes/features.xml|file:///classes/features.xml]}},
> which is invalid because {{C:}} is interpreted as a host name:
> [https://en.wikipedia.org/wiki/File_URI_scheme#Windows_2]
> The error is reported like this:
> {noformat}
> 16:24:58 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.2.0:verify
> (validate) on project infinispan-commons: Unable to load features descriptors
> 16:24:58 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> 16:24:58 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> 16:24:58 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> 16:24:58 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> 16:24:58 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> 16:24:58 at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> 16:24:58 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> 16:24:58 at org.apache.maven.DefaultMaven.doExecute
> (DefaultMaven.java:305)
> 16:24:58 at org.apache.maven.DefaultMaven.doExecute
> (DefaultMaven.java:192)
> 16:24:58 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> 16:24:58 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> 16:24:58 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> 16:24:58 at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> 16:24:58 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 16:24:58 at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> 16:24:58 at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> 16:24:59 at java.lang.reflect.Method.invoke (Method.java:498)
> 16:24:59 at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> 16:24:59 at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> 16:24:59 at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> 16:24:59 at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> 16:24:59 Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to
> load features descriptors
> 16:24:59 at org.apache.karaf.tooling.VerifyMojo.doExecute
> (VerifyMojo.java:293)
> 16:24:59 at org.apache.karaf.tooling.VerifyMojo.execute
> (VerifyMojo.java:185)
> 16:24:59 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> 16:24:59 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> 16:24:59 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> 16:24:59 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> 16:24:59 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> 16:24:59 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> 16:24:59 at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> 16:24:59 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> 16:24:59 at org.apache.maven.DefaultMaven.doExecute
> (DefaultMaven.java:305)
> 16:24:59 at
[jira] [Commented] (KARAF-6178) Feature and file deployer does not work under Java 11
[
https://issues.apache.org/jira/browse/KARAF-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782577#comment-16782577
]
Freeman Fang commented on KARAF-6178:
-
[~pdolezal] thanks for the confirmation!
> Feature and file deployer does not work under Java 11
> -
>
> Key: KARAF-6178
> URL: https://issues.apache.org/jira/browse/KARAF-6178
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: java version "11.0.1" 2018-10-16 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
>Reporter: Petr Dolezal
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 4.2.3
>
>
> When running Karaf with Java 11 (as noted in the environment), {{feature}}
> command is not available at all and dropping a bundle in the usual
> {{deploy/}} directory has no effect. Installing the bundle manually with
> {{bundle:install}} works. There is no failure written in the log.
> When trying the same thing with Java 8, no problem occurs.
> Another interesting, and maybe related, observation: when some dependent
> bundles are installed manually (running under Java 11) and started,
> uninstalling a dependency does not make the dependent bundles stop and
> unresolve.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6178) Feature and file deployer does not work under Java 11
[
https://issues.apache.org/jira/browse/KARAF-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved KARAF-6178.
-
Resolution: Fixed
Fix Version/s: 4.2.3
> Feature and file deployer does not work under Java 11
> -
>
> Key: KARAF-6178
> URL: https://issues.apache.org/jira/browse/KARAF-6178
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: java version "11.0.1" 2018-10-16 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
>Reporter: Petr Dolezal
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 4.2.3
>
>
> When running Karaf with Java 11 (as noted in the environment), {{feature}}
> command is not available at all and dropping a bundle in the usual
> {{deploy/}} directory has no effect. Installing the bundle manually with
> {{bundle:install}} works. There is no failure written in the log.
> When trying the same thing with Java 8, no problem occurs.
> Another interesting, and maybe related, observation: when some dependent
> bundles are installed manually (running under Java 11) and started,
> uninstalling a dependency does not make the dependent bundles stop and
> unresolve.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KARAF-6178) Feature and file deployer does not work under Java 11
[
https://issues.apache.org/jira/browse/KARAF-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781264#comment-16781264
]
Freeman Fang edited comment on KARAF-6178 at 3/1/19 4:14 AM:
-
Hi [~pdolezal],
Could you please try with KARAF 4.2.3, which has better JDK11 support.
FYI, I can't even reproduce it on Karaf 4.2.2, the feature commands are
available for me.
Btw, my java version is
openjdk version "11" 2018-09-25
OpenJDK Runtime Environment 18.9 (build 11+28)
OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)
Freeman
was (Author: ffang):
Hi [~pdolezal],
Could you please try with KARAF 4.2.3, which has better JDK11 support.
FYI, I can't even reproduce it on Karaf 4.2.2, the feature commands are
available for me.
Freeman
> Feature and file deployer does not work under Java 11
> -
>
> Key: KARAF-6178
> URL: https://issues.apache.org/jira/browse/KARAF-6178
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: java version "11.0.1" 2018-10-16 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
>Reporter: Petr Dolezal
>Assignee: Freeman Fang
>Priority: Minor
>
> When running Karaf with Java 11 (as noted in the environment), {{feature}}
> command is not available at all and dropping a bundle in the usual
> {{deploy/}} directory has no effect. Installing the bundle manually with
> {{bundle:install}} works. There is no failure written in the log.
> When trying the same thing with Java 8, no problem occurs.
> Another interesting, and maybe related, observation: when some dependent
> bundles are installed manually (running under Java 11) and started,
> uninstalling a dependency does not make the dependent bundles stop and
> unresolve.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6178) Feature and file deployer does not work under Java 11
[
https://issues.apache.org/jira/browse/KARAF-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781264#comment-16781264
]
Freeman Fang commented on KARAF-6178:
-
Hi [~pdolezal],
Could you please try with KARAF 4.2.3, which has better JDK11 support.
FYI, I can't even reproduce it on Karaf 4.2.2, the feature commands are
available for me.
Freeman
> Feature and file deployer does not work under Java 11
> -
>
> Key: KARAF-6178
> URL: https://issues.apache.org/jira/browse/KARAF-6178
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: java version "11.0.1" 2018-10-16 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
>Reporter: Petr Dolezal
>Assignee: Freeman Fang
>Priority: Minor
>
> When running Karaf with Java 11 (as noted in the environment), {{feature}}
> command is not available at all and dropping a bundle in the usual
> {{deploy/}} directory has no effect. Installing the bundle manually with
> {{bundle:install}} works. There is no failure written in the log.
> When trying the same thing with Java 8, no problem occurs.
> Another interesting, and maybe related, observation: when some dependent
> bundles are installed manually (running under Java 11) and started,
> uninstalling a dependency does not make the dependent bundles stop and
> unresolve.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KARAF-6178) Feature and file deployer does not work under Java 11
[
https://issues.apache.org/jira/browse/KARAF-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned KARAF-6178:
---
Assignee: Freeman Fang
> Feature and file deployer does not work under Java 11
> -
>
> Key: KARAF-6178
> URL: https://issues.apache.org/jira/browse/KARAF-6178
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: java version "11.0.1" 2018-10-16 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
>Reporter: Petr Dolezal
>Assignee: Freeman Fang
>Priority: Minor
>
> When running Karaf with Java 11 (as noted in the environment), {{feature}}
> command is not available at all and dropping a bundle in the usual
> {{deploy/}} directory has no effect. Installing the bundle manually with
> {{bundle:install}} works. There is no failure written in the log.
> When trying the same thing with Java 8, no problem occurs.
> Another interesting, and maybe related, observation: when some dependent
> bundles are installed manually (running under Java 11) and started,
> uninstalling a dependency does not make the dependent bundles stop and
> unresolve.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6177) improve shell:exit help message
[ https://issues.apache.org/jira/browse/KARAF-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6177. - Resolution: Fixed Fix Version/s: 4.2.4 4.3.0 > improve shell:exit help message > --- > > Key: KARAF-6177 > URL: https://issues.apache.org/jira/browse/KARAF-6177 > Project: Karaf > Issue Type: Improvement >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.4 > > > to emphasize it's used to exit subshell, currently users are easy to misuse > this one with shell:logout command which is used to close a shell session -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6177) improve shell:exit help message
Freeman Fang created KARAF-6177: --- Summary: improve shell:exit help message Key: KARAF-6177 URL: https://issues.apache.org/jira/browse/KARAF-6177 Project: Karaf Issue Type: Improvement Reporter: Freeman Fang to emphasize it's used to exit subshell, currently users are easy to misuse this one with shell:logout command which is used to close a shell session -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6177) improve shell:exit help message
[ https://issues.apache.org/jira/browse/KARAF-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6177: --- Assignee: Freeman Fang > improve shell:exit help message > --- > > Key: KARAF-6177 > URL: https://issues.apache.org/jira/browse/KARAF-6177 > Project: Karaf > Issue Type: Improvement >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > to emphasize it's used to exit subshell, currently users are easy to misuse > this one with shell:logout command which is used to close a shell session -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6157) ensure karaf-maven-plugin can honor start-level for bootBundles
[ https://issues.apache.org/jira/browse/KARAF-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-6157. - Resolution: Fixed Fix Version/s: 4.2.4 4.3.0 > ensure karaf-maven-plugin can honor start-level for bootBundles > --- > > Key: KARAF-6157 > URL: https://issues.apache.org/jira/browse/KARAF-6157 > Project: Karaf > Issue Type: Improvement >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 4.3.0, 4.2.4 > > > the bundle element in generated features.xml should have start-level > configured accordingly -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6157) ensure karaf-maven-plugin can honor start-level for bootBundles
[ https://issues.apache.org/jira/browse/KARAF-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6157: --- Assignee: Freeman Fang > ensure karaf-maven-plugin can honor start-level for bootBundles > --- > > Key: KARAF-6157 > URL: https://issues.apache.org/jira/browse/KARAF-6157 > Project: Karaf > Issue Type: Improvement >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > the bundle element in generated features.xml should have start-level > configured accordingly -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6157) ensure karaf-maven-plugin can honor start-level for bootBundles
Freeman Fang created KARAF-6157: --- Summary: ensure karaf-maven-plugin can honor start-level for bootBundles Key: KARAF-6157 URL: https://issues.apache.org/jira/browse/KARAF-6157 Project: Karaf Issue Type: Improvement Reporter: Freeman Fang the bundle element in generated features.xml should have start-level configured accordingly -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6106) LinkageError due to javax.activation not in kernel anymore
[ https://issues.apache.org/jira/browse/KARAF-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748356#comment-16748356 ] Freeman Fang commented on KARAF-6106: - I believe the fix for KARAF-6093 would also fix this issue > LinkageError due to javax.activation not in kernel anymore > -- > > Key: KARAF-6106 > URL: https://issues.apache.org/jira/browse/KARAF-6106 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.2 >Reporter: Jens Kordowski >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 4.2.3 > > > With the update of Karaf from 4.2.1 to 4.2.2 I found the following error: > Caused by: java.lang.LinkageError: loader constraint violation: when > resolving method > "javax.xml.soap.SOAPMessage.createAttachmentPart(Ljavax/activation/DataHandler;)Ljavax/xml/soap/AttachmentPart;" > the class loader "" (instance of > [org.apache.felix.framework.BundleWiringImpl$BundleClassLoader@2febf41d|mailto:org.apache.felix.framework.BundleWiringImpl$BundleClassLoader@2febf41d], > child of > [java.net.URLClassLoader@3fee9989|mailto:java.net.URLClassLoader@3fee9989]) > of the current class, com/sap/it/cxf/xi/XIUtils, and the class loader > for the method's defining class, javax/xml/soap/SOAPMessage, have > different Class objects for the type javax/activation/DataHandler used in the > signature > > I think this came in with this change: > https://issues.apache.org/jira/browse/KARAF-5989 > > Since the servicemix javax.activation bundle is not part of the framework > bundle anymore, it has to load it from the jdk and it will not import it from > the servicemix bundle (see change above). > Other bundles correctly importing javax.activation will get it from the > servicemix bundle. > This can lead to the linkage error outlined above. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6091) upgrade jaxb 2.3.2
[ https://issues.apache.org/jira/browse/KARAF-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6091: --- Assignee: Freeman Fang > upgrade jaxb 2.3.2 > -- > > Key: KARAF-6091 > URL: https://issues.apache.org/jira/browse/KARAF-6091 > Project: Karaf > Issue Type: Task >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > also use org.glassfish.jaxb artifacts instead of the old ones from > com.sun.xml.bind -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6091) upgrade jaxb 2.3.2
Freeman Fang created KARAF-6091: --- Summary: upgrade jaxb 2.3.2 Key: KARAF-6091 URL: https://issues.apache.org/jira/browse/KARAF-6091 Project: Karaf Issue Type: Task Reporter: Freeman Fang also use org.glassfish.jaxb artifacts instead of the old ones from com.sun.xml.bind -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6084) Startup bundles do not resolve correctly when compiled with Java 11 during assembly
[
https://issues.apache.org/jira/browse/KARAF-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved KARAF-6084.
-
Resolution: Fixed
> Startup bundles do not resolve correctly when compiled with Java 11 during
> assembly
> ---
>
> Key: KARAF-6084
> URL: https://issues.apache.org/jira/browse/KARAF-6084
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Martin Krüger
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 4.2.3
>
> Attachments:
> 0001-KARAF-6084-Add-Java-11-and-11-to-the-list-of-support.patch
>
>
> The problem is that we have a fragment for the logger which needs to be
> loaded in the startup phase. We compile the bundles with Java 11 which
> results in a {noformat}Require-Capability:
> osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=11))"{noformat} manifest entry.
> We during build we get an error that a bundle requirement is not met.
> We then discovered that the karaf-maven-plugin uses "1.8" as default value
> for the javase option. Changing that to "11" results in a compile error
> because this version is not supported.
> Therefore I suggest to add Java 10 and Java 11 to enum
> org.apache.karaf.profile.assembly.Builder.JavaVersion. That enables support
> for this Java version also.
> In my local tests this solved the compile issue when setting the javase
> option to 11.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6084) Startup bundles do not resolve correctly when compiled with Java 11 during assembly
[
https://issues.apache.org/jira/browse/KARAF-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739236#comment-16739236
]
Freeman Fang commented on KARAF-6084:
-
Yup, we should do it.
Thanks for the contribution
Patch applied on behalf of Martin Krüger with thanks!
> Startup bundles do not resolve correctly when compiled with Java 11 during
> assembly
> ---
>
> Key: KARAF-6084
> URL: https://issues.apache.org/jira/browse/KARAF-6084
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Martin Krüger
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 4.2.3
>
> Attachments:
> 0001-KARAF-6084-Add-Java-11-and-11-to-the-list-of-support.patch
>
>
> The problem is that we have a fragment for the logger which needs to be
> loaded in the startup phase. We compile the bundles with Java 11 which
> results in a {noformat}Require-Capability:
> osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=11))"{noformat} manifest entry.
> We during build we get an error that a bundle requirement is not met.
> We then discovered that the karaf-maven-plugin uses "1.8" as default value
> for the javase option. Changing that to "11" results in a compile error
> because this version is not supported.
> Therefore I suggest to add Java 10 and Java 11 to enum
> org.apache.karaf.profile.assembly.Builder.JavaVersion. That enables support
> for this Java version also.
> In my local tests this solved the compile issue when setting the javase
> option to 11.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work started] (KARAF-6084) Startup bundles do not resolve correctly when compiled with Java 11 during assembly
[
https://issues.apache.org/jira/browse/KARAF-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KARAF-6084 started by Freeman Fang.
---
> Startup bundles do not resolve correctly when compiled with Java 11 during
> assembly
> ---
>
> Key: KARAF-6084
> URL: https://issues.apache.org/jira/browse/KARAF-6084
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Martin Krüger
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 4.2.3
>
> Attachments:
> 0001-KARAF-6084-Add-Java-11-and-11-to-the-list-of-support.patch
>
>
> The problem is that we have a fragment for the logger which needs to be
> loaded in the startup phase. We compile the bundles with Java 11 which
> results in a {noformat}Require-Capability:
> osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=11))"{noformat} manifest entry.
> We during build we get an error that a bundle requirement is not met.
> We then discovered that the karaf-maven-plugin uses "1.8" as default value
> for the javase option. Changing that to "11" results in a compile error
> because this version is not supported.
> Therefore I suggest to add Java 10 and Java 11 to enum
> org.apache.karaf.profile.assembly.Builder.JavaVersion. That enables support
> for this Java version also.
> In my local tests this solved the compile issue when setting the javase
> option to 11.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KARAF-6084) Startup bundles do not resolve correctly when compiled with Java 11 during assembly
[
https://issues.apache.org/jira/browse/KARAF-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned KARAF-6084:
---
Assignee: Freeman Fang
> Startup bundles do not resolve correctly when compiled with Java 11 during
> assembly
> ---
>
> Key: KARAF-6084
> URL: https://issues.apache.org/jira/browse/KARAF-6084
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Martin Krüger
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 4.2.3
>
> Attachments:
> 0001-KARAF-6084-Add-Java-11-and-11-to-the-list-of-support.patch
>
>
> The problem is that we have a fragment for the logger which needs to be
> loaded in the startup phase. We compile the bundles with Java 11 which
> results in a {noformat}Require-Capability:
> osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=11))"{noformat} manifest entry.
> We during build we get an error that a bundle requirement is not met.
> We then discovered that the karaf-maven-plugin uses "1.8" as default value
> for the javase option. Changing that to "11" results in a compile error
> because this version is not supported.
> Therefore I suggest to add Java 10 and Java 11 to enum
> org.apache.karaf.profile.assembly.Builder.JavaVersion. That enables support
> for this Java version also.
> In my local tests this solved the compile issue when setting the javase
> option to 11.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KARAF-6083) karaf-maven-plugin:features-generate-descriptor fails with ClassCastException
[
https://issues.apache.org/jira/browse/KARAF-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738895#comment-16738895
]
Freeman Fang edited comment on KARAF-6083 at 1/10/19 2:01 AM:
--
could you please run "mvn dependency:tree" to see if you have multiple
maven-resolver-impl jars, this may reveal more
was (Author: ffang):
could you please run "mvn dependency:tree", this may reveal more
> karaf-maven-plugin:features-generate-descriptor fails with ClassCastException
> -
>
> Key: KARAF-6083
> URL: https://issues.apache.org/jira/browse/KARAF-6083
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: Debian testing (up to date)
>Reporter: Robin Vobruba
>Priority: Major
>
> I am running "mvn karaf:features-generate-descriptor", and I get this error:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.2.2:features-generate-descriptor
> (default-cli) on project myProj: Unable to create features.xml file:
> java.lang.ClassCastException:
> org.eclipse.aether.internal.impl.collect.ObjectPool cannot be cast to
> org.eclipse.aether.internal.impl.collect.ObjectPool -> [Help 1]{code}
> Am ready to supply more info if required.
> It looks llike it has two different versions of the class
> `org.eclipse.aether.internal.impl.collect.ObjectPool`.. not sure how that
> happens.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6083) karaf-maven-plugin:features-generate-descriptor fails with ClassCastException
[
https://issues.apache.org/jira/browse/KARAF-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738895#comment-16738895
]
Freeman Fang commented on KARAF-6083:
-
could you please run "mvn dependency:tree", this may reveal more
> karaf-maven-plugin:features-generate-descriptor fails with ClassCastException
> -
>
> Key: KARAF-6083
> URL: https://issues.apache.org/jira/browse/KARAF-6083
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: Debian testing (up to date)
>Reporter: Robin Vobruba
>Priority: Major
>
> I am running "mvn karaf:features-generate-descriptor", and I get this error:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.2.2:features-generate-descriptor
> (default-cli) on project myProj: Unable to create features.xml file:
> java.lang.ClassCastException:
> org.eclipse.aether.internal.impl.collect.ObjectPool cannot be cast to
> org.eclipse.aether.internal.impl.collect.ObjectPool -> [Help 1]{code}
> Am ready to supply more info if required.
> It looks llike it has two different versions of the class
> `org.eclipse.aether.internal.impl.collect.ObjectPool`.. not sure how that
> happens.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
