[jira] [Commented] (KARAF-3733) Update the repository.xml in a repository "on the fly"
[ https://issues.apache.org/jira/browse/KARAF-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400502#comment-15400502 ] Morgan Hautman commented on KARAF-3733: --- We have two solutions here: 1. Add options to the cave:repository-update command. 2. Make a new command cave:scan-repository that would kind of duplicate the behavior of cave:repository-update. I would choose for option 1, WDYT? And can you also confirm that the scheduler should use Karaf's QuartzScheduler? Thanks, Morgan > Update the repository.xml in a repository "on the fly" > -- > > Key: KARAF-3733 > URL: https://issues.apache.org/jira/browse/KARAF-3733 > Project: Karaf > Issue Type: Improvement > Components: cave-server >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: cave-3.0.1, cave-4.0.1 > > > Right now, the only way to update the OBR metadata is by performing the scan > command. Meaning that we need to execute the command each time that the > repository is updated (adding/removing an artifact for instance). > It makes sense to have a thread that periodically update the OBR metadata > (that we can enable/disable with a command, like cave:scan-repository -a for > auto). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4642 started by Jean-Baptiste Onofré. --- > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 3.0.8 > > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3748) Installing activemq-blueprint feature sometimes fails with uses constraint violation
[
https://issues.apache.org/jira/browse/KARAF-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400067#comment-15400067
]
Hadrian Zbarcea commented on KARAF-3748:
[~jbonofre], yes it is, I experience it too.
> Installing activemq-blueprint feature sometimes fails with uses constraint
> violation
>
>
> Key: KARAF-3748
> URL: https://issues.apache.org/jira/browse/KARAF-3748
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.0.0.M3
>Reporter: Achim Finke
> Fix For: 4.1.0, 4.0.6
>
>
> From time to time you get the following exception when installing
> activemq-blueprint feature.
> {code}
> org.osgi.service.resolver.ResolutionException: Uses constraint violation.
> Unable to resolve resource org.apache.activemq.activemq-blueprint
> [org.apache.activemq.activemq-blueprint/5.11.1] because it is exposed to
> package 'org.apache.aries.blueprint' from resources
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] and
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] via
> two dependency chains.
> Chain 1:
> org.apache.activemq.activemq-blueprint
> [org.apache.activemq.activemq-blueprint/5.11.1]
> import:
> (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package: org.apache.aries.blueprint
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3]
> Chain 2:
> org.apache.activemq.activemq-blueprint
> [org.apache.activemq.activemq-blueprint/5.11.1]
> import:
> (&(osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version>=3.13.0)(!(version>=4.0.0)))
> |
> export: osgi.wiring.package=org.apache.xbean.blueprint.context.impl;
> uses:=org.apache.aries.blueprint
> org.apache.xbean.blueprint [org.apache.xbean.blueprint/3.18.0]
> import:
> (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package: org.apache.aries.blueprint
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3]
> at
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1410)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:289)[org.apache.felix.framework-5.0.0.jar:]
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:185)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:261)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1061)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:960)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_31]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_31]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_31]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]
> {code}
> The behaviour is not predictable. Installation worked x times, afterwards
> installation failed y times so you may need some trys to reproduce.
> To reproduce execute:
> {code}
> feature:repo-add activemq 5.11.1
> feature:install activemq-blueprint
> {code}
> if you don't get the exception stop the container, delete data folder and try
> again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4642: Fix Version/s: 3.0.8 > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Priority: Critical > Fix For: 3.0.8 > > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-4642: --- Assignee: Jean-Baptiste Onofré > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 3.0.8 > > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399843#comment-15399843 ] James Carman commented on KARAF-4642: - Pull request created: https://github.com/apache/karaf/pull/218 > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Priority: Critical > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399833#comment-15399833 ] ASF GitHub Bot commented on KARAF-4642: --- GitHub user jwcarman opened a pull request: https://github.com/apache/karaf/pull/218 KARAF-4642: featuresBoot order is not honored You can merge this pull request into a Git repository by running: $ git pull https://github.com/jwcarman/karaf KARAF-4642 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/karaf/pull/218.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #218 commit f72a527c48ae39b12f6a6b1821846865da3c28e2 Author: James Carman Date: 2016-07-29T18:40:57Z KARAF-4642: featuresBoot order is not honored > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Priority: Critical > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4642) featuresBoot order is not honored
James Carman created KARAF-4642: --- Summary: featuresBoot order is not honored Key: KARAF-4642 URL: https://issues.apache.org/jira/browse/KARAF-4642 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 3.0.7 Reporter: James Carman Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated KARAF-4642: Description: When starting up a vanilla 3.0.7 installation, the featuresBoot is: config,standard,region,package,kar,ssh,management However, looking at the log files, they are not installed in that order: 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature kar 3.0.7 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature management 3.0.7 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature config 3.0.7 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature standard 3.0.7 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature region 3.0.7 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature ssh 3.0.7 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature package 3.0.7 > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Priority: Critical > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4640) Support startLevel in startup bundle/features for kustom karaf distribution
[
https://issues.apache.org/jira/browse/KARAF-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli updated KARAF-4640:
---
Description:
When used to generate a custom distribution, the karaf-maven-plugin place all
the bundles configured in startupBundles section at the same start level which
could cause issues if the startup order matters (i.e. a blueprint extension is
required) so it would be nice if the startup level could be configured directly
from the plugin to avoid writing a custom feature, something like:
{code:xml}
mvn:my/bundle-1/version
60
mvn:my/bundle-2/version
80
{code}
Or:
{code:xml}
mvn:my/bundle-1/version@60
mvn:my/bundle-2/version@80
{code}
was:
When used to generate a custom distribution, the karaf-maven-plugin place all
the bundles configured in startupBundles section at the same start level which
could cause issues if the startup order matters (i.e. a blueprint extension is
required) so it would be nice if the startup level could be configured directly
from the plugin to avoid writing a custom feature, something like:
{code:xml}
mvn:my/bundle-1/version
mvn:my/bundle-2/version
{code}
> Support startLevel in startup bundle/features for kustom karaf distribution
> ---
>
> Key: KARAF-4640
> URL: https://issues.apache.org/jira/browse/KARAF-4640
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Reporter: Luca Burgazzoli
>
> When used to generate a custom distribution, the karaf-maven-plugin place all
> the bundles configured in startupBundles section at the same start level
> which could cause issues if the startup order matters (i.e. a blueprint
> extension is required) so it would be nice if the startup level could be
> configured directly from the plugin to avoid writing a custom feature,
> something like:
> {code:xml}
>
>
>
> mvn:my/bundle-1/version
> 60
>
>
> mvn:my/bundle-2/version
> 80
>
>
>
> {code}
> Or:
> {code:xml}
>
>
> mvn:my/bundle-1/version@60
> mvn:my/bundle-2/version@80
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4641) Possible problems with wrap jars in profiles
[ https://issues.apache.org/jira/browse/KARAF-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-4641. Resolution: Fixed > Possible problems with wrap jars in profiles > > > Key: KARAF-4641 > URL: https://issues.apache.org/jira/browse/KARAF-4641 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.5 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0, 4.0.6 > > > Quotes can be used in wrap:xxx uris but they are not fully valid URIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4641) Possible problems with wrap jars in profiles
[ https://issues.apache.org/jira/browse/KARAF-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399485#comment-15399485 ] ASF subversion and git services commented on KARAF-4641: Commit 783212924e67c0028240e55ce1d413141c0c6239 in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=7832129 ] [KARAF-4641] Fix problem with wrap uri with quotes and profiles > Possible problems with wrap jars in profiles > > > Key: KARAF-4641 > URL: https://issues.apache.org/jira/browse/KARAF-4641 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.5 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0, 4.0.6 > > > Quotes can be used in wrap:xxx uris but they are not fully valid URIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4641) Possible problems with wrap jars in profiles
[ https://issues.apache.org/jira/browse/KARAF-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399479#comment-15399479 ] ASF subversion and git services commented on KARAF-4641: Commit 2c0bf85f9f29e7366ad4059d71c60fb9a4678ae9 in karaf's branch refs/heads/karaf-4.0.x from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=2c0bf85 ] [KARAF-4641] Fix problem with wrap uri with quotes and profiles > Possible problems with wrap jars in profiles > > > Key: KARAF-4641 > URL: https://issues.apache.org/jira/browse/KARAF-4641 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.5 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0, 4.0.6 > > > Quotes can be used in wrap:xxx uris but they are not fully valid URIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4641) Possible problems with wrap jars in profiles
Guillaume Nodet created KARAF-4641: -- Summary: Possible problems with wrap jars in profiles Key: KARAF-4641 URL: https://issues.apache.org/jira/browse/KARAF-4641 Project: Karaf Issue Type: Bug Affects Versions: 4.0.5 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.1.0, 4.0.6 Quotes can be used in wrap:xxx uris but they are not fully valid URIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4640) Support startLevel in startup bundle/features for kustom karaf distribution
Luca Burgazzoli created KARAF-4640:
--
Summary: Support startLevel in startup bundle/features for kustom
karaf distribution
Key: KARAF-4640
URL: https://issues.apache.org/jira/browse/KARAF-4640
Project: Karaf
Issue Type: Improvement
Components: karaf-tooling
Reporter: Luca Burgazzoli
When used to generate a custom distribution, the karaf-maven-plugin place all
the bundles configured in startupBundles section at the same start level which
could cause issues if the startup order matters (i.e. a blueprint extension is
required) so it would be nice if the startup level could be configured directly
from the plugin to avoid writing a custom feature, something like:
{code:xml}
mvn:my/bundle-1/version
mvn:my/bundle-2/version
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4615) Cannot get OpenJPA 2.4.1 to work due to JPA 2.1 being installed
[ https://issues.apache.org/jira/browse/KARAF-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399255#comment-15399255 ] Christian Schneider edited comment on KARAF-4615 at 7/29/16 12:31 PM: -- I finally found a way to make both hibernate 4.3 and openjpa 2.4.1 work. Of course not at the same time .. but at least at all. Just pushed a change on master .. can you test this? was (Author: ch...@die-schneider.net): I finally found a way to make both hibernate 4.3 and openjpa 2.4.1 work. Of course not at the same time .. but at least at all. > Cannot get OpenJPA 2.4.1 to work due to JPA 2.1 being installed > --- > > Key: KARAF-4615 > URL: https://issues.apache.org/jira/browse/KARAF-4615 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.5 >Reporter: Bengt Rodehav >Assignee: Christian Schneider > Fix For: 4.0.6 > > > In order to use OpenJPA 2.4.1 both the "openjpa" (2.4.1) feature and the > "jpa" (2.3.0) features need to be installed. > However, OpenJPA needs JPA 2.0 - it does not work with JPA 2.1. But when > installing the "jpa" (2.3.0) feature, JPA 2.1 is being installed. > This has been discussed on the Karaf user list under the subject "Migrating > from Karaf 2.4.1 to 4.0.5, JPA problems". > I have, as a workaround, modified the enterprise-4.0.5-features.xml, feature > "jpa" (2.3.0), as follows: > * I have changed the version range for the peristence-api feature from > [2.0.0,2.2.0) to [2.0.0,2.1.0). This disqualifies JPA 2.1 and instead cause > JPA 2.0 to be installed. > * The JPA 2.1 bundle seemed to be providing the package org.osgi.service.jpa > which is mandatory. I therefore added the following dependency: > ** mvn:org.osgi/org.osgi.service.jpa/1.0.0 > So my modified "jpa" (2.3.0) feature now looks like this: > > JPA implementation provided by Apache Aries JPA 2.x. NB: this > feature doesn't provide the JPA engine, you have to install one by yourself > (OpenJPA for instance) > dependency="false">transaction-api > mvn:org.osgi/org.osgi.service.jpa/1.0.0 > dependency="false">persistence-api > dependency="true">mvn:org.apache.felix/org.apache.felix.coordinator/1.0.2 > dependency="true">mvn:org.osgi/org.osgi.service.jdbc/1.0.0 > mvn:org.apache.aries.jpa/org.apache.aries.jpa.api/2.3.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/2.3.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.support/2.3.0 > > aries-blueprint > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint/2.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4615) Cannot get OpenJPA 2.4.1 to work due to JPA 2.1 being installed
[ https://issues.apache.org/jira/browse/KARAF-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399256#comment-15399256 ] ASF subversion and git services commented on KARAF-4615: Commit 7c44db45f4c8d75b2a7fabf9eaec3e37b84bfec1 in karaf's branch refs/heads/master from [~ch...@die-schneider.net] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=7c44db4 ] [KARAF-4615] Make sure providers requiring jpa 2.0 and 2.1 can both work > Cannot get OpenJPA 2.4.1 to work due to JPA 2.1 being installed > --- > > Key: KARAF-4615 > URL: https://issues.apache.org/jira/browse/KARAF-4615 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.5 >Reporter: Bengt Rodehav >Assignee: Christian Schneider > Fix For: 4.0.6 > > > In order to use OpenJPA 2.4.1 both the "openjpa" (2.4.1) feature and the > "jpa" (2.3.0) features need to be installed. > However, OpenJPA needs JPA 2.0 - it does not work with JPA 2.1. But when > installing the "jpa" (2.3.0) feature, JPA 2.1 is being installed. > This has been discussed on the Karaf user list under the subject "Migrating > from Karaf 2.4.1 to 4.0.5, JPA problems". > I have, as a workaround, modified the enterprise-4.0.5-features.xml, feature > "jpa" (2.3.0), as follows: > * I have changed the version range for the peristence-api feature from > [2.0.0,2.2.0) to [2.0.0,2.1.0). This disqualifies JPA 2.1 and instead cause > JPA 2.0 to be installed. > * The JPA 2.1 bundle seemed to be providing the package org.osgi.service.jpa > which is mandatory. I therefore added the following dependency: > ** mvn:org.osgi/org.osgi.service.jpa/1.0.0 > So my modified "jpa" (2.3.0) feature now looks like this: > > JPA implementation provided by Apache Aries JPA 2.x. NB: this > feature doesn't provide the JPA engine, you have to install one by yourself > (OpenJPA for instance) > dependency="false">transaction-api > mvn:org.osgi/org.osgi.service.jpa/1.0.0 > dependency="false">persistence-api > dependency="true">mvn:org.apache.felix/org.apache.felix.coordinator/1.0.2 > dependency="true">mvn:org.osgi/org.osgi.service.jdbc/1.0.0 > mvn:org.apache.aries.jpa/org.apache.aries.jpa.api/2.3.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/2.3.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.support/2.3.0 > > aries-blueprint > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint/2.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4615) Cannot get OpenJPA 2.4.1 to work due to JPA 2.1 being installed
[ https://issues.apache.org/jira/browse/KARAF-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399255#comment-15399255 ] Christian Schneider commented on KARAF-4615: I finally found a way to make both hibernate 4.3 and openjpa 2.4.1 work. Of course not at the same time .. but at least at all. > Cannot get OpenJPA 2.4.1 to work due to JPA 2.1 being installed > --- > > Key: KARAF-4615 > URL: https://issues.apache.org/jira/browse/KARAF-4615 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.5 >Reporter: Bengt Rodehav >Assignee: Christian Schneider > Fix For: 4.0.6 > > > In order to use OpenJPA 2.4.1 both the "openjpa" (2.4.1) feature and the > "jpa" (2.3.0) features need to be installed. > However, OpenJPA needs JPA 2.0 - it does not work with JPA 2.1. But when > installing the "jpa" (2.3.0) feature, JPA 2.1 is being installed. > This has been discussed on the Karaf user list under the subject "Migrating > from Karaf 2.4.1 to 4.0.5, JPA problems". > I have, as a workaround, modified the enterprise-4.0.5-features.xml, feature > "jpa" (2.3.0), as follows: > * I have changed the version range for the peristence-api feature from > [2.0.0,2.2.0) to [2.0.0,2.1.0). This disqualifies JPA 2.1 and instead cause > JPA 2.0 to be installed. > * The JPA 2.1 bundle seemed to be providing the package org.osgi.service.jpa > which is mandatory. I therefore added the following dependency: > ** mvn:org.osgi/org.osgi.service.jpa/1.0.0 > So my modified "jpa" (2.3.0) feature now looks like this: > > JPA implementation provided by Apache Aries JPA 2.x. NB: this > feature doesn't provide the JPA engine, you have to install one by yourself > (OpenJPA for instance) > dependency="false">transaction-api > mvn:org.osgi/org.osgi.service.jpa/1.0.0 > dependency="false">persistence-api > dependency="true">mvn:org.apache.felix/org.apache.felix.coordinator/1.0.2 > dependency="true">mvn:org.osgi/org.osgi.service.jdbc/1.0.0 > mvn:org.apache.aries.jpa/org.apache.aries.jpa.api/2.3.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/2.3.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.support/2.3.0 > > aries-blueprint > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint/2.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4615) Cannot get OpenJPA 2.4.1 to work due to JPA 2.1 being installed
[ https://issues.apache.org/jira/browse/KARAF-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398985#comment-15398985 ] Christian Schneider commented on KARAF-4615: I tried with embedding the OSGi jpa api into Aries JPA and use a JPA 2.1 bundle that does not embed the OSGi JPA but it did not help. So not sure how to proceed here. Separate feature for JPA 2.1 and JP2 2.0 might be necessary. I am only a bit concerned about the confusions with the Aries JPA version number. > Cannot get OpenJPA 2.4.1 to work due to JPA 2.1 being installed > --- > > Key: KARAF-4615 > URL: https://issues.apache.org/jira/browse/KARAF-4615 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.5 >Reporter: Bengt Rodehav >Assignee: Christian Schneider > Fix For: 4.0.6 > > > In order to use OpenJPA 2.4.1 both the "openjpa" (2.4.1) feature and the > "jpa" (2.3.0) features need to be installed. > However, OpenJPA needs JPA 2.0 - it does not work with JPA 2.1. But when > installing the "jpa" (2.3.0) feature, JPA 2.1 is being installed. > This has been discussed on the Karaf user list under the subject "Migrating > from Karaf 2.4.1 to 4.0.5, JPA problems". > I have, as a workaround, modified the enterprise-4.0.5-features.xml, feature > "jpa" (2.3.0), as follows: > * I have changed the version range for the peristence-api feature from > [2.0.0,2.2.0) to [2.0.0,2.1.0). This disqualifies JPA 2.1 and instead cause > JPA 2.0 to be installed. > * The JPA 2.1 bundle seemed to be providing the package org.osgi.service.jpa > which is mandatory. I therefore added the following dependency: > ** mvn:org.osgi/org.osgi.service.jpa/1.0.0 > So my modified "jpa" (2.3.0) feature now looks like this: > > JPA implementation provided by Apache Aries JPA 2.x. NB: this > feature doesn't provide the JPA engine, you have to install one by yourself > (OpenJPA for instance) > dependency="false">transaction-api > mvn:org.osgi/org.osgi.service.jpa/1.0.0 > dependency="false">persistence-api > dependency="true">mvn:org.apache.felix/org.apache.felix.coordinator/1.0.2 > dependency="true">mvn:org.osgi/org.osgi.service.jdbc/1.0.0 > mvn:org.apache.aries.jpa/org.apache.aries.jpa.api/2.3.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/2.3.0 > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.support/2.3.0 > > aries-blueprint > > mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint/2.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4535) OpenJPA 2.4.1 Missing dependencies: objectClass=javax.persistence.EntityManager
[
https://issues.apache.org/jira/browse/KARAF-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398963#comment-15398963
]
Christian Schneider commented on KARAF-4535:
I found no good solution to this problem. When I do changes to limit the
persistence API to 2.0 then other databases with 2.1 do not work anymore. We
might need a fix in Aries JPA to be able to cope with both APIs being installed
at the same time.
> OpenJPA 2.4.1 Missing dependencies:
> objectClass=javax.persistence.EntityManager
> ---
>
> Key: KARAF-4535
> URL: https://issues.apache.org/jira/browse/KARAF-4535
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.5
> Environment: Karaf 4.0.5
> OpenJPA 2.4.1
>Reporter: Jirka
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.6
>
>
> OpenJPA 2.4.1 does not start when installed with the jpa feature.
> Problem is that the jpa feature installs persistence api 2.1.0
> {code}
> dependency="false">persistence-api
>
> {code}
> It collides with persistence api 2.0.0 installed by the openjpa feature
> {code}
> dependency="false">persistence-api
> {code}
> Workaround is to use this custom jpa feature instead of the jpa feature.
> {code}
>version="2.3.0">
> JPA implementation provided by Apache Aries JPA 2.x.
> NB: this feature doesn't provide the JPA engine, you have to install one by
> yourself (OpenJPA for instance)
>dependency="false">transaction-api
>dependency="true">mvn:org.apache.felix/org.apache.felix.coordinator/1.0.2
>dependency="true">mvn:org.osgi/org.osgi.service.jdbc/1.0.0
> mvn:org.osgi/org.osgi.service.jpa/1.0.0
>
> mvn:org.apache.aries.jpa/org.apache.aries.jpa.api/2.3.0
>
> mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/2.3.0
>
> mvn:org.apache.aries.jpa/org.apache.aries.jpa.support/2.3.0
>
> aries-blueprint
>
> mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint/2.3.0
>
>
> {code}
> Changes compared to the karaf jpa feature::
> Removed:
> {code}
> dependency="false">persistence-api
> {code}
> Added
> {code}
> mvn:org.osgi/org.osgi.service.jpa/1.0.0 added
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4158) Unexpected behavior on first startup
[ https://issues.apache.org/jira/browse/KARAF-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-4158. Resolution: Cannot Reproduce Closing as there was no further activity > Unexpected behavior on first startup > > > Key: KARAF-4158 > URL: https://issues.apache.org/jira/browse/KARAF-4158 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.3 > Environment: RHEL 6.2 x32, Java 1.8.0_72-ea-b05 >Reporter: Jean-Philippe CLEMENT >Assignee: Christian Schneider > Fix For: 4.1.0, 4.0.6 > > > This problem only occurs on the very first startup of a custom assembly. This > means unpacking the assembly .tar.gz then run karaf. This issue is not 100% > reproducible. Several untar/run might be necessary to reproduce the issue. > The problem comes with Blueprint property-placeholders. User bundles might be > started and not get .cfg replaced properties but the "$(PARAM_NAME)" itself > (String property). > I suspect user bundles to be started before the .cfg files are populated in > the /etc directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4221) Add Decanter REST service collector and appender
[ https://issues.apache.org/jira/browse/KARAF-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-4221. Resolution: Fixed > Add Decanter REST service collector and appender > > > Key: KARAF-4221 > URL: https://issues.apache.org/jira/browse/KARAF-4221 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Christian Schneider > > In order to be able to use decanter outside of karaf, it would be interesting > if decanter can provide a REST service/API to append collected data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4577) Use ServiceComponentRuntime api and provide a BundleStateService for DS
[ https://issues.apache.org/jira/browse/KARAF-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-4577. Resolution: Fixed > Use ServiceComponentRuntime api and provide a BundleStateService for DS > --- > > Key: KARAF-4577 > URL: https://issues.apache.org/jira/browse/KARAF-4577 > Project: Karaf > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4628) Can not start karaf on linux
[ https://issues.apache.org/jira/browse/KARAF-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-4628. Resolution: Fixed > Can not start karaf on linux > > > Key: KARAF-4628 > URL: https://issues.apache.org/jira/browse/KARAF-4628 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.1.0 >Reporter: Christian Schneider >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > > I am not able to start karaf build from master. See below for how to > reproduce. > Build karaf from master using: > mvn clean install -Pfastinstall > and unpack using > tar -xzvf > ~/checkout/karaf/assemblies/apache-karaf/target/apache-karaf-4.1.0-SNAPSHOT.tar.gz > cschneider@wscschneider:~/java/apache-karaf-4.1.0-SNAPSHOT$ bin/karaf > Error: Could not find or load main class org.apache.karaf.main.Main > See here for a run with bash -x: http://apaste.info/esV > It seems like karaf is detecting the karaf directory wrongly. > If I cd to the bin dir and run karaf from there it works. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4599) KARAF-4564 impact: karaf startup command now only works when invoked from current directoy, no longer via absolute path
[
https://issues.apache.org/jira/browse/KARAF-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved KARAF-4599.
Resolution: Fixed
> KARAF-4564 impact: karaf startup command now only works when invoked from
> current directoy, no longer via absolute path
> ---
>
> Key: KARAF-4599
> URL: https://issues.apache.org/jira/browse/KARAF-4599
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 3.0.7, 3.0.8
>Reporter: Michael Vorburger
>Assignee: Guillaume Nodet
>Priority: Critical
> Fix For: 4.1.0, 4.0.6, 3.0.8
>
>
> KARAF-4564 introduced a fix for "Can't start karaf using symbolic link", but
> this introduced a new regression: Following that change, the ./karaf startup
> command now only works when invoked from current directoy, no longer via
> absolute path. For example:
> {noformat}git clone git://git.apache.org/karaf.git
> cd karaf
> git checkout karaf-3.0.x
> cd tooling/karaf-maven-plugin
> mvn clean install
> cd ../..
> mvn clean install -DskipTests
> cd assemblies/apache-karaf/target/assembly/bin/
> chmod +x karaf
> ./karaf
> cd ../../../../..
> ./assemblies/apache-karaf/target/assembly/bin/karaf
> Error: Could not find or load main class org.apache.karaf.main.Main
> {noformat}
> Of course we could further fiddle with the startup script to solve this
> somehow, but it occurred to me that perhaps somewhere on Apache there is a
> ready made script for this already? Like maybe looking at e.g. how the Maven
> / Ant & other such tools (Gradle?) would be valuable.
> Perhaps some sort of non-regression integration test for both start-up
> scenarios, from current as well as via abs. path, would be of value?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4564) Can't start karaf using symbolic link
[ https://issues.apache.org/jira/browse/KARAF-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398859#comment-15398859 ] ASF subversion and git services commented on KARAF-4564: Commit c06766b1137a4999f537bee8db77c6f2257893e2 in karaf's branch refs/heads/karaf-4.0.x from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=c06766b ] [KARAF-4628] [KARAF-4564] Fix unix startup scripts > Can't start karaf using symbolic link > -- > > Key: KARAF-4564 > URL: https://issues.apache.org/jira/browse/KARAF-4564 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.6 > Environment: Ubuntu (Linux vagrant 3.19.0-25-generic > #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 > GNU/Linux) > OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep 1 > 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64) > Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) >Reporter: Alexis de Talhouët >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.7, 4.0.6 > > > When using a symbolic link to use the scripts defined here: > https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin > e.g. karaf or client and so on, it's failing to start the container and show > this error: > Error: Could not find or load main class org.apache.karaf.main.Main > This issue is related to the DIRNAME variable and the way it is setup. > This bug has been found in OpenDaylight, here is the ticket with more > information https://bugs.opendaylight.org/show_bug.cgi?id=6027 > I have also propose a candidate fix in ODL: > https://git.opendaylight.org/gerrit/#/c/39982/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4628) Can not start karaf on linux
[ https://issues.apache.org/jira/browse/KARAF-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398858#comment-15398858 ] ASF subversion and git services commented on KARAF-4628: Commit c06766b1137a4999f537bee8db77c6f2257893e2 in karaf's branch refs/heads/karaf-4.0.x from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=c06766b ] [KARAF-4628] [KARAF-4564] Fix unix startup scripts > Can not start karaf on linux > > > Key: KARAF-4628 > URL: https://issues.apache.org/jira/browse/KARAF-4628 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.1.0 >Reporter: Christian Schneider >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > > I am not able to start karaf build from master. See below for how to > reproduce. > Build karaf from master using: > mvn clean install -Pfastinstall > and unpack using > tar -xzvf > ~/checkout/karaf/assemblies/apache-karaf/target/apache-karaf-4.1.0-SNAPSHOT.tar.gz > cschneider@wscschneider:~/java/apache-karaf-4.1.0-SNAPSHOT$ bin/karaf > Error: Could not find or load main class org.apache.karaf.main.Main > See here for a run with bash -x: http://apaste.info/esV > It seems like karaf is detecting the karaf directory wrongly. > If I cd to the bin dir and run karaf from there it works. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4570) Upgrade to jline 3
[ https://issues.apache.org/jira/browse/KARAF-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-4570. Resolution: Fixed > Upgrade to jline 3 > -- > > Key: KARAF-4570 > URL: https://issues.apache.org/jira/browse/KARAF-4570 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4639) Add job control in the console
[ https://issues.apache.org/jira/browse/KARAF-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-4639. Resolution: Fixed > Add job control in the console > -- > > Key: KARAF-4639 > URL: https://issues.apache.org/jira/browse/KARAF-4639 > Project: Karaf > Issue Type: Improvement > Components: karaf-shell >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > > * add 3 commands: jobs, fg, bg > * disable sigtstp in the karaf shell script > * handle Ctrl+C / Ctrl+Z correctly in the shell -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4639) Add job control in the console
[ https://issues.apache.org/jira/browse/KARAF-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398852#comment-15398852 ] ASF subversion and git services commented on KARAF-4639: Commit 8c06b2e9298941b132e12d1fdf4485c173dba3b3 in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=8c06b2e ] [KARAF-4639] Add job control in the console > Add job control in the console > -- > > Key: KARAF-4639 > URL: https://issues.apache.org/jira/browse/KARAF-4639 > Project: Karaf > Issue Type: Improvement > Components: karaf-shell >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > > * add 3 commands: jobs, fg, bg > * disable sigtstp in the karaf shell script > * handle Ctrl+C / Ctrl+Z correctly in the shell -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4564) Can't start karaf using symbolic link
[ https://issues.apache.org/jira/browse/KARAF-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398854#comment-15398854 ] ASF subversion and git services commented on KARAF-4564: Commit 5bbaf71814df514b112cbe8cd73ba57fefdc869f in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=5bbaf71 ] [KARAF-4628] [KARAF-4564] Fix unix startup scripts > Can't start karaf using symbolic link > -- > > Key: KARAF-4564 > URL: https://issues.apache.org/jira/browse/KARAF-4564 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.6 > Environment: Ubuntu (Linux vagrant 3.19.0-25-generic > #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 > GNU/Linux) > OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep 1 > 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64) > Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) >Reporter: Alexis de Talhouët >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.7, 4.0.6 > > > When using a symbolic link to use the scripts defined here: > https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin > e.g. karaf or client and so on, it's failing to start the container and show > this error: > Error: Could not find or load main class org.apache.karaf.main.Main > This issue is related to the DIRNAME variable and the way it is setup. > This bug has been found in OpenDaylight, here is the ticket with more > information https://bugs.opendaylight.org/show_bug.cgi?id=6027 > I have also propose a candidate fix in ODL: > https://git.opendaylight.org/gerrit/#/c/39982/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4628) Can not start karaf on linux
[ https://issues.apache.org/jira/browse/KARAF-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398853#comment-15398853 ] ASF subversion and git services commented on KARAF-4628: Commit 5bbaf71814df514b112cbe8cd73ba57fefdc869f in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=5bbaf71 ] [KARAF-4628] [KARAF-4564] Fix unix startup scripts > Can not start karaf on linux > > > Key: KARAF-4628 > URL: https://issues.apache.org/jira/browse/KARAF-4628 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.1.0 >Reporter: Christian Schneider >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > > I am not able to start karaf build from master. See below for how to > reproduce. > Build karaf from master using: > mvn clean install -Pfastinstall > and unpack using > tar -xzvf > ~/checkout/karaf/assemblies/apache-karaf/target/apache-karaf-4.1.0-SNAPSHOT.tar.gz > cschneider@wscschneider:~/java/apache-karaf-4.1.0-SNAPSHOT$ bin/karaf > Error: Could not find or load main class org.apache.karaf.main.Main > See here for a run with bash -x: http://apaste.info/esV > It seems like karaf is detecting the karaf directory wrongly. > If I cd to the bin dir and run karaf from there it works. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
