[jira] [Resolved] (KARAF-6005) Resolve of bundle with version range in a feature only works with ".m2" and not with "system" directory
[
https://issues.apache.org/jira/browse/KARAF-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved KARAF-6005.
-
Resolution: Fixed
> Resolve of bundle with version range in a feature only works with ".m2" and
> not with "system" directory
> ---
>
> Key: KARAF-6005
> URL: https://issues.apache.org/jira/browse/KARAF-6005
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Volker Althaus
>Assignee: Grzegorz Grzybek
>Priority: Critical
> Fix For: 4.2.3
>
>
> I defined a feature with a ranged bundle version:
> {code:xml}
>
> mvn:de.some.api/api/[1,2)
>
> {code}
> If a bundle within that range lies within the global/user Maven repo ".m2",
> the bundle gets resolved.
> If it resides only within the "system" folder of Karaf I get an exception:
> {noformat}
> karaf@root()> org.apache.karaf.features.internal.util.MultiException: Error:
> Error downloading mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:91)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:457)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:452)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:224)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: java.io.IOException: Error downloading
> mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:77)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> ... 3 more
> Caused by: java.io.IOException: Error resolving artifact
> de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:729)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:659)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:600)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:567)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:47)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60)
> ... 7 more
> Caused by:
> shaded.org.eclipse.aether.resolution.VersionRangeResolutionException: No
> highest version found for de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveLatestVersionRange(AetherBasedResolver.java:998)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:703)
> ... 12 more
> {noformat}
> Setting the property org.ops4j.pax.url.mvn.defaultLocalRepoAsRemote = true as
> mentioned in the mailing list does not help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6079) Upgrade to pax-url 2.6.1
[ https://issues.apache.org/jira/browse/KARAF-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved KARAF-6079. - Resolution: Fixed > Upgrade to pax-url 2.6.1 > > > Key: KARAF-6079 > URL: https://issues.apache.org/jira/browse/KARAF-6079 > Project: Karaf > Issue Type: Dependency upgrade >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.2.3 > > > pax-url 2.6.1 uses maver-resolver instead of eclipse-aether, but is > compatible. There are also several pax-url-aether fixes and a fix for > KARAF-6005 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6081) Add -Pconsistency to the Jenkins master job
[ https://issues.apache.org/jira/browse/KARAF-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6081: Labels: jenkins (was: ) > Add -Pconsistency to the Jenkins master job > --- > > Key: KARAF-6081 > URL: https://issues.apache.org/jira/browse/KARAF-6081 > Project: Karaf > Issue Type: Task > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: jenkins > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6081) Add -Pconsistency to the Jenkins master job
Jean-Baptiste Onofré created KARAF-6081: --- Summary: Add -Pconsistency to the Jenkins master job Key: KARAF-6081 URL: https://issues.apache.org/jira/browse/KARAF-6081 Project: Karaf Issue Type: Task Components: karaf Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6079) Upgrade to pax-url 2.6.1
Grzegorz Grzybek created KARAF-6079: --- Summary: Upgrade to pax-url 2.6.1 Key: KARAF-6079 URL: https://issues.apache.org/jira/browse/KARAF-6079 Project: Karaf Issue Type: Dependency upgrade Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek pax-url 2.6.1 uses maver-resolver instead of eclipse-aether, but is compatible. There are also several pax-url-aether fixes and a fix for KARAF-6005 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6079) Upgrade to pax-url 2.6.1
[ https://issues.apache.org/jira/browse/KARAF-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated KARAF-6079: Fix Version/s: 4.2.3 > Upgrade to pax-url 2.6.1 > > > Key: KARAF-6079 > URL: https://issues.apache.org/jira/browse/KARAF-6079 > Project: Karaf > Issue Type: Dependency upgrade >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.2.3 > > > pax-url 2.6.1 uses maver-resolver instead of eclipse-aether, but is > compatible. There are also several pax-url-aether fixes and a fix for > KARAF-6005 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6079) Upgrade to pax-url 2.6.1
[ https://issues.apache.org/jira/browse/KARAF-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737112#comment-16737112 ] Grzegorz Grzybek commented on KARAF-6079: - However pax-web should be updated too to use matching pax-url version. > Upgrade to pax-url 2.6.1 > > > Key: KARAF-6079 > URL: https://issues.apache.org/jira/browse/KARAF-6079 > Project: Karaf > Issue Type: Dependency upgrade >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > > pax-url 2.6.1 uses maver-resolver instead of eclipse-aether, but is > compatible. There are also several pax-url-aether fixes and a fix for > KARAF-6005 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6005) Resolve of bundle with version range in a feature only works with ".m2" and not with "system" directory
[
https://issues.apache.org/jira/browse/KARAF-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737181#comment-16737181
]
ASF subversion and git services commented on KARAF-6005:
Commit 48dc8e65ef173757e6e23af5459d739f30242f45 in karaf's branch
refs/heads/master from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=48dc8e6 ]
[KARAF-6005][KARAF-6079] Upgrade to pax-url 2.6.1
> Resolve of bundle with version range in a feature only works with ".m2" and
> not with "system" directory
> ---
>
> Key: KARAF-6005
> URL: https://issues.apache.org/jira/browse/KARAF-6005
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Volker Althaus
>Assignee: Grzegorz Grzybek
>Priority: Critical
> Fix For: 4.2.3
>
>
> I defined a feature with a ranged bundle version:
> {code:xml}
>
> mvn:de.some.api/api/[1,2)
>
> {code}
> If a bundle within that range lies within the global/user Maven repo ".m2",
> the bundle gets resolved.
> If it resides only within the "system" folder of Karaf I get an exception:
> {noformat}
> karaf@root()> org.apache.karaf.features.internal.util.MultiException: Error:
> Error downloading mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:91)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:457)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:452)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:224)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: java.io.IOException: Error downloading
> mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:77)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> ... 3 more
> Caused by: java.io.IOException: Error resolving artifact
> de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:729)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:659)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:600)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:567)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:47)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60)
> ... 7 more
> Caused by:
> shaded.org.eclipse.aether.resolution.VersionRangeResolutionException: No
> highest version found for de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveLatestVersionRange(AetherBasedResolver.java:998)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:703)
> ... 12 more
> {noformat}
> Setting the property org.ops4j.pax.url.mvn.defaultLocalRepoAsRemote = true as
> mentioned in the mailing list does not help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6079) Upgrade to pax-url 2.6.1
[ https://issues.apache.org/jira/browse/KARAF-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737182#comment-16737182 ] ASF subversion and git services commented on KARAF-6079: Commit 48dc8e65ef173757e6e23af5459d739f30242f45 in karaf's branch refs/heads/master from Grzegorz Grzybek [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=48dc8e6 ] [KARAF-6005][KARAF-6079] Upgrade to pax-url 2.6.1 > Upgrade to pax-url 2.6.1 > > > Key: KARAF-6079 > URL: https://issues.apache.org/jira/browse/KARAF-6079 > Project: Karaf > Issue Type: Dependency upgrade >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.2.3 > > > pax-url 2.6.1 uses maver-resolver instead of eclipse-aether, but is > compatible. There are also several pax-url-aether fixes and a fix for > KARAF-6005 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6078) Misaligned versions of jetty between pax-web and standard features
[ https://issues.apache.org/jira/browse/KARAF-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-6078. - Resolution: Fixed > Misaligned versions of jetty between pax-web and standard features > -- > > Key: KARAF-6078 > URL: https://issues.apache.org/jira/browse/KARAF-6078 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Affects Versions: 4.1.6, 4.1.7 >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.8 > > > KARAF-5860 upgraded the jetty version brought it by pax-web, but did not > upgrade the version provided in features/standard, which was left at 9.3.21. > This means that depending on which feature downstreams are using, they may > end up with a vulnerable jetty version. > Furthermore, an offline distribution (like the one created for OpenDaylight) > will end up having both versions, leadining to unnecessary bloat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6078) Misaligned versions of jetty between pax-web and standard features
[ https://issues.apache.org/jira/browse/KARAF-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736968#comment-16736968 ] ASF subversion and git services commented on KARAF-6078: Commit 749d74ee364b7b9b265d70fc2ad5775f799db545 in karaf's branch refs/heads/karaf-4.1.x from Robert Varga [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=749d74e ] [KARAF-6078] bump jetty to 9.3.24.v20180605 > Misaligned versions of jetty between pax-web and standard features > -- > > Key: KARAF-6078 > URL: https://issues.apache.org/jira/browse/KARAF-6078 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Affects Versions: 4.1.6, 4.1.7 >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.8 > > > KARAF-5860 upgraded the jetty version brought it by pax-web, but did not > upgrade the version provided in features/standard, which was left at 9.3.21. > This means that depending on which feature downstreams are using, they may > end up with a vulnerable jetty version. > Furthermore, an offline distribution (like the one created for OpenDaylight) > will end up having both versions, leadining to unnecessary bloat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6005) Resolve of bundle with version range in a feature only works with ".m2" and not with "system" directory
[
https://issues.apache.org/jira/browse/KARAF-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated KARAF-6005:
Fix Version/s: 4.2.3
> Resolve of bundle with version range in a feature only works with ".m2" and
> not with "system" directory
> ---
>
> Key: KARAF-6005
> URL: https://issues.apache.org/jira/browse/KARAF-6005
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Volker Althaus
>Assignee: Grzegorz Grzybek
>Priority: Critical
> Fix For: 4.2.3
>
>
> I defined a feature with a ranged bundle version:
> {code:xml}
>
> mvn:de.some.api/api/[1,2)
>
> {code}
> If a bundle within that range lies within the global/user Maven repo ".m2",
> the bundle gets resolved.
> If it resides only within the "system" folder of Karaf I get an exception:
> {noformat}
> karaf@root()> org.apache.karaf.features.internal.util.MultiException: Error:
> Error downloading mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:91)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:457)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:452)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:224)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: java.io.IOException: Error downloading
> mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:77)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> ... 3 more
> Caused by: java.io.IOException: Error resolving artifact
> de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:729)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:659)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:600)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:567)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:47)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60)
> ... 7 more
> Caused by:
> shaded.org.eclipse.aether.resolution.VersionRangeResolutionException: No
> highest version found for de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveLatestVersionRange(AetherBasedResolver.java:998)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:703)
> ... 12 more
> {noformat}
> Setting the property org.ops4j.pax.url.mvn.defaultLocalRepoAsRemote = true as
> mentioned in the mailing list does not help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6080) Duplicate configuration randomly created on the first start in ConfigurationAdmin
[ https://issues.apache.org/jira/browse/KARAF-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J. Brébec updated KARAF-6080: - Attachment: karaf-6080.patch > Duplicate configuration randomly created on the first start in > ConfigurationAdmin > - > > Key: KARAF-6080 > URL: https://issues.apache.org/jira/browse/KARAF-6080 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.2 > Environment: Karaf 4.1.2, Karaf 4.2.2 > Windows 7, Equinox >Reporter: J. Brébec >Priority: Major > Attachments: karaf-6080.patch > > > On the first start, if a boot feature contains a element, and the > associated .cfg file exists in the etc folder, then this Configuration can be > created twice in ConfigurationAdmin : > # File Install check the etc folder and create for every cfg a Configuration > in ConfigurationAdmin > # the FeatureService (FeatureConfigInstaller), when a feature is installed > and has a configuration, check if this configuration exists in > ConfigurationAdmin. If the configuration doesn't exists, then it creates a > new one > If 1 and 2 are executed simultaneously, then the same configuration is > created twice in ConfigurationAdmin. If this configuration is linked to a > managed service, then this service will be instanciated twice. > By default, the karaf-maven-plugin copies every cfg to the etc folder, this > issue can probably be triggered by any element on a boot feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6080) Duplicate configuration randomly created on the first start in ConfigurationAdmin
[ https://issues.apache.org/jira/browse/KARAF-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737297#comment-16737297 ] J. Brébec commented on KARAF-6080: -- I have attached a patch I use since Karaf 4.1.2 > Duplicate configuration randomly created on the first start in > ConfigurationAdmin > - > > Key: KARAF-6080 > URL: https://issues.apache.org/jira/browse/KARAF-6080 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.2 > Environment: Karaf 4.1.2, Karaf 4.2.2 > Windows 7, Equinox >Reporter: J. Brébec >Priority: Major > Attachments: karaf-6080.patch > > > On the first start, if a boot feature contains a element, and the > associated .cfg file exists in the etc folder, then this Configuration can be > created twice in ConfigurationAdmin : > # File Install check the etc folder and create for every cfg a Configuration > in ConfigurationAdmin > # the FeatureService (FeatureConfigInstaller), when a feature is installed > and has a configuration, check if this configuration exists in > ConfigurationAdmin. If the configuration doesn't exists, then it creates a > new one > If 1 and 2 are executed simultaneously, then the same configuration is > created twice in ConfigurationAdmin. If this configuration is linked to a > managed service, then this service will be instanciated twice. > By default, the karaf-maven-plugin copies every cfg to the etc folder, this > issue can probably be triggered by any element on a boot feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6082) Eniment test case failure due to hard-coded karaf version
[ https://issues.apache.org/jira/browse/KARAF-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-6082. - Resolution: Not A Problem Fix Version/s: (was: 4.2.3) karaf.version property is already used, 4.2.3-SNAPSHOT is just a fallback (that should be removed anyway). > Eniment test case failure due to hard-coded karaf version > - > > Key: KARAF-6082 > URL: https://issues.apache.org/jira/browse/KARAF-6082 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.2 >Reporter: Martin Krüger >Assignee: Jean-Baptiste Onofré >Priority: Major > Attachments: > 0001-KARAF-6082-Remove-hard-coded-version-string-from-tes.patch > > > In commit aa78736c8da40d8a292d5c474fd270ab397b5074 hard coded karaf versions > in test cases were replaced by newer versions. But this does not solve the > problem. Latest with the next tag the code is broken again in case older > artefacts are not available during test runs. > Please see the attached patch to fix the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6038) Shell Table improvements
[ https://issues.apache.org/jira/browse/KARAF-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Krüger updated KARAF-6038: - Affects Version/s: 4.2.2 > Shell Table improvements > > > Key: KARAF-6038 > URL: https://issues.apache.org/jira/browse/KARAF-6038 > Project: Karaf > Issue Type: Improvement > Components: karaf >Affects Versions: 4.2.1, 4.2.2 >Reporter: Martin Krüger >Priority: Major > Attachments: > 0001-KARAF-6038-Several-improvements-of-Shell-Table-code.patch > > > The starting point was the warning of Java 11 that there is an "illegal > reflective access operation" which is not supported in later versions of Java. > Event though currently I see no way of getting rid of it without sacrificing > some functionality some other improvements were made along the way. (Mainly > shorten the code by getting rid of redundant functionality.) > Please have a look at the attached patch. > Thx. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6082) Eniment test case failure due to hard-coded karaf version
[
https://issues.apache.org/jira/browse/KARAF-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737945#comment-16737945
]
Martin Krüger commented on KARAF-6082:
--
In 59f500fc29940113b43ae64cee5d533110dd5784 that was the way to go. Either none
or all test cases should use {code}String karafVersion =
MavenUtils.getArtifactVersion("org.apache.karaf", "apache-karaf");
... System.getProperty("karaf.version", karafVersion) + ".jar") ...{code}
Having two versions is not good.
> Eniment test case failure due to hard-coded karaf version
> -
>
> Key: KARAF-6082
> URL: https://issues.apache.org/jira/browse/KARAF-6082
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Martin Krüger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments:
> 0001-KARAF-6082-Remove-hard-coded-version-string-from-tes.patch
>
>
> In commit aa78736c8da40d8a292d5c474fd270ab397b5074 hard coded karaf versions
> in test cases were replaced by newer versions. But this does not solve the
> problem. Latest with the next tag the code is broken again in case older
> artefacts are not available during test runs.
> Please see the attached patch to fix the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6082) Eniment test case failure due to hard-coded karaf version
[ https://issues.apache.org/jira/browse/KARAF-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737942#comment-16737942 ] Martin Krüger commented on KARAF-6082: -- Yes. That is what I also used in the patch. Thx. > Eniment test case failure due to hard-coded karaf version > - > > Key: KARAF-6082 > URL: https://issues.apache.org/jira/browse/KARAF-6082 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.2 >Reporter: Martin Krüger >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.3 > > Attachments: > 0001-KARAF-6082-Remove-hard-coded-version-string-from-tes.patch > > > In commit aa78736c8da40d8a292d5c474fd270ab397b5074 hard coded karaf versions > in test cases were replaced by newer versions. But this does not solve the > problem. Latest with the next tag the code is broken again in case older > artefacts are not available during test runs. > Please see the attached patch to fix the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6082) Eniment test case failure due to hard-coded karaf version
[ https://issues.apache.org/jira/browse/KARAF-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737940#comment-16737940 ] Jean-Baptiste Onofré commented on KARAF-6082: - I gonna use the karaf.version property in test. > Eniment test case failure due to hard-coded karaf version > - > > Key: KARAF-6082 > URL: https://issues.apache.org/jira/browse/KARAF-6082 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.2 >Reporter: Martin Krüger >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.3 > > > In commit aa78736c8da40d8a292d5c474fd270ab397b5074 hard coded karaf versions > in test cases were replaced by newer versions. But this does not solve the > problem. Latest with the next tag the code is broken again in case older > artefacts are not available during test runs. > Please see the attached patch to fix the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6082) Eniment test case failure due to hard-coded karaf version
[ https://issues.apache.org/jira/browse/KARAF-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6082: Fix Version/s: 4.2.3 > Eniment test case failure due to hard-coded karaf version > - > > Key: KARAF-6082 > URL: https://issues.apache.org/jira/browse/KARAF-6082 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.2 >Reporter: Martin Krüger >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.3 > > > In commit aa78736c8da40d8a292d5c474fd270ab397b5074 hard coded karaf versions > in test cases were replaced by newer versions. But this does not solve the > problem. Latest with the next tag the code is broken again in case older > artefacts are not available during test runs. > Please see the attached patch to fix the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6082) Eniment test case failure due to hard-coded karaf version
[ https://issues.apache.org/jira/browse/KARAF-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-6082: --- Assignee: Jean-Baptiste Onofré > Eniment test case failure due to hard-coded karaf version > - > > Key: KARAF-6082 > URL: https://issues.apache.org/jira/browse/KARAF-6082 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.2 >Reporter: Martin Krüger >Assignee: Jean-Baptiste Onofré >Priority: Major > > In commit aa78736c8da40d8a292d5c474fd270ab397b5074 hard coded karaf versions > in test cases were replaced by newer versions. But this does not solve the > problem. Latest with the next tag the code is broken again in case older > artefacts are not available during test runs. > Please see the attached patch to fix the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6082) Eniment test case failure due to hard-coded karaf version
[ https://issues.apache.org/jira/browse/KARAF-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6082: Component/s: karaf > Eniment test case failure due to hard-coded karaf version > - > > Key: KARAF-6082 > URL: https://issues.apache.org/jira/browse/KARAF-6082 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.2 >Reporter: Martin Krüger >Assignee: Jean-Baptiste Onofré >Priority: Major > > In commit aa78736c8da40d8a292d5c474fd270ab397b5074 hard coded karaf versions > in test cases were replaced by newer versions. But this does not solve the > problem. Latest with the next tag the code is broken again in case older > artefacts are not available during test runs. > Please see the attached patch to fix the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6082) Eniment test case failure due to hard-coded karaf version
[ https://issues.apache.org/jira/browse/KARAF-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Krüger updated KARAF-6082: - Attachment: 0001-KARAF-6082-Remove-hard-coded-version-string-from-tes.patch > Eniment test case failure due to hard-coded karaf version > - > > Key: KARAF-6082 > URL: https://issues.apache.org/jira/browse/KARAF-6082 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.2 >Reporter: Martin Krüger >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.3 > > Attachments: > 0001-KARAF-6082-Remove-hard-coded-version-string-from-tes.patch > > > In commit aa78736c8da40d8a292d5c474fd270ab397b5074 hard coded karaf versions > in test cases were replaced by newer versions. But this does not solve the > problem. Latest with the next tag the code is broken again in case older > artefacts are not available during test runs. > Please see the attached patch to fix the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6082) Eniment test case failure due to hard-coded karaf version
Martin Krüger created KARAF-6082: Summary: Eniment test case failure due to hard-coded karaf version Key: KARAF-6082 URL: https://issues.apache.org/jira/browse/KARAF-6082 Project: Karaf Issue Type: Bug Reporter: Martin Krüger In commit aa78736c8da40d8a292d5c474fd270ab397b5074 hard coded karaf versions in test cases were replaced by newer versions. But this does not solve the problem. Latest with the next tag the code is broken again in case older artefacts are not available during test runs. Please see the attached patch to fix the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6082) Eniment test case failure due to hard-coded karaf version
[ https://issues.apache.org/jira/browse/KARAF-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Krüger updated KARAF-6082: - Affects Version/s: 4.2.2 > Eniment test case failure due to hard-coded karaf version > - > > Key: KARAF-6082 > URL: https://issues.apache.org/jira/browse/KARAF-6082 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.2 >Reporter: Martin Krüger >Priority: Major > > In commit aa78736c8da40d8a292d5c474fd270ab397b5074 hard coded karaf versions > in test cases were replaced by newer versions. But this does not solve the > problem. Latest with the next tag the code is broken again in case older > artefacts are not available during test runs. > Please see the attached patch to fix the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6080) Duplicate configuration randomly created on the first start in ConfigurationAdmin
J. Brébec created KARAF-6080: Summary: Duplicate configuration randomly created on the first start in ConfigurationAdmin Key: KARAF-6080 URL: https://issues.apache.org/jira/browse/KARAF-6080 Project: Karaf Issue Type: Bug Components: karaf Affects Versions: 4.2.2 Environment: Karaf 4.1.2, Karaf 4.2.2 Windows 7, Equinox Reporter: J. Brébec On the first start, if a boot feature contains a element, and the associated .cfg file exists in the etc folder, then this Configuration can be created twice in ConfigurationAdmin : # File Install check the etc folder and create for every cfg a Configuration in ConfigurationAdmin # the FeatureService (FeatureConfigInstaller), when a feature is installed and has a configuration, check if this configuration exists in ConfigurationAdmin. If the configuration doesn't exists, then it creates a new one If 1 and 2 are executed simultaneously, then the same configuration is created twice in ConfigurationAdmin. If this configuration is linked to a managed service, then this service will be instanciated twice. By default, the karaf-maven-plugin copies every cfg to the etc folder, this issue can probably be triggered by any element on a boot feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6078) Misaligned versions of jetty between pax-web and standard features
Robert Varga created KARAF-6078: --- Summary: Misaligned versions of jetty between pax-web and standard features Key: KARAF-6078 URL: https://issues.apache.org/jira/browse/KARAF-6078 Project: Karaf Issue Type: Bug Components: karaf Affects Versions: 4.1.7, 4.1.6 Reporter: Robert Varga KARAF-5860 upgraded the jetty version brought it by pax-web, but did not upgrade the version provided in features/standard, which was left at 9.3.21. This means that depending on which feature downstreams are using, they may end up with a vulnerable jetty version. Furthermore, an offline distribution (like the one created for OpenDaylight) will end up having both versions, leadining to unnecessary bloat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6078) Misaligned versions of jetty between pax-web and standard features
[ https://issues.apache.org/jira/browse/KARAF-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Varga updated KARAF-6078: Issue Type: Dependency upgrade (was: Bug) > Misaligned versions of jetty between pax-web and standard features > -- > > Key: KARAF-6078 > URL: https://issues.apache.org/jira/browse/KARAF-6078 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Affects Versions: 4.1.6, 4.1.7 >Reporter: Robert Varga >Priority: Major > > KARAF-5860 upgraded the jetty version brought it by pax-web, but did not > upgrade the version provided in features/standard, which was left at 9.3.21. > This means that depending on which feature downstreams are using, they may > end up with a vulnerable jetty version. > Furthermore, an offline distribution (like the one created for OpenDaylight) > will end up having both versions, leadining to unnecessary bloat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6078) Misaligned versions of jetty between pax-web and standard features
[ https://issues.apache.org/jira/browse/KARAF-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6078: Fix Version/s: 4.1.8 > Misaligned versions of jetty between pax-web and standard features > -- > > Key: KARAF-6078 > URL: https://issues.apache.org/jira/browse/KARAF-6078 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Affects Versions: 4.1.6, 4.1.7 >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.8 > > > KARAF-5860 upgraded the jetty version brought it by pax-web, but did not > upgrade the version provided in features/standard, which was left at 9.3.21. > This means that depending on which feature downstreams are using, they may > end up with a vulnerable jetty version. > Furthermore, an offline distribution (like the one created for OpenDaylight) > will end up having both versions, leadining to unnecessary bloat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6078) Misaligned versions of jetty between pax-web and standard features
[ https://issues.apache.org/jira/browse/KARAF-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736969#comment-16736969 ] ASF subversion and git services commented on KARAF-6078: Commit 1ebcdb916711bbf8ae89ea50545da842d6e0b638 in karaf's branch refs/heads/karaf-4.1.x from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=1ebcdb9 ] Merge pull request #713 from rovarga/jetty-9.3.24 [KARAF-6078] bump jetty to 9.3.24.v20180605 > Misaligned versions of jetty between pax-web and standard features > -- > > Key: KARAF-6078 > URL: https://issues.apache.org/jira/browse/KARAF-6078 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Affects Versions: 4.1.6, 4.1.7 >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.8 > > > KARAF-5860 upgraded the jetty version brought it by pax-web, but did not > upgrade the version provided in features/standard, which was left at 9.3.21. > This means that depending on which feature downstreams are using, they may > end up with a vulnerable jetty version. > Furthermore, an offline distribution (like the one created for OpenDaylight) > will end up having both versions, leadining to unnecessary bloat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6078) Misaligned versions of jetty between pax-web and standard features
[ https://issues.apache.org/jira/browse/KARAF-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736966#comment-16736966 ] ASF GitHub Bot commented on KARAF-6078: --- jbonofre commented on pull request #713: [KARAF-6078] bump jetty to 9.3.24.v20180605 URL: https://github.com/apache/karaf/pull/713 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Misaligned versions of jetty between pax-web and standard features > -- > > Key: KARAF-6078 > URL: https://issues.apache.org/jira/browse/KARAF-6078 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Affects Versions: 4.1.6, 4.1.7 >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.8 > > > KARAF-5860 upgraded the jetty version brought it by pax-web, but did not > upgrade the version provided in features/standard, which was left at 9.3.21. > This means that depending on which feature downstreams are using, they may > end up with a vulnerable jetty version. > Furthermore, an offline distribution (like the one created for OpenDaylight) > will end up having both versions, leadining to unnecessary bloat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6078) Misaligned versions of jetty between pax-web and standard features
[ https://issues.apache.org/jira/browse/KARAF-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736925#comment-16736925 ] ASF GitHub Bot commented on KARAF-6078: --- rovarga commented on pull request #713: [KARAF-6078] bump jetty to 9.3.24.v20180605 URL: https://github.com/apache/karaf/pull/713 This aligns jetty version used by features/standard with the version used by pas-web-6.0.11. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Misaligned versions of jetty between pax-web and standard features > -- > > Key: KARAF-6078 > URL: https://issues.apache.org/jira/browse/KARAF-6078 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Affects Versions: 4.1.6, 4.1.7 >Reporter: Robert Varga >Priority: Major > > KARAF-5860 upgraded the jetty version brought it by pax-web, but did not > upgrade the version provided in features/standard, which was left at 9.3.21. > This means that depending on which feature downstreams are using, they may > end up with a vulnerable jetty version. > Furthermore, an offline distribution (like the one created for OpenDaylight) > will end up having both versions, leadining to unnecessary bloat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6078) Misaligned versions of jetty between pax-web and standard features
[ https://issues.apache.org/jira/browse/KARAF-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-6078: --- Assignee: Jean-Baptiste Onofré > Misaligned versions of jetty between pax-web and standard features > -- > > Key: KARAF-6078 > URL: https://issues.apache.org/jira/browse/KARAF-6078 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Affects Versions: 4.1.6, 4.1.7 >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré >Priority: Major > > KARAF-5860 upgraded the jetty version brought it by pax-web, but did not > upgrade the version provided in features/standard, which was left at 9.3.21. > This means that depending on which feature downstreams are using, they may > end up with a vulnerable jetty version. > Furthermore, an offline distribution (like the one created for OpenDaylight) > will end up having both versions, leadining to unnecessary bloat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
