[jira] [Updated] (KARAF-4172) Karaf must be restarted for pax-jdbc see driver adapters

2015-12-08 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet updated KARAF-4172:
---
Fix Version/s: (was: 4.0.4)

> Karaf must be restarted for pax-jdbc see driver adapters
> 
>
> Key: KARAF-4172
> URL: https://issues.apache.org/jira/browse/KARAF-4172
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-jdbc
>Affects Versions: 4.0.3
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Assignee: Guillaume Nodet
>Priority: Blocker
>
> I made some tests with DataSourceFactory being visible by pax-jdbc. Here is 
> the results:
> Karaf must be restarted for pax-jdbc see my adapters. It doesn't matter i 
> install my adapters after Karaf restart or before. It doesn't matter how I 
> register my services via blueprint or by activator. I install my adapters via 
> bundle:install mvn: wrap command.
> When I install build-in pax-jdbc adapter features everything works fine.
> How to reproduce:
> 1. build simple driver adapter: http://www.lorien.biz/karaf/test2.zip
> 2. run clear Karaf 4.0.3
> 3. run script (please, do not modify, run as is):
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2/0.7.0;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> bundle:install -s mvn:org.postgresql/postgresql/9.4-1200-jdbc41;
> bundle:install -s mvn:postgres/test2;
> 4. type ds-factories
> you will see empty list
> 5. type service:list DataSourceFactory
> you will see some factories registered
> 6. restart karaf and type ds-factories
> you will see factories appeared
> It is strange but 0.7.0 marked as unreleased version here in Jira.



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

[jira] [Created] (KARAF-4180) Document overrides configuration

2015-12-08 Thread Christian Schneider (JIRA) 
Christian Schneider created KARAF-4180:
--

 Summary: Document overrides configuration
 Key: KARAF-4180
 URL: https://issues.apache.org/jira/browse/KARAF-4180
 Project: Karaf
  Issue Type: Documentation
  Components: karaf-feature
Affects Versions: 4.0.3
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: 4.0.4






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

[jira] [Commented] (KARAF-4173) Uses constraint violation when installing activemq feature

2015-12-08 Thread Christian Schneider (JIRA) 

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

Christian Schneider commented on KARAF-4173:


I was not able to reproduce in some runes with the original commands. I now 
added the activemq-broker feature and was able to reproduce again.
It does not seem to happen every time. 

I was able to get the exception quite reliably when repeatedly calling:
feature:install activemq-broker activemq-blueprint

So it might be an ordering issue

> Uses constraint violation when installing activemq feature
> --
>
> Key: KARAF-4173
> URL: https://issues.apache.org/jira/browse/KARAF-4173
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Christian Schneider
> Fix For: 4.0.4
>
>
> When installing thre activemq-blueprint feature there sometimes is a strange 
> uses constraint violation. 
> I think this should not cause an exceptions as both chains start and end in 
> the same bundle.
> {code}
> karaf@root()> feature:repo-add activemq 5.13.0
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.13.0/xml/features
> karaf@root()> feature:install activemq-broker activemq-blueprint
> Error executing command: Uses constraint violation. Unable to resolve 
> resource org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.13.0] because it is exposed to 
> package 'org.apache.aries.blueprint' from resources 
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5] and 
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5] via 
> two dependency chains.
> Chain 1:
>   org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.13.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.5]
> Chain 2:
>   org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.13.0]
> import: 
> (&(osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version>=3.13.0)(!(version>=5.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.5]
> {code}



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

[jira] [Created] (KARAF-4181) blacklist.properties is not a properties file

2015-12-08 Thread Benson Margulies (JIRA) 
Benson Margulies created KARAF-4181:
---

 Summary: blacklist.properties is not a properties file
 Key: KARAF-4181
 URL: https://issues.apache.org/jira/browse/KARAF-4181
 Project: Karaf
  Issue Type: Bug
Reporter: Benson Margulies


It's confusing that a file named 'blacklist.properties' does not, in fact, 
contain a properties file. Rather, it's just a list of blacklisted bundles. It 
seems to me that the name 'blacklist.properties' might be deprecated and the 
name 'bundle-blacklist.txt' would be more informative.




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

[jira] [Resolved] (KARAF-4172) Karaf must be restarted for pax-jdbc see driver adapters

2015-12-08 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet resolved KARAF-4172.

Resolution: Not A Problem
  Assignee: Guillaume Nodet

> Karaf must be restarted for pax-jdbc see driver adapters
> 
>
> Key: KARAF-4172
> URL: https://issues.apache.org/jira/browse/KARAF-4172
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-jdbc
>Affects Versions: 4.0.3
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Assignee: Guillaume Nodet
>Priority: Blocker
> Fix For: 4.0.4
>
>
> I made some tests with DataSourceFactory being visible by pax-jdbc. Here is 
> the results:
> Karaf must be restarted for pax-jdbc see my adapters. It doesn't matter i 
> install my adapters after Karaf restart or before. It doesn't matter how I 
> register my services via blueprint or by activator. I install my adapters via 
> bundle:install mvn: wrap command.
> When I install build-in pax-jdbc adapter features everything works fine.
> How to reproduce:
> 1. build simple driver adapter: http://www.lorien.biz/karaf/test2.zip
> 2. run clear Karaf 4.0.3
> 3. run script (please, do not modify, run as is):
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2/0.7.0;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> bundle:install -s mvn:org.postgresql/postgresql/9.4-1200-jdbc41;
> bundle:install -s mvn:postgres/test2;
> 4. type ds-factories
> you will see empty list
> 5. type service:list DataSourceFactory
> you will see some factories registered
> 6. restart karaf and type ds-factories
> you will see factories appeared
> It is strange but 0.7.0 marked as unreleased version here in Jira.



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

[jira] [Comment Edited] (KARAF-4173) Uses constraint violation when installing activemq feature

2015-12-08 Thread Christian Schneider (JIRA) 

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

Christian Schneider edited comment on KARAF-4173 at 12/8/15 12:58 PM:
--

I was not able to reproduce in some runs with the original commands.

I was able to get the exception quite reliably when repeatedly calling:
feature:install activemq-broker activemq-blueprint

So it might be an ordering issue


was (Author: ch...@die-schneider.net):
I was not able to reproduce in some runes with the original commands. I now 
added the activemq-broker feature and was able to reproduce again.
It does not seem to happen every time. 

I was able to get the exception quite reliably when repeatedly calling:
feature:install activemq-broker activemq-blueprint

So it might be an ordering issue

> Uses constraint violation when installing activemq feature
> --
>
> Key: KARAF-4173
> URL: https://issues.apache.org/jira/browse/KARAF-4173
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Christian Schneider
> Fix For: 4.0.4
>
>
> When installing thre activemq-blueprint feature there sometimes is a strange 
> uses constraint violation. 
> I think this should not cause an exceptions as both chains start and end in 
> the same bundle.
> {code}
> karaf@root()> feature:repo-add activemq 5.13.0
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.13.0/xml/features
> karaf@root()> feature:install activemq-broker activemq-blueprint
> Error executing command: Uses constraint violation. Unable to resolve 
> resource org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.13.0] because it is exposed to 
> package 'org.apache.aries.blueprint' from resources 
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5] and 
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5] via 
> two dependency chains.
> Chain 1:
>   org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.13.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.5]
> Chain 2:
>   org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.13.0]
> import: 
> (&(osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version>=3.13.0)(!(version>=5.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.5]
> {code}



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

[jira] [Commented] (KARAF-4172) Karaf must be restarted for pax-jdbc see driver adapters

2015-12-08 Thread Viktor Kozlov (JIRA) 

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

Viktor Kozlov commented on KARAF-4172:
--

Do you plan dependency upgrade jpa-2.3.0 for karaf-4.0.4?
I wish I could use bundle:install scenario without any problems.

> Karaf must be restarted for pax-jdbc see driver adapters
> 
>
> Key: KARAF-4172
> URL: https://issues.apache.org/jira/browse/KARAF-4172
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-jdbc
>Affects Versions: 4.0.3
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Assignee: Guillaume Nodet
>Priority: Blocker
>
> I made some tests with DataSourceFactory being visible by pax-jdbc. Here is 
> the results:
> Karaf must be restarted for pax-jdbc see my adapters. It doesn't matter i 
> install my adapters after Karaf restart or before. It doesn't matter how I 
> register my services via blueprint or by activator. I install my adapters via 
> bundle:install mvn: wrap command.
> When I install build-in pax-jdbc adapter features everything works fine.
> How to reproduce:
> 1. build simple driver adapter: http://www.lorien.biz/karaf/test2.zip
> 2. run clear Karaf 4.0.3
> 3. run script (please, do not modify, run as is):
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2/0.7.0;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> bundle:install -s mvn:org.postgresql/postgresql/9.4-1200-jdbc41;
> bundle:install -s mvn:postgres/test2;
> 4. type ds-factories
> you will see empty list
> 5. type service:list DataSourceFactory
> you will see some factories registered
> 6. restart karaf and type ds-factories
> you will see factories appeared
> It is strange but 0.7.0 marked as unreleased version here in Jira.



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

[jira] [Commented] (KARAF-4172) Karaf must be restarted for pax-jdbc see driver adapters

2015-12-08 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet commented on KARAF-4172:


You can use bundle:install, but you need to refresh all the bundles to make 
sure the wiring is correct.
It would be easier to use the deployer though, as you would not need 8 commands 
to deploy your application.

Fwiw, refreshing all bundles can be done calling {{bundle:refresh .*}} after 
the installation.

> Karaf must be restarted for pax-jdbc see driver adapters
> 
>
> Key: KARAF-4172
> URL: https://issues.apache.org/jira/browse/KARAF-4172
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-jdbc
>Affects Versions: 4.0.3
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Assignee: Guillaume Nodet
>Priority: Blocker
>
> I made some tests with DataSourceFactory being visible by pax-jdbc. Here is 
> the results:
> Karaf must be restarted for pax-jdbc see my adapters. It doesn't matter i 
> install my adapters after Karaf restart or before. It doesn't matter how I 
> register my services via blueprint or by activator. I install my adapters via 
> bundle:install mvn: wrap command.
> When I install build-in pax-jdbc adapter features everything works fine.
> How to reproduce:
> 1. build simple driver adapter: http://www.lorien.biz/karaf/test2.zip
> 2. run clear Karaf 4.0.3
> 3. run script (please, do not modify, run as is):
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2/0.7.0;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> bundle:install -s mvn:org.postgresql/postgresql/9.4-1200-jdbc41;
> bundle:install -s mvn:postgres/test2;
> 4. type ds-factories
> you will see empty list
> 5. type service:list DataSourceFactory
> you will see some factories registered
> 6. restart karaf and type ds-factories
> you will see factories appeared
> It is strange but 0.7.0 marked as unreleased version here in Jira.



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

[jira] [Closed] (KARAF-4172) Karaf must be restarted for pax-jdbc see driver adapters

2015-12-08 Thread Viktor Kozlov (JIRA) 

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

Viktor Kozlov closed KARAF-4172.


> Karaf must be restarted for pax-jdbc see driver adapters
> 
>
> Key: KARAF-4172
> URL: https://issues.apache.org/jira/browse/KARAF-4172
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-jdbc
>Affects Versions: 4.0.3
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Assignee: Guillaume Nodet
>Priority: Blocker
>
> I made some tests with DataSourceFactory being visible by pax-jdbc. Here is 
> the results:
> Karaf must be restarted for pax-jdbc see my adapters. It doesn't matter i 
> install my adapters after Karaf restart or before. It doesn't matter how I 
> register my services via blueprint or by activator. I install my adapters via 
> bundle:install mvn: wrap command.
> When I install build-in pax-jdbc adapter features everything works fine.
> How to reproduce:
> 1. build simple driver adapter: http://www.lorien.biz/karaf/test2.zip
> 2. run clear Karaf 4.0.3
> 3. run script (please, do not modify, run as is):
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2/0.7.0;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> bundle:install -s mvn:org.postgresql/postgresql/9.4-1200-jdbc41;
> bundle:install -s mvn:postgres/test2;
> 4. type ds-factories
> you will see empty list
> 5. type service:list DataSourceFactory
> you will see some factories registered
> 6. restart karaf and type ds-factories
> you will see factories appeared
> It is strange but 0.7.0 marked as unreleased version here in Jira.



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

[jira] [Commented] (KARAF-4172) Karaf must be restarted for pax-jdbc see driver adapters

2015-12-08 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet commented on KARAF-4172:


You should try to deploy the bundles 
{{mvn:org.postgresql/postgresql/9.4-1200-jdbc41}} and {{mvn:postgres/test2}} 
using a feature.
This will solve the problem.
The reason is that you manually install bundles without using the deployer, so 
that the wiring is done according to the OSGi rules, which in this case, is 
valid.  The observed behaviour is caused by the org.osgi.jdbc package being 
exported twice and the two manually installed bundles are wired to the 
incorrect package.

> Karaf must be restarted for pax-jdbc see driver adapters
> 
>
> Key: KARAF-4172
> URL: https://issues.apache.org/jira/browse/KARAF-4172
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-jdbc
>Affects Versions: 4.0.3
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Priority: Blocker
> Fix For: 4.0.4
>
>
> I made some tests with DataSourceFactory being visible by pax-jdbc. Here is 
> the results:
> Karaf must be restarted for pax-jdbc see my adapters. It doesn't matter i 
> install my adapters after Karaf restart or before. It doesn't matter how I 
> register my services via blueprint or by activator. I install my adapters via 
> bundle:install mvn: wrap command.
> When I install build-in pax-jdbc adapter features everything works fine.
> How to reproduce:
> 1. build simple driver adapter: http://www.lorien.biz/karaf/test2.zip
> 2. run clear Karaf 4.0.3
> 3. run script (please, do not modify, run as is):
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2/0.7.0;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> bundle:install -s mvn:org.postgresql/postgresql/9.4-1200-jdbc41;
> bundle:install -s mvn:postgres/test2;
> 4. type ds-factories
> you will see empty list
> 5. type service:list DataSourceFactory
> you will see some factories registered
> 6. restart karaf and type ds-factories
> you will see factories appeared
> It is strange but 0.7.0 marked as unreleased version here in Jira.



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

[jira] [Commented] (KARAF-4172) Karaf must be restarted for pax-jdbc see driver adapters

2015-12-08 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet commented on KARAF-4172:


The package duplication is caused by ARIES-1469.

> Karaf must be restarted for pax-jdbc see driver adapters
> 
>
> Key: KARAF-4172
> URL: https://issues.apache.org/jira/browse/KARAF-4172
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-jdbc
>Affects Versions: 4.0.3
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Priority: Blocker
> Fix For: 4.0.4
>
>
> I made some tests with DataSourceFactory being visible by pax-jdbc. Here is 
> the results:
> Karaf must be restarted for pax-jdbc see my adapters. It doesn't matter i 
> install my adapters after Karaf restart or before. It doesn't matter how I 
> register my services via blueprint or by activator. I install my adapters via 
> bundle:install mvn: wrap command.
> When I install build-in pax-jdbc adapter features everything works fine.
> How to reproduce:
> 1. build simple driver adapter: http://www.lorien.biz/karaf/test2.zip
> 2. run clear Karaf 4.0.3
> 3. run script (please, do not modify, run as is):
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2/0.7.0;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> bundle:install -s mvn:org.postgresql/postgresql/9.4-1200-jdbc41;
> bundle:install -s mvn:postgres/test2;
> 4. type ds-factories
> you will see empty list
> 5. type service:list DataSourceFactory
> you will see some factories registered
> 6. restart karaf and type ds-factories
> you will see factories appeared
> It is strange but 0.7.0 marked as unreleased version here in Jira.



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

[jira] [Updated] (KARAF-4173) Uses constraint violation when installing activemq feature

2015-12-08 Thread Christian Schneider (JIRA) 

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

Christian Schneider updated KARAF-4173:
---
Description: 
When installing thre activemq-blueprint feature there sometimes is a strange 
uses constraint violation. 
I think this should not cause an exceptions as both chains start and end in the 
same bundle.

{code}
karaf@root()> feature:repo-add activemq 5.13.0
Adding feature url mvn:org.apache.activemq/activemq-karaf/5.13.0/xml/features
karaf@root()> feature:install activemq-broker activemq-blueprint
Error executing command: Uses constraint violation. Unable to resolve resource 
org.apache.activemq.activemq-blueprint 
[org.apache.activemq.activemq-blueprint/5.13.0] because it is exposed to 
package 'org.apache.aries.blueprint' from resources 
org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5] and 
org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5] via two 
dependency chains.

Chain 1:
  org.apache.activemq.activemq-blueprint 
[org.apache.activemq.activemq-blueprint/5.13.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.5]

Chain 2:
  org.apache.activemq.activemq-blueprint 
[org.apache.activemq.activemq-blueprint/5.13.0]
import: 
(&(osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version>=3.13.0)(!(version>=5.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.5]
{code}

  was:
When installing thre activemq-blueprint feature there sometimes is a strange 
uses constraint violation. 
I think this should not cause an exceptions as both chains start and end in the 
same bundle.

{code}
karaf@root()> feature:repo-add activemq 5.13.0
Adding feature url mvn:org.apache.activemq/activemq-karaf/5.13.0/xml/features
karaf@root()> feature:install activemq-blueprint
Error executing command: Uses constraint violation. Unable to resolve resource 
org.apache.activemq.activemq-blueprint 
[org.apache.activemq.activemq-blueprint/5.13.0] because it is exposed to 
package 'org.apache.aries.blueprint' from resources 
org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5] and 
org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5] via two 
dependency chains.

Chain 1:
  org.apache.activemq.activemq-blueprint 
[org.apache.activemq.activemq-blueprint/5.13.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.5]

Chain 2:
  org.apache.activemq.activemq-blueprint 
[org.apache.activemq.activemq-blueprint/5.13.0]
import: 
(&(osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version>=3.13.0)(!(version>=5.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.5]
{code}


> Uses constraint violation when installing activemq feature
> --
>
> Key: KARAF-4173
> URL: https://issues.apache.org/jira/browse/KARAF-4173
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Christian Schneider
> Fix For: 4.0.4
>
>
> When installing thre activemq-blueprint feature there sometimes is a strange 
> uses constraint violation. 
> I think this should not cause an exceptions as both chains start and end in 
> the same bundle.
> {code}
> karaf@root()> feature:repo-add activemq 5.13.0
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.13.0/xml/features
> karaf@root()> feature:install activemq-broker activemq-blueprint
> Error executing command: Uses constraint violation. Unable to resolve 
> resource org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.13.0] because it is exposed to 
> package 'org.apache.aries.blueprint' from resources 
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5]

[jira] [Updated] (KARAF-4172) Karaf must be restarted for pax-jdbc see driver adapters

2015-12-08 Thread Viktor Kozlov (JIRA) 

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

Viktor Kozlov updated KARAF-4172:
-
Fix Version/s: 4.0.4

> Karaf must be restarted for pax-jdbc see driver adapters
> 
>
> Key: KARAF-4172
> URL: https://issues.apache.org/jira/browse/KARAF-4172
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-jdbc
>Affects Versions: 4.0.3
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Priority: Blocker
> Fix For: 4.0.4
>
>
> I made some tests with DataSourceFactory being visible by pax-jdbc. Here is 
> the results:
> Karaf must be restarted for pax-jdbc see my adapters. It doesn't matter i 
> install my adapters after Karaf restart or before. It doesn't matter how I 
> register my services via blueprint or by activator. I install my adapters via 
> bundle:install mvn: wrap command.
> When I install build-in pax-jdbc adapter features everything works fine.
> How to reproduce:
> 1. build simple driver adapter: http://www.lorien.biz/karaf/test2.zip
> 2. run clear Karaf 4.0.3
> 3. run script (please, do not modify, run as is):
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2/0.7.0;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> bundle:install -s mvn:org.postgresql/postgresql/9.4-1200-jdbc41;
> bundle:install -s mvn:postgres/test2;
> 4. type ds-factories
> you will see empty list
> 5. type service:list DataSourceFactory
> you will see some factories registered
> 6. restart karaf and type ds-factories
> you will see factories appeared
> It is strange but 0.7.0 marked as unreleased version here in Jira.



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

[jira] [Commented] (KARAF-4172) Karaf must be restarted for pax-jdbc see driver adapters

2015-12-08 Thread Viktor Kozlov (JIRA) 

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

Viktor Kozlov commented on KARAF-4172:
--

Thanks for work-around. Closed.

> Karaf must be restarted for pax-jdbc see driver adapters
> 
>
> Key: KARAF-4172
> URL: https://issues.apache.org/jira/browse/KARAF-4172
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-jdbc
>Affects Versions: 4.0.3
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Assignee: Guillaume Nodet
>Priority: Blocker
>
> I made some tests with DataSourceFactory being visible by pax-jdbc. Here is 
> the results:
> Karaf must be restarted for pax-jdbc see my adapters. It doesn't matter i 
> install my adapters after Karaf restart or before. It doesn't matter how I 
> register my services via blueprint or by activator. I install my adapters via 
> bundle:install mvn: wrap command.
> When I install build-in pax-jdbc adapter features everything works fine.
> How to reproduce:
> 1. build simple driver adapter: http://www.lorien.biz/karaf/test2.zip
> 2. run clear Karaf 4.0.3
> 3. run script (please, do not modify, run as is):
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2/0.7.0;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> bundle:install -s mvn:org.postgresql/postgresql/9.4-1200-jdbc41;
> bundle:install -s mvn:postgres/test2;
> 4. type ds-factories
> you will see empty list
> 5. type service:list DataSourceFactory
> you will see some factories registered
> 6. restart karaf and type ds-factories
> you will see factories appeared
> It is strange but 0.7.0 marked as unreleased version here in Jira.



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

[jira] [Commented] (KARAF-4173) Uses constraint violation when installing activemq feature

2015-12-08 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet commented on KARAF-4173:


I can't really reproduce the issue ... Any hint ?

> Uses constraint violation when installing activemq feature
> --
>
> Key: KARAF-4173
> URL: https://issues.apache.org/jira/browse/KARAF-4173
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Christian Schneider
> Fix For: 4.0.4
>
>
> When installing thre activemq-blueprint feature there sometimes is a strange 
> uses constraint violation. 
> I think this should not cause an exceptions as both chains start and end in 
> the same bundle.
> {code}
> karaf@root()> feature:repo-add activemq 5.13.0
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.13.0/xml/features
> karaf@root()> feature:install activemq-blueprint
> Error executing command: Uses constraint violation. Unable to resolve 
> resource org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.13.0] because it is exposed to 
> package 'org.apache.aries.blueprint' from resources 
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5] and 
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.5] via 
> two dependency chains.
> Chain 1:
>   org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.13.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.5]
> Chain 2:
>   org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.13.0]
> import: 
> (&(osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version>=3.13.0)(!(version>=5.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.5]
> {code}



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

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

2015-12-08 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet commented on KARAF-4167:


The ConfigAdmin implementation is in full control of this area.

> 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-3918) An installed blueprint.xml has always been updated and restarted when install another unrelated feature

2015-12-08 Thread JIRA 

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

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

For the blueprint deployer, let me try to remove the DynamicImport-Package and 
test it. For now, I don't change the Spring deployer (waiting the Aries Spring 
support).

> An installed blueprint.xml has always been updated and restarted when install 
> another unrelated feature
> ---
>
> Key: KARAF-3918
> URL: https://issues.apache.org/jira/browse/KARAF-3918
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.0
> Environment: Java 7
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
>
> There is an installed blueprint.xml. (by install -s 
> blueprint:mvn:org.abc/my-project/1.0-SNAPSHOT/xml, or deploy this 
> blueprint.xml into deploy folder).
> then, if you do feature:install , to install some other feature (no 
> dependencies to the blueprint.xml above), the installed blueprint.xml will 
> always be updated and restarted, that's not expected behavious.
> After checking with org.apache.karaf.features.internal.service.Deployer 
> class, I found that the old checksum will only be calculated in case of url 
> start with "jar:" (Line 1159), so in case of the url start with "blueprint:", 
> the new checksum will never equal with old checksum, then it will be put into 
> deployment.toUpdate Map.
> The Deployer class should be fixed for "blueprint:" deployment.



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

[jira] [Commented] (KARAF-4181) blacklist.properties is not a properties file

2015-12-08 Thread JIRA 

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

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

I guess you talk the bundle blacklist file used by the Builder.

You are right that it's not a pure "properties" file as it contains bundle 
blacklist like, for instance:

{code}
spring;range="[2,3)"
{code}

For backward compatible, I will add the bundle-blacklist.txt filename format, 
and raise a warn message when using blacklist.properties.

> blacklist.properties is not a properties file
> -
>
> Key: KARAF-4181
> URL: https://issues.apache.org/jira/browse/KARAF-4181
> Project: Karaf
>  Issue Type: Bug
>Reporter: Benson Margulies
>
> It's confusing that a file named 'blacklist.properties' does not, in fact, 
> contain a properties file. Rather, it's just a list of blacklisted bundles. 
> It seems to me that the name 'blacklist.properties' might be deprecated and 
> the name 'bundle-blacklist.txt' would be more informative.



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

[jira] [Updated] (KARAF-4181) blacklist.properties is not a properties file

2015-12-08 Thread JIRA 

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

Jean-Baptiste Onofré updated KARAF-4181:

Affects Version/s: 4.0.3

> blacklist.properties is not a properties file
> -
>
> Key: KARAF-4181
> URL: https://issues.apache.org/jira/browse/KARAF-4181
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-profile
>Affects Versions: 4.0.3
>Reporter: Benson Margulies
>Assignee: Jean-Baptiste Onofré
>
> It's confusing that a file named 'blacklist.properties' does not, in fact, 
> contain a properties file. Rather, it's just a list of blacklisted bundles. 
> It seems to me that the name 'blacklist.properties' might be deprecated and 
> the name 'bundle-blacklist.txt' would be more informative.



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

[jira] [Updated] (KARAF-4181) blacklist.properties is not a properties file

2015-12-08 Thread JIRA 

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

Jean-Baptiste Onofré updated KARAF-4181:

Component/s: karaf-profile

> blacklist.properties is not a properties file
> -
>
> Key: KARAF-4181
> URL: https://issues.apache.org/jira/browse/KARAF-4181
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-profile
>Affects Versions: 4.0.3
>Reporter: Benson Margulies
>Assignee: Jean-Baptiste Onofré
>
> It's confusing that a file named 'blacklist.properties' does not, in fact, 
> contain a properties file. Rather, it's just a list of blacklisted bundles. 
> It seems to me that the name 'blacklist.properties' might be deprecated and 
> the name 'bundle-blacklist.txt' would be more informative.



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

[jira] [Assigned] (KARAF-4181) blacklist.properties is not a properties file

2015-12-08 Thread JIRA 

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

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

Assignee: Jean-Baptiste Onofré

> blacklist.properties is not a properties file
> -
>
> Key: KARAF-4181
> URL: https://issues.apache.org/jira/browse/KARAF-4181
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-profile
>Affects Versions: 4.0.3
>Reporter: Benson Margulies
>Assignee: Jean-Baptiste Onofré
>
> It's confusing that a file named 'blacklist.properties' does not, in fact, 
> contain a properties file. Rather, it's just a list of blacklisted bundles. 
> It seems to me that the name 'blacklist.properties' might be deprecated and 
> the name 'bundle-blacklist.txt' would be more informative.



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

[jira] [Updated] (KARAF-3918) An installed blueprint.xml has always been updated and restarted when install another unrelated feature

2015-12-08 Thread JIRA 

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

Jean-Baptiste Onofré updated KARAF-3918:

Fix Version/s: 4.0.4

> An installed blueprint.xml has always been updated and restarted when install 
> another unrelated feature
> ---
>
> Key: KARAF-3918
> URL: https://issues.apache.org/jira/browse/KARAF-3918
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.0
> Environment: Java 7
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> There is an installed blueprint.xml. (by install -s 
> blueprint:mvn:org.abc/my-project/1.0-SNAPSHOT/xml, or deploy this 
> blueprint.xml into deploy folder).
> then, if you do feature:install , to install some other feature (no 
> dependencies to the blueprint.xml above), the installed blueprint.xml will 
> always be updated and restarted, that's not expected behavious.
> After checking with org.apache.karaf.features.internal.service.Deployer 
> class, I found that the old checksum will only be calculated in case of url 
> start with "jar:" (Line 1159), so in case of the url start with "blueprint:", 
> the new checksum will never equal with old checksum, then it will be put into 
> deployment.toUpdate Map.
> The Deployer class should be fixed for "blueprint:" deployment.



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

[jira] [Commented] (KARAF-3918) An installed blueprint.xml has always been updated and restarted when install another unrelated feature

2015-12-08 Thread JIRA 

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

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

Unfortunately, DynamicImport-Package header is required, for instance when 
using namespace like jasypt enc.

I'm trying another hack.

> An installed blueprint.xml has always been updated and restarted when install 
> another unrelated feature
> ---
>
> Key: KARAF-3918
> URL: https://issues.apache.org/jira/browse/KARAF-3918
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.0
> Environment: Java 7
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> There is an installed blueprint.xml. (by install -s 
> blueprint:mvn:org.abc/my-project/1.0-SNAPSHOT/xml, or deploy this 
> blueprint.xml into deploy folder).
> then, if you do feature:install , to install some other feature (no 
> dependencies to the blueprint.xml above), the installed blueprint.xml will 
> always be updated and restarted, that's not expected behavious.
> After checking with org.apache.karaf.features.internal.service.Deployer 
> class, I found that the old checksum will only be calculated in case of url 
> start with "jar:" (Line 1159), so in case of the url start with "blueprint:", 
> the new checksum will never equal with old checksum, then it will be put into 
> deployment.toUpdate Map.
> The Deployer class should be fixed for "blueprint:" deployment.



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

[jira] [Commented] (KARAF-3918) An installed blueprint.xml has always been updated and restarted when install another unrelated feature

2015-12-08 Thread JIRA 

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

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

Basically, the DynamicImport-Private header is not the cause of the refresh. I 
removed this header in the BlueprintTransformer and the bundle is refreshed 
anyway (whatever the feature I install):

{code}
karaf@root()> bundle:headers 52

Bundle 52
-
Manifest-Version = 2

Bundle-ManifestVersion = 2
Bundle-SymbolicName = test.xml
Bundle-UpdateLocation = blueprint:file:/home/jbonofre/test.xml
Bundle-Version = 0.0.0

Import-Package = 
org.apache.karaf.features

karaf@root()> feature:install -v jndi
...
karaf@root()> feature:install -v jndi
The specified feature: 'jndi' version '4.0.4.SNAPSHOT' is already installed
Adding features: jndi/[4.0.4.SNAPSHOT,4.0.4.SNAPSHOT]
Changes to perform:
  Region: root
Bundles to update:
  test.xml/0.0.0 with blueprint:file:/home/jbonofre/test.xml
Stopping bundles:
  test.xml/0.0.0
Updating bundles:
  blueprint:file:/home/jbonofre/test.xml
Stopping bundles:
  test.xml/0.0.0
Refreshing bundles:
test.xml/0.0.0 (Bundle will be updated)
Starting bundles:
  test.xml/0.0.0
Done.
karaf@root()> feature:install jdbc
...
Stopping bundles:
  test.xml/0.0.0
Refreshing bundles:
test.xml/0.0.0 (Bundle will be updated)
...
{code}

The problem is in the feature Deployer: the computeDeployment() method is not 
fully correct when dealing with blueprint XML directly. I'm fixing that.

> An installed blueprint.xml has always been updated and restarted when install 
> another unrelated feature
> ---
>
> Key: KARAF-3918
> URL: https://issues.apache.org/jira/browse/KARAF-3918
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.0
> Environment: Java 7
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> There is an installed blueprint.xml. (by install -s 
> blueprint:mvn:org.abc/my-project/1.0-SNAPSHOT/xml, or deploy this 
> blueprint.xml into deploy folder).
> then, if you do feature:install , to install some other feature (no 
> dependencies to the blueprint.xml above), the installed blueprint.xml will 
> always be updated and restarted, that's not expected behavious.
> After checking with org.apache.karaf.features.internal.service.Deployer 
> class, I found that the old checksum will only be calculated in case of url 
> start with "jar:" (Line 1159), so in case of the url start with "blueprint:", 
> the new checksum will never equal with old checksum, then it will be put into 
> deployment.toUpdate Map.
> The Deployer class should be fixed for "blueprint:" deployment.



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

[jira] [Commented] (KARAF-3918) An installed blueprint.xml has always been updated and restarted when install another unrelated feature

2015-12-08 Thread JIRA 

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

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

OK, I can reproduce the problem, and actually, the original description is not 
correct. When the blueprint is deployed outside of a feature, it works fine. 
The blueprint is always refreshed when part of a features XML. I'm trying to 
find a workaround (probably easier as the behaviour is narrowed now ;)).

> An installed blueprint.xml has always been updated and restarted when install 
> another unrelated feature
> ---
>
> Key: KARAF-3918
> URL: https://issues.apache.org/jira/browse/KARAF-3918
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.0
> Environment: Java 7
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> There is an installed blueprint.xml. (by install -s 
> blueprint:mvn:org.abc/my-project/1.0-SNAPSHOT/xml, or deploy this 
> blueprint.xml into deploy folder).
> then, if you do feature:install , to install some other feature (no 
> dependencies to the blueprint.xml above), the installed blueprint.xml will 
> always be updated and restarted, that's not expected behavious.
> After checking with org.apache.karaf.features.internal.service.Deployer 
> class, I found that the old checksum will only be calculated in case of url 
> start with "jar:" (Line 1159), so in case of the url start with "blueprint:", 
> the new checksum will never equal with old checksum, then it will be put into 
> deployment.toUpdate Map.
> The Deployer class should be fixed for "blueprint:" deployment.



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

[jira] [Commented] (KARAF-4182) Upgrade to Spring 4.2.3.RELEASE

2015-12-08 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino commented on KARAF-4182:
-

I'll provide PR for this.

> Upgrade to Spring 4.2.3.RELEASE
> ---
>
> Key: KARAF-4182
> URL: https://issues.apache.org/jira/browse/KARAF-4182
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Andrea Cosentino
> Fix For: 4.1.0, 4.0.4
>
>




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

[jira] [Created] (KARAF-4182) Upgrade to Spring 4.2.3.RELEASE

2015-12-08 Thread Andrea Cosentino (JIRA) 
Andrea Cosentino created KARAF-4182:
---

 Summary: Upgrade to Spring 4.2.3.RELEASE
 Key: KARAF-4182
 URL: https://issues.apache.org/jira/browse/KARAF-4182
 Project: Karaf
  Issue Type: Dependency upgrade
  Components: karaf-core
Reporter: Andrea Cosentino
 Fix For: 4.1.0, 4.0.4






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

[jira] [Commented] (KARAF-4182) Upgrade to Spring 4.2.3.RELEASE

2015-12-08 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino commented on KARAF-4182:
-

PR submitted:
https://github.com/apache/karaf/pull/115

> Upgrade to Spring 4.2.3.RELEASE
> ---
>
> Key: KARAF-4182
> URL: https://issues.apache.org/jira/browse/KARAF-4182
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Andrea Cosentino
> Fix For: 4.1.0, 4.0.4
>
>




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

[jira] [Commented] (KARAF-4182) Upgrade to Spring 4.2.3.RELEASE

2015-12-08 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user oscerd opened a pull request:

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

[KARAF-4182] Upgrade to Spring 4.2.3.RELEASE

Hi all,

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

Andrea

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

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

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

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


commit ff1dba474f189c0bec603338bab4b88fb6dc8172
Author: Andrea Cosentino 
Date:   2015-12-09T07:50:15Z

[KARAF-4182] Upgrade to Spring 4.2.3.RELEASE




> Upgrade to Spring 4.2.3.RELEASE
> ---
>
> Key: KARAF-4182
> URL: https://issues.apache.org/jira/browse/KARAF-4182
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Andrea Cosentino
> Fix For: 4.1.0, 4.0.4
>
>




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