[jira] [Commented] (KARAF-1972) karaf-maven-plugin should respect scope

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/23


> karaf-maven-plugin should respect scope
> ---
>
> Key: KARAF-1972
> URL: https://issues.apache.org/jira/browse/KARAF-1972
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 3.0.0.RC1
>Reporter: Andrei Pozolotin
>Assignee: Jean-Baptiste Onofré
> Attachments: 0001-Fixing-the-scope-handling.patch, KARAF-1972.patch
>
>
> PROBLEM:
> currently, in project with dependencies such as these:
> {code}
>   
>   org.osgi
>   org.osgi.core
>   provided
>   
>   
>   org.osgi
>   org.osgi.compendium
>   provided
>   
> {code}
> karaf-maven-plugin with invocation like this:
> {code}
>   
>   
>   
>   org.apache.karaf.tooling
>   karaf-maven-plugin
>   3.0.0-SNAPSHOT
>   
>   
>   generate-descriptor
>   package
>   
>   
> features-generate-descriptor
>   
>   
>   
> auto
>   
> 90
>   
> ./target/${project.artifactId}-${project.version}-features.xml
>   
>   
>   
>   
>   
>   
> {code}
> will produce features.xml with entries:
> {code}
> mvn:org.osgi/org.osgi.core/4.3.0
>  start-level="90">mvn:org.osgi/org.osgi.compendium/4.2.0
> {code}
> which is not as expected. scope==provided should not show up there.
> SOLUTION:
> instead, karaf-maven-plugin should respect scope;
> I suggest to add karaf-maven-plugin config parameters such as:
> {code}
> 
>compile
> 
> {code}
> or
> {code}
> 
>provided
>runtime
>test
> 
> {code}
> IMPACT:
> current plugin behavior forces to create a separate maven
> project to generate features.xml, since scope==provided
> is in fact excluded from transitive dependencies in that case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-1972) karaf-maven-plugin should respect scope

[JIRA]

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

Jean-Baptiste Onofré resolved KARAF-1972.
-
Resolution: Won't Fix

> karaf-maven-plugin should respect scope
> ---
>
> Key: KARAF-1972
> URL: https://issues.apache.org/jira/browse/KARAF-1972
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 3.0.0.RC1
>Reporter: Andrei Pozolotin
>Assignee: Jean-Baptiste Onofré
> Attachments: 0001-Fixing-the-scope-handling.patch, KARAF-1972.patch
>
>
> PROBLEM:
> currently, in project with dependencies such as these:
> {code}
>   
>   org.osgi
>   org.osgi.core
>   provided
>   
>   
>   org.osgi
>   org.osgi.compendium
>   provided
>   
> {code}
> karaf-maven-plugin with invocation like this:
> {code}
>   
>   
>   
>   org.apache.karaf.tooling
>   karaf-maven-plugin
>   3.0.0-SNAPSHOT
>   
>   
>   generate-descriptor
>   package
>   
>   
> features-generate-descriptor
>   
>   
>   
> auto
>   
> 90
>   
> ./target/${project.artifactId}-${project.version}-features.xml
>   
>   
>   
>   
>   
>   
> {code}
> will produce features.xml with entries:
> {code}
> mvn:org.osgi/org.osgi.core/4.3.0
>  start-level="90">mvn:org.osgi/org.osgi.compendium/4.2.0
> {code}
> which is not as expected. scope==provided should not show up there.
> SOLUTION:
> instead, karaf-maven-plugin should respect scope;
> I suggest to add karaf-maven-plugin config parameters such as:
> {code}
> 
>compile
> 
> {code}
> or
> {code}
> 
>provided
>runtime
>test
> 
> {code}
> IMPACT:
> current plugin behavior forces to create a separate maven
> project to generate features.xml, since scope==provided
> is in fact excluded from transitive dependencies in that case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4152) Resolution of relative URLs from OBR repositories not working when there are multiple URLs

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet resolved KARAF-4152.

   Resolution: Fixed
 Assignee: Guillaume Nodet  (was: Jean-Baptiste Onofré)
Fix Version/s: 4.0.4

https://github.com/apache/karaf/commit/f2c944a4eb784ad1dabdeaae25274d1c90f8684c

> Resolution of relative URLs from OBR repositories not working when there are 
> multiple URLs
> --
>
> Key: KARAF-4152
> URL: https://issues.apache.org/jira/browse/KARAF-4152
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Reporter: David Leangen
>Assignee: Guillaume Nodet
> Fix For: 4.0.4
>
>
> The fix in [KARAF-4142] only worked for a single repository.
> In the same mindset, I will submit a patch, but for multiple repositories.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3100) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin

[JIRA]

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

Jean-Baptiste Onofré updated KARAF-3100:

Fix Version/s: 4.0.4
   3.0.6

> Add Option To Create Config Files For Feature Configs Instead Of Importing 
> Directly Into Config Admin
> -
>
> Key: KARAF-3100
> URL: https://issues.apache.org/jira/browse/KARAF-3100
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Affects Versions: 3.0.1
>Reporter: Gareth Collins
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> I have created a pull request for this here:
> https://github.com/apache/karaf/pull/43
> As the title says, this allows karaf to be configured to output feature 
> configurations to config file...which I believe are easier to manage. Let me 
> know what you think. If it looks OK, would it be possible to merge soon (e.g. 
> karaf 3.0.2 :))? The changes are very localized.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4166) Add karaf.lock.exclusive property to prevent a slave instance to start

[JIRA]

Jean-Baptiste Onofré created KARAF-4166:
---

 Summary: Add karaf.lock.exclusive property to prevent a slave 
instance to start
 Key: KARAF-4166
 URL: https://issues.apache.org/jira/browse/KARAF-4166
 Project: Karaf
  Issue Type: Improvement
  Components: karaf-core
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
 Fix For: 3.0.6, 4.0.4


By default, a Karaf slave instance starts to be able to "pre-install" bundle 
there.

We can enhance the SimpleLockFile (controled a karaf.lock.exclusive property) 
like this:

{code}
boolean lock() throws Exception {
 boolean locked = super.lock();
 if (!locked) throw new RuntimeException("startup aborted");
 return true;
}
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4162) Wrap deployer does not add default versions to exported packages

[Aleksei Lissitsin (JIRA)]

Aleksei Lissitsin created KARAF-4162:


 Summary: Wrap deployer does not add default versions to exported 
packages
 Key: KARAF-4162
 URL: https://issues.apache.org/jira/browse/KARAF-4162
 Project: Karaf
  Issue Type: Bug
  Components: karaf-feature
Affects Versions: 4.0.3
Reporter: Aleksei Lissitsin


Wrap deployer does not add default versions to exported packages but should. 
Try, e.g., with the provided spring-beans jar.

My attempts to override this behaviour by using bundle:install with wrap url 
containing '-nodefaultversion=false' failed too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-2951) Transitive repositories and bundles are not added to system repo

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/42


> Transitive repositories and bundles are not added to system repo
> 
>
> Key: KARAF-2951
> URL: https://issues.apache.org/jira/browse/KARAF-2951
> Project: Karaf
>  Issue Type: Bug
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.0.0.M3
>
> Attachments: KARAF-2951-2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-2186) bunde:scanner (new command)

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/12


> bunde:scanner (new command)
> ---
>
> Key: KARAF-2186
> URL: https://issues.apache.org/jira/browse/KARAF-2186
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Reporter: Andrei Pozolotin
>
> bunde:scanner (new command)
> {code}
> @Command( //
> scope = "bundle", //
> name = "scanner", //
> description = "Scans and updates snapshot bundles.", //
> detailedDescription = "Scans installed snapshot bundles, updates them from 
> remote maven repository, and re-deploys changed jars in karaf.")
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4161) Adding requirement does not resolve required bundles

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet commented on KARAF-4161:


Some problems have been fixed by 
https://github.com/apache/karaf/commit/f9279d98983f18076f8d43b9d2d6cf792401b1e6.
Could you see if you still experience the mentioned problems ?

> Adding requirement does not resolve required bundles
> 
>
> Key: KARAF-4161
> URL: https://issues.apache.org/jira/browse/KARAF-4161
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Reporter: David Leangen
>Assignee: Guillaume Nodet
>
> When using
> {code}
> feature:requirement-add 
> ‘requirement:osgi.identity;osgi.identity=my.bundle;type=osgi.bundle'
> {code}
> required bundles are not getting resolved, even if they exist in an installed 
> repository. This seems to occur when the required bundle is available from a 
> different repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (KARAF-3100) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin

[JIRA]

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

Work on KARAF-3100 started by Jean-Baptiste Onofré.
---
> Add Option To Create Config Files For Feature Configs Instead Of Importing 
> Directly Into Config Admin
> -
>
> Key: KARAF-3100
> URL: https://issues.apache.org/jira/browse/KARAF-3100
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Affects Versions: 3.0.1
>Reporter: Gareth Collins
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> I have created a pull request for this here:
> https://github.com/apache/karaf/pull/43
> As the title says, this allows karaf to be configured to output feature 
> configurations to config file...which I believe are easier to manage. Let me 
> know what you think. If it looks OK, would it be possible to merge soon (e.g. 
> karaf 3.0.2 :))? The changes are very localized.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4165) Upgrade Felix Webconsole to version 4.2.14

[Andrea Cosentino (JIRA)]

Andrea Cosentino created KARAF-4165:
---

 Summary: Upgrade Felix Webconsole to version 4.2.14
 Key: KARAF-4165
 URL: https://issues.apache.org/jira/browse/KARAF-4165
 Project: Karaf
  Issue Type: Dependency upgrade
  Components: cellar-core
Reporter: Andrea Cosentino
Priority: Minor
 Fix For: cellar-4.0.1






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4162) Wrap deployer does not add default versions to exported packages

[Aleksei Lissitsin (JIRA)]

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

Aleksei Lissitsin updated KARAF-4162:
-
Attachment: spring-beans-4.1.7.RELEASE.jar

> Wrap deployer does not add default versions to exported packages
> 
>
> Key: KARAF-4162
> URL: https://issues.apache.org/jira/browse/KARAF-4162
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Aleksei Lissitsin
> Attachments: spring-beans-4.1.7.RELEASE.jar
>
>
> Wrap deployer does not add default versions to exported packages but should. 
> Try, e.g., with the provided spring-beans jar.
> My attempts to override this behaviour by using bundle:install with wrap url 
> containing '-nodefaultversion=false' failed too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4165) Upgrade Felix Webconsole to version 4.2.14

[JIRA]

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

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

Assignee: Jean-Baptiste Onofré

> Upgrade Felix Webconsole to version 4.2.14
> --
>
> Key: KARAF-4165
> URL: https://issues.apache.org/jira/browse/KARAF-4165
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4165) Upgrade Felix Webconsole to version 4.2.14

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on KARAF-4165:
-

I'll provide PR for this.

> Upgrade Felix Webconsole to version 4.2.14
> --
>
> Key: KARAF-4165
> URL: https://issues.apache.org/jira/browse/KARAF-4165
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4164) Upgrade Felix Bundle Repository to version 2.0.6

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on KARAF-4164:
-

I'll provide PR for this.

> Upgrade Felix Bundle Repository to version 2.0.6
> 
>
> Key: KARAF-4164
> URL: https://issues.apache.org/jira/browse/KARAF-4164
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4164) Upgrade Felix Bundle Repository to version 2.0.6

[JIRA]

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

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

Assignee: Jean-Baptiste Onofré

> Upgrade Felix Bundle Repository to version 2.0.6
> 
>
> Key: KARAF-4164
> URL: https://issues.apache.org/jira/browse/KARAF-4164
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4163) Upgrade Joda-time to version 2.9.1

[JIRA]

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

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

Assignee: Jean-Baptiste Onofré

> Upgrade Joda-time to version 2.9.1
> --
>
> Key: KARAF-4163
> URL: https://issues.apache.org/jira/browse/KARAF-4163
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4162) Wrap deployer does not add default versions to exported packages

[Aleksei Lissitsin (JIRA)]

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

Aleksei Lissitsin updated KARAF-4162:
-
Attachment: export-package-expected.txt
export-package-actual.txt

Adding expected and actual export-package section.

> Wrap deployer does not add default versions to exported packages
> 
>
> Key: KARAF-4162
> URL: https://issues.apache.org/jira/browse/KARAF-4162
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Aleksei Lissitsin
> Attachments: export-package-actual.txt, export-package-expected.txt, 
> spring-beans-4.1.7.RELEASE.jar
>
>
> Wrap deployer does not add default versions to exported packages but should. 
> Try, e.g., with the provided spring-beans jar.
> My attempts to override this behaviour by using bundle:install with wrap url 
> containing '-nodefaultversion=false' failed too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4130) Use OSGi Resource repositories in features XML

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet commented on KARAF-4130:


Committed with 
https://github.com/apache/karaf/commit/f9279d98983f18076f8d43b9d2d6cf792401b1e6

> Use OSGi Resource repositories in features XML
> --
>
> Key: KARAF-4130
> URL: https://issues.apache.org/jira/browse/KARAF-4130
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> It would be great to support OBR index.xml directly in features XML.
> I propose a two steps support:
> 1. add a  or  element in features XML to be able to load a 
> resource repository (index.xml, a bit like we do in resourceRepositories in 
> etc/org.apache.karaf.features.cfg)
> 2. "extend" the  element to support the artifacts name (symbolicName 
> and version range)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4130) Use OSGi Resource repositories in features XML

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet resolved KARAF-4130.

   Resolution: Fixed
 Assignee: Guillaume Nodet  (was: Jean-Baptiste Onofré)
Fix Version/s: 4.0.4

> Use OSGi Resource repositories in features XML
> --
>
> Key: KARAF-4130
> URL: https://issues.apache.org/jira/browse/KARAF-4130
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Reporter: Jean-Baptiste Onofré
>Assignee: Guillaume Nodet
> Fix For: 4.0.4
>
>
> It would be great to support OBR index.xml directly in features XML.
> I propose a two steps support:
> 1. add a  or  element in features XML to be able to load a 
> resource repository (index.xml, a bit like we do in resourceRepositories in 
> etc/org.apache.karaf.features.cfg)
> 2. "extend" the  element to support the artifacts name (symbolicName 
> and version range)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4163) Upgrade Joda-time to version 2.9.1

[Andrea Cosentino (JIRA)]

Andrea Cosentino created KARAF-4163:
---

 Summary: Upgrade Joda-time to version 2.9.1
 Key: KARAF-4163
 URL: https://issues.apache.org/jira/browse/KARAF-4163
 Project: Karaf
  Issue Type: Dependency upgrade
  Components: cellar-core
Reporter: Andrea Cosentino
Priority: Minor
 Fix For: cellar-4.0.1






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4164) Upgrade Felix Bundle Repository to version 2.0.6

[Andrea Cosentino (JIRA)]

Andrea Cosentino created KARAF-4164:
---

 Summary: Upgrade Felix Bundle Repository to version 2.0.6
 Key: KARAF-4164
 URL: https://issues.apache.org/jira/browse/KARAF-4164
 Project: Karaf
  Issue Type: Dependency upgrade
  Components: cellar-core
Reporter: Andrea Cosentino
Priority: Minor
 Fix For: cellar-4.0.1






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4163) Upgrade Joda-time to version 2.9.1

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on KARAF-4163:
-

I'll provide PR for this.

> Upgrade Joda-time to version 2.9.1
> --
>
> Key: KARAF-4163
> URL: https://issues.apache.org/jira/browse/KARAF-4163
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4164) Upgrade Felix Bundle Repository to version 2.0.6

[ASF GitHub Bot (JIRA)]

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

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

GitHub user oscerd opened a pull request:

https://github.com/apache/karaf-cellar/pull/19

[KARAF-4164] Upgrade Felix Bundle Repository to version 2.0.6

Hi all,

This PR is related to:
https://issues.apache.org/jira/browse/KARAF-4164

Andrea

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/oscerd/karaf-cellar KARAF-4164

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf-cellar/pull/19.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 #19


commit 4a2a0a7839e697a2aa701c621e2225add05b6e1d
Author: Andrea Cosentino 
Date:   2015-12-02T16:37:01Z

[KARAF-4164] Upgrade Felix Bundle Repository to version 2.0.6




> Upgrade Felix Bundle Repository to version 2.0.6
> 
>
> Key: KARAF-4164
> URL: https://issues.apache.org/jira/browse/KARAF-4164
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4163) Upgrade Joda-time to version 2.9.1

[ASF GitHub Bot (JIRA)]

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

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

GitHub user oscerd opened a pull request:

https://github.com/apache/karaf-cellar/pull/18

[KARAF-4163] Upgrade Joda-time to version 2.9.1

Hi all,

This PR is related to:
https://issues.apache.org/jira/browse/KARAF-4163

Andrea

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/oscerd/karaf-cellar KARAF-4163

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf-cellar/pull/18.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 #18


commit 8cbab37750afa26462cbb3d9ec536bd7ffc4534a
Author: Andrea Cosentino 
Date:   2015-12-02T16:35:24Z

[KARAF-4163] Upgrade Joda-time to version 2.9.1




> Upgrade Joda-time to version 2.9.1
> --
>
> Key: KARAF-4163
> URL: https://issues.apache.org/jira/browse/KARAF-4163
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4165) Upgrade Felix Webconsole to version 4.2.14

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on KARAF-4165:
-

PR submitted:
https://github.com/apache/karaf-cellar/pull/20

> Upgrade Felix Webconsole to version 4.2.14
> --
>
> Key: KARAF-4165
> URL: https://issues.apache.org/jira/browse/KARAF-4165
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4165) Upgrade Felix Webconsole to version 4.2.14

[ASF GitHub Bot (JIRA)]

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

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

GitHub user oscerd opened a pull request:

https://github.com/apache/karaf-cellar/pull/20

[KARAF-4165] Upgrade Felix Webconsole to version 4.2.14

Hi all,

This PR is related to:
https://issues.apache.org/jira/browse/KARAF-4165

Andrea

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/oscerd/karaf-cellar KARAF-4165

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf-cellar/pull/20.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 #20


commit 51ec0db1189337a803f492884054150189a7d35b
Author: Andrea Cosentino 
Date:   2015-12-02T16:38:50Z

[KARAF-4165] Upgrade Felix Webconsole to version 4.2.14




> Upgrade Felix Webconsole to version 4.2.14
> --
>
> Key: KARAF-4165
> URL: https://issues.apache.org/jira/browse/KARAF-4165
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4164) Upgrade Felix Bundle Repository to version 2.0.6

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on KARAF-4164:
-

PR submitted:
https://github.com/apache/karaf-cellar/pull/19

> Upgrade Felix Bundle Repository to version 2.0.6
> 
>
> Key: KARAF-4164
> URL: https://issues.apache.org/jira/browse/KARAF-4164
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4163) Upgrade Joda-time to version 2.9.1

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on KARAF-4163:
-

PR submitted:
https://github.com/apache/karaf-cellar/pull/18

> Upgrade Joda-time to version 2.9.1
> --
>
> Key: KARAF-4163
> URL: https://issues.apache.org/jira/browse/KARAF-4163
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4167) Accidently shared config files diagnosed

[Benson Margulies (JIRA)]

Benson Margulies created KARAF-4167:
---

 Summary: Accidently shared config files diagnosed
 Key: KARAF-4167
 URL: https://issues.apache.org/jira/browse/KARAF-4167
 Project: Karaf
  Issue Type: Improvement
Reporter: Benson Margulies


If you stupidly tell two different @Components to use the same 
configurationPid, one of them will just get stuck, and neither bundle:services 
nor any of the scr commands will reveal what the problem is. It sure would be 
nice to have a log message, or some detail from one of the commands.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4167) Accidently shared config files diagnosed

[JIRA]

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

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

You are right: it's BAD to use the same PID for two @Components (or generally 
speaking for ManagedService). And you are right, at least a log message would 
be helpful. Let me take a look as I'm not sure it's only Karaf related.

> Accidently shared config files diagnosed
> 
>
> Key: KARAF-4167
> URL: https://issues.apache.org/jira/browse/KARAF-4167
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Benson Margulies
>
> If you stupidly tell two different @Components to use the same 
> configurationPid, one of them will just get stuck, and neither 
> bundle:services nor any of the scr commands will reveal what the problem is. 
> It sure would be nice to have a log message, or some detail from one of the 
> commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4062) Karaf client does now work after installing BouncyCastle

[Wojciech Oczkowski (JIRA)]

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

Wojciech Oczkowski commented on KARAF-4062:
---

same problem in 2.4.3 any chance to patch this one too?

> Karaf client does now work after installing BouncyCastle
> 
>
> Key: KARAF-4062
> URL: https://issues.apache.org/jira/browse/KARAF-4062
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.2
> Environment: OS X, Windows
>Reporter: Pavlo Vasylchenko
>Assignee: Freeman Fang
> Fix For: 4.0.3, 3.0.6
>
>
> Karaf client throws:
> " Exception caught
> java.security.InvalidAlgorithmParameterException: Prime size must be multiple 
> of 64, and can only ra
> nge from 512 to 2048 (inclusive)
> at 
> com.sun.crypto.provider.DHKeyPairGenerator.initialize(DHKeyPairGenerator.java:120)"
> after installing mvn:org.bouncycastle/bcprov-jdk15on/1.52 into container



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4160) Allow for the "feature wrapping" of a bundle

[David Leangen (JIRA)]

David Leangen created KARAF-4160:


 Summary: Allow for the "feature wrapping" of a bundle
 Key: KARAF-4160
 URL: https://issues.apache.org/jira/browse/KARAF-4160
 Project: Karaf
  Issue Type: Improvement
Reporter: David Leangen


In the OSGi capability/requirement model, if a bundle declares all of its 
dependencies, then it could be considered to be very similar to a feature.

It would be very nice to be able to wrap such a bundle during runtime in order 
to generate features "on the fly". Currently, Karaf requires that a feature be 
described statically in a features.xml file, and further that related 
repositories already be declared at startup, so this type of dynamic feature 
generation is currently not possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4160) Allow for the "feature wrapping" of a bundle

[David Leangen (JIRA)]

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

David Leangen updated KARAF-4160:
-
Component/s: karaf-feature

> Allow for the "feature wrapping" of a bundle
> 
>
> Key: KARAF-4160
> URL: https://issues.apache.org/jira/browse/KARAF-4160
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Reporter: David Leangen
>
> In the OSGi capability/requirement model, if a bundle declares all of its 
> dependencies, then it could be considered to be very similar to a feature.
> It would be very nice to be able to wrap such a bundle during runtime in 
> order to generate features "on the fly". Currently, Karaf requires that a 
> feature be described statically in a features.xml file, and further that 
> related repositories already be declared at startup, so this type of dynamic 
> feature generation is currently not possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (KARAF-4062) Karaf client does now work after installing BouncyCastle

[Wojciech Oczkowski (JIRA)]

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

Wojciech Oczkowski edited comment on KARAF-4062 at 12/2/15 9:23 AM:


same problem in 2.4.3 any chance to patch this one too?

Workaround for now is:
setting "org.apache.sshd.registerBouncyCastle" system property to false


was (Author: oczkins):
same problem in 2.4.3 any chance to patch this one too?

Workaround for now is setting org.apache.sshd.registerBouncyCastle system 
property to false

> Karaf client does now work after installing BouncyCastle
> 
>
> Key: KARAF-4062
> URL: https://issues.apache.org/jira/browse/KARAF-4062
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.2
> Environment: OS X, Windows
>Reporter: Pavlo Vasylchenko
>Assignee: Freeman Fang
> Fix For: 4.0.3, 3.0.6
>
>
> Karaf client throws:
> " Exception caught
> java.security.InvalidAlgorithmParameterException: Prime size must be multiple 
> of 64, and can only ra
> nge from 512 to 2048 (inclusive)
> at 
> com.sun.crypto.provider.DHKeyPairGenerator.initialize(DHKeyPairGenerator.java:120)"
> after installing mvn:org.bouncycastle/bcprov-jdk15on/1.52 into container



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4160) Allow for the "feature wrapping" of a bundle

[David Leangen (JIRA)]

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

David Leangen commented on KARAF-4160:
--

I have created a [sample bndtools (enRoute) 
workspace|https://github.com/dleangen/org.apache.karaf.demos.enroute] on github:

Although quite simplistic, hopefully it is representative of what happens in a 
typical enRoute workspace. The workspace gets released as a unit in the form of 
an OBR. To me, this “unit” is clearly homologous to a Karaf Feature, or at 
least very synergetic. The objective is in fact to take the released OBR, which 
is plain and simple OSGi, and transform it into a Feature on the fly.

The “driver” or “application” bundle is 
org.apache.karaf.demos.enroute.application. The EnrouteApplication class pulls 
in all the required dependencies. The mechanism is to annotate the class, and 
bndtools uses the information in the annotations to write the requirements in 
the manifest. All Karaf would need to do is wrap this bundle, and in theory all 
the requirements (if available) should get resolved.

I’m still grappling a bit with what to do about configurations with regards to 
features, but FYI I also included a simple configuration in the "enRoute Way” 
as well. You can see this in the “unrelated” bundle, which also happens to get 
pulled into the “application”. (I am not advocating that this _should_ be the 
right or only way to pull in a dependency or a configuration, just showing that 
it _can_ be done, and is very easy to do.)

Once the code was ready, I performed a “release”, which creates an OBR. This is 
saved in the cnf/release directory, which I also committed to the same project 
in github. If you look at the index.xml file, you will notice that the 
application bundle indeed provides the following capability:

{code:title=index.xml snippet|borderStyle=solid}
   
 
 
 
 
   
{code}

As you can probably imagine, it would be very easy to write a parser to scan 
for this “feature” and create one in runtime. In fact, I already created a 
parser (was very easy to do indeed), but got blocked because currently Karaf 
won’t let me use this info to create a Feature in runtime, as it expects an xml 
file instead.

Barring any suggested improvements, then, it seems to me that the only things 
to decide on to make this nice process work are:

 # Whether or not the namespace etc. should be standardised in Karaf
 # If so, what this standardisation should be, and create a corresponding parser
 # How to get a feature working in runtime without requiring the use of a 
features.xml file

Please let me know if I can provide any more information. Hopefully this gives 
a better idea of what could be done. :-)

> Allow for the "feature wrapping" of a bundle
> 
>
> Key: KARAF-4160
> URL: https://issues.apache.org/jira/browse/KARAF-4160
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Reporter: David Leangen
>
> In the OSGi capability/requirement model, if a bundle declares all of its 
> dependencies, then it could be considered to be very similar to a feature.
> It would be very nice to be able to wrap such a bundle during runtime in 
> order to generate features "on the fly". Currently, Karaf requires that a 
> feature be described statically in a features.xml file, and further that 
> related repositories already be declared at startup, so this type of dynamic 
> feature generation is currently not possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (KARAF-4062) Karaf client does now work after installing BouncyCastle

[Wojciech Oczkowski (JIRA)]

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

Wojciech Oczkowski edited comment on KARAF-4062 at 12/2/15 9:23 AM:


same problem in 2.4.3 any chance to patch this one too?

Workaround for now is setting org.apache.sshd.registerBouncyCastle system 
property to false


was (Author: oczkins):
same problem in 2.4.3 any chance to patch this one too?

> Karaf client does now work after installing BouncyCastle
> 
>
> Key: KARAF-4062
> URL: https://issues.apache.org/jira/browse/KARAF-4062
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.2
> Environment: OS X, Windows
>Reporter: Pavlo Vasylchenko
>Assignee: Freeman Fang
> Fix For: 4.0.3, 3.0.6
>
>
> Karaf client throws:
> " Exception caught
> java.security.InvalidAlgorithmParameterException: Prime size must be multiple 
> of 64, and can only ra
> nge from 512 to 2048 (inclusive)
> at 
> com.sun.crypto.provider.DHKeyPairGenerator.initialize(DHKeyPairGenerator.java:120)"
> after installing mvn:org.bouncycastle/bcprov-jdk15on/1.52 into container



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4161) Adding requirement does not resolve required bundles

[David Leangen (JIRA)]

David Leangen created KARAF-4161:


 Summary: Adding requirement does not resolve required bundles
 Key: KARAF-4161
 URL: https://issues.apache.org/jira/browse/KARAF-4161
 Project: Karaf
  Issue Type: Bug
Reporter: David Leangen


When using
{code}
feature:requirement-add 
‘requirement:osgi.identity;osgi.identity=my.bundle;type=osgi.bundle'
{code}

required bundles are not getting resolved, even if they exist in an installed 
repository. This seems to occur when the required bundle is available from a 
different repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (KARAF-4062) Karaf client does now work after installing BouncyCastle

[Freeman Fang (JIRA)]

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

Freeman Fang reopened KARAF-4062:
-

need also address this for 2.4.x

> Karaf client does now work after installing BouncyCastle
> 
>
> Key: KARAF-4062
> URL: https://issues.apache.org/jira/browse/KARAF-4062
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.2
> Environment: OS X, Windows
>Reporter: Pavlo Vasylchenko
>Assignee: Freeman Fang
> Fix For: 4.0.3, 3.0.6
>
>
> Karaf client throws:
> " Exception caught
> java.security.InvalidAlgorithmParameterException: Prime size must be multiple 
> of 64, and can only ra
> nge from 512 to 2048 (inclusive)
> at 
> com.sun.crypto.provider.DHKeyPairGenerator.initialize(DHKeyPairGenerator.java:120)"
> after installing mvn:org.bouncycastle/bcprov-jdk15on/1.52 into container



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4168) Upgrade to Pax Exam 4.7.0

[JIRA]

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

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

https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=597f65091bdcf477d85b541376c510c774d6416d

> Upgrade to Pax Exam 4.7.0
> -
>
> Key: KARAF-4168
> URL: https://issues.apache.org/jira/browse/KARAF-4168
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-test
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4168) Upgrade to Pax Exam 4.7.0

[JIRA]

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

Jean-Baptiste Onofré resolved KARAF-4168.
-
Resolution: Fixed

> Upgrade to Pax Exam 4.7.0
> -
>
> Key: KARAF-4168
> URL: https://issues.apache.org/jira/browse/KARAF-4168
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-test
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4168) Upgrade to Pax Exam 4.7.0

[JIRA]

Jean-Baptiste Onofré created KARAF-4168:
---

 Summary: Upgrade to Pax Exam 4.7.0
 Key: KARAF-4168
 URL: https://issues.apache.org/jira/browse/KARAF-4168
 Project: Karaf
  Issue Type: Dependency upgrade
  Components: karaf-test
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.4






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4062) Karaf client does now work after installing BouncyCastle

[Freeman Fang (JIRA)]

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

Freeman Fang resolved KARAF-4062.
-
   Resolution: Fixed
Fix Version/s: 2.4.4

commit fix
http://git-wip-us.apache.org/repos/asf/karaf/commit/9f2281a6 for karaf-2.x 
branch

> Karaf client does now work after installing BouncyCastle
> 
>
> Key: KARAF-4062
> URL: https://issues.apache.org/jira/browse/KARAF-4062
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.2
> Environment: OS X, Windows
>Reporter: Pavlo Vasylchenko
>Assignee: Freeman Fang
> Fix For: 2.4.4, 3.0.6, 4.0.3
>
>
> Karaf client throws:
> " Exception caught
> java.security.InvalidAlgorithmParameterException: Prime size must be multiple 
> of 64, and can only ra
> nge from 512 to 2048 (inclusive)
> at 
> com.sun.crypto.provider.DHKeyPairGenerator.initialize(DHKeyPairGenerator.java:120)"
> after installing mvn:org.bouncycastle/bcprov-jdk15on/1.52 into container



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4161) Adding requirement does not resolve required bundles

[David Leangen (JIRA)]

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

David Leangen updated KARAF-4161:
-
Component/s: karaf-feature

> Adding requirement does not resolve required bundles
> 
>
> Key: KARAF-4161
> URL: https://issues.apache.org/jira/browse/KARAF-4161
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Reporter: David Leangen
>
> When using
> {code}
> feature:requirement-add 
> ‘requirement:osgi.identity;osgi.identity=my.bundle;type=osgi.bundle'
> {code}
> required bundles are not getting resolved, even if they exist in an installed 
> repository. This seems to occur when the required bundle is available from a 
> different repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3825) Add ability to shutdown Karaf with a disabled shutdown port

[JIRA]

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

Jean-Baptiste Onofré updated KARAF-3825:

Fix Version/s: 4.0.4
   3.0.6

> Add ability to shutdown Karaf with a disabled shutdown port
> ---
>
> Key: KARAF-3825
> URL: https://issues.apache.org/jira/browse/KARAF-3825
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-core
>Affects Versions: 3.0.3, 4.0.0
>Reporter: Dmitry Konstantinov
> Fix For: 3.0.6, 4.0.4
>
>
> Sometimes by security reasons listen ports are asked to disable. It would be 
> nice to provide an alternative way to trigger Karaf shutdown by touching a 
> special file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4161) Adding requirement does not resolve required bundles

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet commented on KARAF-4161:


Why do you mean by "installed repository" ? Did you configure the 
resourceRepositories in etc/org.apache.karaf.feature.cfg file ?
If that's the case, I think I already have a fix, I'll try to commit it asap.

> Adding requirement does not resolve required bundles
> 
>
> Key: KARAF-4161
> URL: https://issues.apache.org/jira/browse/KARAF-4161
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Reporter: David Leangen
>
> When using
> {code}
> feature:requirement-add 
> ‘requirement:osgi.identity;osgi.identity=my.bundle;type=osgi.bundle'
> {code}
> required bundles are not getting resolved, even if they exist in an installed 
> repository. This seems to occur when the required bundle is available from a 
> different repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4161) Adding requirement does not resolve required bundles

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet reassigned KARAF-4161:
--

Assignee: Guillaume Nodet

> Adding requirement does not resolve required bundles
> 
>
> Key: KARAF-4161
> URL: https://issues.apache.org/jira/browse/KARAF-4161
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Reporter: David Leangen
>Assignee: Guillaume Nodet
>
> When using
> {code}
> feature:requirement-add 
> ‘requirement:osgi.identity;osgi.identity=my.bundle;type=osgi.bundle'
> {code}
> required bundles are not getting resolved, even if they exist in an installed 
> repository. This seems to occur when the required bundle is available from a 
> different repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4161) Adding requirement does not resolve required bundles

[David Leangen (JIRA)]

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

David Leangen commented on KARAF-4161:
--

Yes, that is correct.

The resolution problem occurs when there is more than one repository listed in 
resourceRepositories, and the providing bundle is in a different repository 
from the requesting bundle.

> Adding requirement does not resolve required bundles
> 
>
> Key: KARAF-4161
> URL: https://issues.apache.org/jira/browse/KARAF-4161
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Reporter: David Leangen
>Assignee: Guillaume Nodet
>
> When using
> {code}
> feature:requirement-add 
> ‘requirement:osgi.identity;osgi.identity=my.bundle;type=osgi.bundle'
> {code}
> required bundles are not getting resolved, even if they exist in an installed 
> repository. This seems to occur when the required bundle is available from a 
> different repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)