[jira] [Work started] (KARAF-4635) Upgrade Pax JDBC to version 0.9.0
[ https://issues.apache.org/jira/browse/KARAF-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4635 started by Jean-Baptiste Onofré. --- > Upgrade Pax JDBC to version 0.9.0 > - > > Key: KARAF-4635 > URL: https://issues.apache.org/jira/browse/KARAF-4635 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Lukas Roedl >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > > some time ago Pax JDBC 0.9.0 was released. Changelog can be found at > https://ops4j1.jira.com/wiki/display/PAXJDBC/2016/06/23/PAX+JDBC+0.9.0+Released -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4635) Upgrade Pax JDBC to version 0.9.0
[ https://issues.apache.org/jira/browse/KARAF-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4635: Fix Version/s: 4.0.6 4.1.0 > Upgrade Pax JDBC to version 0.9.0 > - > > Key: KARAF-4635 > URL: https://issues.apache.org/jira/browse/KARAF-4635 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Lukas Roedl >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > > some time ago Pax JDBC 0.9.0 was released. Changelog can be found at > https://ops4j1.jira.com/wiki/display/PAXJDBC/2016/06/23/PAX+JDBC+0.9.0+Released -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4635) Upgrade Pax JDBC to version 0.9.0
[ https://issues.apache.org/jira/browse/KARAF-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-4635: --- Assignee: Jean-Baptiste Onofré > Upgrade Pax JDBC to version 0.9.0 > - > > Key: KARAF-4635 > URL: https://issues.apache.org/jira/browse/KARAF-4635 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Lukas Roedl >Assignee: Jean-Baptiste Onofré >Priority: Minor > > some time ago Pax JDBC 0.9.0 was released. Changelog can be found at > https://ops4j1.jira.com/wiki/display/PAXJDBC/2016/06/23/PAX+JDBC+0.9.0+Released -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4616) Upgrade to Felix SCR 2.0.4, SCR Compat 1.0.4, SCR Annotations 1.11.0
[ https://issues.apache.org/jira/browse/KARAF-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4616: Summary: Upgrade to Felix SCR 2.0.4, SCR Compat 1.0.4, SCR Annotations 1.11.0 (was: Upgrade to Felix SCR 2.0.4, SCR Compat 1.0.4) > Upgrade to Felix SCR 2.0.4, SCR Compat 1.0.4, SCR Annotations 1.11.0 > > > Key: KARAF-4616 > URL: https://issues.apache.org/jira/browse/KARAF-4616 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4616) Upgrade to Felix SCR 2.0.4, SCR Compat 1.0.4
[ https://issues.apache.org/jira/browse/KARAF-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4616: Summary: Upgrade to Felix SCR 2.0.4, SCR Compat 1.0.4 (was: Upgrade to Felix SCR 2.0.4) > Upgrade to Felix SCR 2.0.4, SCR Compat 1.0.4 > > > Key: KARAF-4616 > URL: https://issues.apache.org/jira/browse/KARAF-4616 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4616) Upgrade to Felix SCR 2.0.4, SCR Compat 1.0.4
[ https://issues.apache.org/jira/browse/KARAF-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4616 started by Jean-Baptiste Onofré. --- > Upgrade to Felix SCR 2.0.4, SCR Compat 1.0.4 > > > Key: KARAF-4616 > URL: https://issues.apache.org/jira/browse/KARAF-4616 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4648) Feature service-wrapper creates invalid SERVICENAME-wrapper.conf file
[
https://issues.apache.org/jira/browse/KARAF-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-4648:
---
Assignee: Jean-Baptiste Onofré
> Feature service-wrapper creates invalid SERVICENAME-wrapper.conf file
> -
>
> Key: KARAF-4648
> URL: https://issues.apache.org/jira/browse/KARAF-4648
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.5
> Environment: Windows KARAF_BASE defined to be outside of KARAF_HOME
> hierarchy.
>Reporter: Scott Leschke
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>
> Note: KARAF_BASE is defined to be outside the KARAF_HOME hierarchy.
> After installing service-wrapper, ran wrapper:install command per the docs.
> That worked fine. When we tried to start the service though it failed. Upon
> review, I saw that the {service-name}-wrapper.conf file had the following
> lines in it. This file is created under KARAF_BASE/etc.
>
> wrapper.java.classpath.2=%KARAF_HOME%/lib/wrapper/*.jar
> wrapper.java.library.path.1=%KARAF_HOME%/lib/wrapper/
> Replacing KARAF_HOME with KARAF_BASE as shown below allowed the service to
> start.
>
> wrapper.java.classpath.2=%KARAF_BASE%/lib/wrapper/*.jar
> wrapper.java.library.path.1=%KARAF_BASE%/lib/wrapper/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4648) Feature service-wrapper creates invalid SERVICENAME-wrapper.conf file
[
https://issues.apache.org/jira/browse/KARAF-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4648:
Fix Version/s: 4.0.6
4.1.0
> Feature service-wrapper creates invalid SERVICENAME-wrapper.conf file
> -
>
> Key: KARAF-4648
> URL: https://issues.apache.org/jira/browse/KARAF-4648
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.5
> Environment: Windows KARAF_BASE defined to be outside of KARAF_HOME
> hierarchy.
>Reporter: Scott Leschke
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>
> Note: KARAF_BASE is defined to be outside the KARAF_HOME hierarchy.
> After installing service-wrapper, ran wrapper:install command per the docs.
> That worked fine. When we tried to start the service though it failed. Upon
> review, I saw that the {service-name}-wrapper.conf file had the following
> lines in it. This file is created under KARAF_BASE/etc.
>
> wrapper.java.classpath.2=%KARAF_HOME%/lib/wrapper/*.jar
> wrapper.java.library.path.1=%KARAF_HOME%/lib/wrapper/
> Replacing KARAF_HOME with KARAF_BASE as shown below allowed the service to
> start.
>
> wrapper.java.classpath.2=%KARAF_BASE%/lib/wrapper/*.jar
> wrapper.java.library.path.1=%KARAF_BASE%/lib/wrapper/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
[ https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4649. - Resolution: Fixed > AssemblyMojo : blacklistPolicy set to null if not defined in pom > > > Key: KARAF-4649 > URL: https://issues.apache.org/jira/browse/KARAF-4649 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > > In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo > sets the policy the assembly Builder should use, it is not explicit > configured in the pom, it sets it to null overriding the default value > defined by Builder. > The effect is that if you do not set the policy in pom, the blacklisted > bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
[ https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412355#comment-15412355 ] ASF subversion and git services commented on KARAF-4649: Commit e4c8b2cfdfb2593b0d78a9700c86f36151603264 in karaf's branch refs/heads/karaf-4.0.x from [~lb] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=e4c8b2c ] [KARAF-4649] In the AssemblyMojo, set blacklistPolicy to null if not defined in pom > AssemblyMojo : blacklistPolicy set to null if not defined in pom > > > Key: KARAF-4649 > URL: https://issues.apache.org/jira/browse/KARAF-4649 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > > In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo > sets the policy the assembly Builder should use, it is not explicit > configured in the pom, it sets it to null overriding the default value > defined by Builder. > The effect is that if you do not set the policy in pom, the blacklisted > bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
[ https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412310#comment-15412310 ] ASF GitHub Bot commented on KARAF-4649: --- Github user asfgit closed the pull request at: https://github.com/apache/karaf/pull/225 > AssemblyMojo : blacklistPolicy set to null if not defined in pom > > > Key: KARAF-4649 > URL: https://issues.apache.org/jira/browse/KARAF-4649 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > > In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo > sets the policy the assembly Builder should use, it is not explicit > configured in the pom, it sets it to null overriding the default value > defined by Builder. > The effect is that if you do not set the policy in pom, the blacklisted > bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
[ https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412308#comment-15412308 ] ASF subversion and git services commented on KARAF-4649: Commit 120bbb5e37de94453eff7c062c462faf00ca1137 in karaf's branch refs/heads/master from [~lb] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=120bbb5 ] [KARAF-4649] In the AssemblyMojo, set blacklistPolicy to null if not defined in pom > AssemblyMojo : blacklistPolicy set to null if not defined in pom > > > Key: KARAF-4649 > URL: https://issues.apache.org/jira/browse/KARAF-4649 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > > In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo > sets the policy the assembly Builder should use, it is not explicit > configured in the pom, it sets it to null overriding the default value > defined by Builder. > The effect is that if you do not set the policy in pom, the blacklisted > bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
[ https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412309#comment-15412309 ] ASF subversion and git services commented on KARAF-4649: Commit 065fb489cedca8e6f1ad616c76437351f0c228e9 in karaf's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=065fb48 ] [KARAF-4649] This closes #225 > AssemblyMojo : blacklistPolicy set to null if not defined in pom > > > Key: KARAF-4649 > URL: https://issues.apache.org/jira/browse/KARAF-4649 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > > In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo > sets the policy the assembly Builder should use, it is not explicit > configured in the pom, it sets it to null overriding the default value > defined by Builder. > The effect is that if you do not set the policy in pom, the blacklisted > bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
[ https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4649: Fix Version/s: 4.0.6 4.1.0 > AssemblyMojo : blacklistPolicy set to null if not defined in pom > > > Key: KARAF-4649 > URL: https://issues.apache.org/jira/browse/KARAF-4649 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > > In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo > sets the policy the assembly Builder should use, it is not explicit > configured in the pom, it sets it to null overriding the default value > defined by Builder. > The effect is that if you do not set the policy in pom, the blacklisted > bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
[ https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411897#comment-15411897 ] Jean-Baptiste Onofré commented on KARAF-4649: - I discussed with Luca on IRC about it. > AssemblyMojo : blacklistPolicy set to null if not defined in pom > > > Key: KARAF-4649 > URL: https://issues.apache.org/jira/browse/KARAF-4649 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Luca Burgazzoli >Assignee: Christian Schneider > > In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo > sets the policy the assembly Builder should use, it is not explicit > configured in the pom, it sets it to null overriding the default value > defined by Builder. > The effect is that if you do not set the policy in pom, the blacklisted > bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
[ https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-4649: --- Assignee: Jean-Baptiste Onofré (was: Christian Schneider) > AssemblyMojo : blacklistPolicy set to null if not defined in pom > > > Key: KARAF-4649 > URL: https://issues.apache.org/jira/browse/KARAF-4649 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré > > In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo > sets the policy the assembly Builder should use, it is not explicit > configured in the pom, it sets it to null overriding the default value > defined by Builder. > The effect is that if you do not set the policy in pom, the blacklisted > bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
[ https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider reassigned KARAF-4649: -- Assignee: Christian Schneider > AssemblyMojo : blacklistPolicy set to null if not defined in pom > > > Key: KARAF-4649 > URL: https://issues.apache.org/jira/browse/KARAF-4649 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Luca Burgazzoli >Assignee: Christian Schneider > > In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo > sets the policy the assembly Builder should use, it is not explicit > configured in the pom, it sets it to null overriding the default value > defined by Builder. > The effect is that if you do not set the policy in pom, the blacklisted > bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
[ https://issues.apache.org/jira/browse/KARAF-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411647#comment-15411647 ] ASF GitHub Bot commented on KARAF-4649: --- GitHub user lburgazzoli opened a pull request: https://github.com/apache/karaf/pull/225 KARAF-4649: AssemblyMojo : blacklistPolicy set to null if not defined in pom You can merge this pull request into a Git repository by running: $ git pull https://github.com/lburgazzoli/apache-karaf KARAF-4649 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/karaf/pull/225.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 #225 commit 066a4e2ee696726372f327402c6b9f19b1ef36e5 Author: lburgazzoli Date: 2016-08-08T10:45:22Z KARAF-4649: AssemblyMojo : blacklistPolicy set to null if not defined in pom > AssemblyMojo : blacklistPolicy set to null if not defined in pom > > > Key: KARAF-4649 > URL: https://issues.apache.org/jira/browse/KARAF-4649 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Reporter: Luca Burgazzoli > > In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo > sets the policy the assembly Builder should use, it is not explicit > configured in the pom, it sets it to null overriding the default value > defined by Builder. > The effect is that if you do not set the policy in pom, the blacklisted > bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
Luca Burgazzoli created KARAF-4649: -- Summary: AssemblyMojo : blacklistPolicy set to null if not defined in pom Key: KARAF-4649 URL: https://issues.apache.org/jira/browse/KARAF-4649 Project: Karaf Issue Type: Bug Components: karaf-tooling Reporter: Luca Burgazzoli In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo sets the policy the assembly Builder should use, it is not explicit configured in the pom, it sets it to null overriding the default value defined by Builder. The effect is that if you do not set the policy in pom, the blacklisted bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
