Jenkins build is still unstable: Tamaya-Sandbox-Master #2059

2018-07-10 Thread Apache Jenkins Server 
See

Jenkins build is still unstable: Tamaya-Sandbox-Master » Apache Tamaya Modules - Metamodel #2059

2018-07-10 Thread Apache Jenkins Server 
See

Jenkins build is still unstable: Tamaya-Sandbox-Master #2058

2018-07-10 Thread Apache Jenkins Server 
See

Jenkins build is still unstable: Tamaya-Sandbox-Master » Apache Tamaya Modules - Metamodel #2058

2018-07-10 Thread Apache Jenkins Server 
See

Jenkins build became unstable: Tamaya-Sandbox-Master » Apache Tamaya Modules - Metamodel #2057

2018-07-10 Thread Apache Jenkins Server 
See

Jenkins build became unstable: Tamaya-Sandbox-Master #2057

2018-07-10 Thread Apache Jenkins Server 
See

Jenkins build is back to normal : Tamaya-Sandbox-Master #2056

2018-07-10 Thread Apache Jenkins Server 
See

[jira] [Resolved] (TAMAYA-273) Describe current configuration provider configuration upon Tamaya launch

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch resolved TAMAYA-273.
---
Resolution: Fixed

* Prints out delegate and config once after SPI has been loaded.
 * configjsr based branch already logs config on INFO level, when a new config 
for a classloader has been created.

> Describe current configuration provider configuration upon Tamaya launch
> 
>
> Key: TAMAYA-273
> URL: https://issues.apache.org/jira/browse/TAMAYA-273
> Project: Tamaya
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.3-incubating
>Reporter: Philipp Ottlinger
>Assignee: Anatole Tresch
>Priority: Major
>
> After starting an application that makes use of Tamaya I want to see which 
> configuration providers are activated and in which order they appear. At the 
> moment the output is:
> {code}
> Jun 12, 2017 8:24:05 PM org.apache.tamaya.spi.ServiceContextManager
> loadDefaultServiceProvider
> INFORMATION: Using Service Context of type:
> org.apache.tamaya.core.internal.DefaultServiceContext
> Jun 12, 2017 8:24:05 PM org.apache.tamaya.ConfigurationProvider spi
> {code}
> A possible output (toString() of providers?) could be the ordinal and a short 
> hint how the provider works or what services it offers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-273) Describe current configuration provider configuration upon Tamaya launch

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538757#comment-16538757
 ] 

ASF subversion and git services commented on TAMAYA-273:


Commit 5a130523ab7d3a9d33091b13f62db90ddb8fba5c in incubator-tamaya's branch 
refs/heads/master from [~anatole]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;h=5a13052 ]

TAMAYA-273 Tamaya logs initial setup on startup on info level.


> Describe current configuration provider configuration upon Tamaya launch
> 
>
> Key: TAMAYA-273
> URL: https://issues.apache.org/jira/browse/TAMAYA-273
> Project: Tamaya
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.3-incubating
>Reporter: Philipp Ottlinger
>Assignee: Anatole Tresch
>Priority: Major
>
> After starting an application that makes use of Tamaya I want to see which 
> configuration providers are activated and in which order they appear. At the 
> moment the output is:
> {code}
> Jun 12, 2017 8:24:05 PM org.apache.tamaya.spi.ServiceContextManager
> loadDefaultServiceProvider
> INFORMATION: Using Service Context of type:
> org.apache.tamaya.core.internal.DefaultServiceContext
> Jun 12, 2017 8:24:05 PM org.apache.tamaya.ConfigurationProvider spi
> {code}
> A possible output (toString() of providers?) could be the ordinal and a short 
> hint how the provider works or what services it offers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (TAMAYA-273) Describe current configuration provider configuration upon Tamaya launch

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch reassigned TAMAYA-273:
-

Assignee: Anatole Tresch

> Describe current configuration provider configuration upon Tamaya launch
> 
>
> Key: TAMAYA-273
> URL: https://issues.apache.org/jira/browse/TAMAYA-273
> Project: Tamaya
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.3-incubating
>Reporter: Philipp Ottlinger
>Assignee: Anatole Tresch
>Priority: Major
>
> After starting an application that makes use of Tamaya I want to see which 
> configuration providers are activated and in which order they appear. At the 
> moment the output is:
> {code}
> Jun 12, 2017 8:24:05 PM org.apache.tamaya.spi.ServiceContextManager
> loadDefaultServiceProvider
> INFORMATION: Using Service Context of type:
> org.apache.tamaya.core.internal.DefaultServiceContext
> Jun 12, 2017 8:24:05 PM org.apache.tamaya.ConfigurationProvider spi
> {code}
> A possible output (toString() of providers?) could be the ordinal and a short 
> hint how the provider works or what services it offers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (TAMAYA-304) Service Loading should consider class's class loader

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch resolved TAMAYA-304.
---
Resolution: Fixed
  Assignee: Anatole Tresch

> Service Loading should consider class's class loader
> 
>
> Key: TAMAYA-304
> URL: https://issues.apache.org/jira/browse/TAMAYA-304
> Project: Tamaya
>  Issue Type: Improvement
>Reporter: John D. Ament
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> {{DefaultServiceContext}} only considers the TCCL.  In order to properly load 
> services in Java EE environments, you need to also consider the class's class 
> loader.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (TAMAYA-308) Error in CommonsConfigPropertySource constructor

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch reassigned TAMAYA-308:
-

Assignee: Anatole Tresch

> Error in CommonsConfigPropertySource constructor
> 
>
> Key: TAMAYA-308
> URL: https://issues.apache.org/jira/browse/TAMAYA-308
> Project: Tamaya
>  Issue Type: Bug
>  Components: Sandbox
>Affects Versions: 0.4-incubating
>Reporter: Christian Niehues
>Assignee: Anatole Tresch
>Priority: Major
>
> there is an error in CommonsConfigPropertySource, this.commonsConfig will be 
> null:
> public CommonsConfigPropertySource(String name, Configuration commonsConfig) {
> commonsConfig = Objects.requireNonNull(commonsConfig);
> ...
> }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (TAMAYA-308) Error in CommonsConfigPropertySource constructor

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch resolved TAMAYA-308.
---
Resolution: Fixed

> Error in CommonsConfigPropertySource constructor
> 
>
> Key: TAMAYA-308
> URL: https://issues.apache.org/jira/browse/TAMAYA-308
> Project: Tamaya
>  Issue Type: Bug
>  Components: Sandbox
>Affects Versions: 0.4-incubating
>Reporter: Christian Niehues
>Assignee: Anatole Tresch
>Priority: Major
>
> there is an error in CommonsConfigPropertySource, this.commonsConfig will be 
> null:
> public CommonsConfigPropertySource(String name, Configuration commonsConfig) {
> commonsConfig = Objects.requireNonNull(commonsConfig);
> ...
> }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-308) Error in CommonsConfigPropertySource constructor

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538714#comment-16538714
 ] 

ASF subversion and git services commented on TAMAYA-308:


Commit 71f8928e065573600e97cae9306a7423a88ed06c in incubator-tamaya-sandbox's 
branch refs/heads/configjsr from [~anatole]
[ 
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-sandbox.git;h=71f8928
 ]

TAMAYA-308 Fixed config assignment in constructor.

Signed-off-by: Anatole Tresch 


> Error in CommonsConfigPropertySource constructor
> 
>
> Key: TAMAYA-308
> URL: https://issues.apache.org/jira/browse/TAMAYA-308
> Project: Tamaya
>  Issue Type: Bug
>  Components: Sandbox
>Affects Versions: 0.4-incubating
>Reporter: Christian Niehues
>Priority: Major
>
> there is an error in CommonsConfigPropertySource, this.commonsConfig will be 
> null:
> public CommonsConfigPropertySource(String name, Configuration commonsConfig) {
> commonsConfig = Objects.requireNonNull(commonsConfig);
> ...
> }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-308) Error in CommonsConfigPropertySource constructor

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538713#comment-16538713
 ] 

ASF subversion and git services commented on TAMAYA-308:


Commit 96fc9d5cbd8d4170af2908d8ba88ed5aa19eae22 in incubator-tamaya-sandbox's 
branch refs/heads/master from [~anatole]
[ 
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-sandbox.git;h=96fc9d5
 ]

TAMAYA-308 Fixed config assignment in constructor.


> Error in CommonsConfigPropertySource constructor
> 
>
> Key: TAMAYA-308
> URL: https://issues.apache.org/jira/browse/TAMAYA-308
> Project: Tamaya
>  Issue Type: Bug
>  Components: Sandbox
>Affects Versions: 0.4-incubating
>Reporter: Christian Niehues
>Priority: Major
>
> there is an error in CommonsConfigPropertySource, this.commonsConfig will be 
> null:
> public CommonsConfigPropertySource(String name, Configuration commonsConfig) {
> commonsConfig = Objects.requireNonNull(commonsConfig);
> ...
> }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-305) InstantiationException on EnumConverter when adding default converters

2018-07-10 Thread Anatole Tresch (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538711#comment-16538711
 ] 

Anatole Tresch commented on TAMAYA-305:
---

There was a useless OSGI @Component annotation. Depending on the OSGI 
environment this may lead to trying to add the EnumConverter as service 
component, which fails due to reasons mentioned. Fixed.

> InstantiationException on EnumConverter when adding default converters
> --
>
> Key: TAMAYA-305
> URL: https://issues.apache.org/jira/browse/TAMAYA-305
> Project: Tamaya
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.3-incubating
> Environment: Ubuntu 14.04
> Java 8
> Karaf 4.1.1
>Reporter: Christian Niehues
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> When I try to add the default property converters to the 
> ConfigurationContextBuilder like
> ConfigurationContextBuilder builder = 
> ConfigurationProvider.getConfigurationContextBuilder();
> builder.addDefaultPropertyConverters();
> I get the following error
> 2017-09-21T09:43:42,196 | ERROR | FelixDispatchQueue | core   
>   | 367 - org.apache.tamaya.core - 0.4.0.incubating-201709190608 | 
> FrameworkEvent ERROR - org.apache.tamaya.core
> org.osgi.framework.ServiceException: Service factory returned null. 
> (Component: org.apache.tamaya.core.internal.converters.EnumConverter (16))
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:380)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:247)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350)
>  [?:?]
>   at org.apache.felix.framework.Felix.getService(Felix.java:3720) [?:?]
>   at 
> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:470)
>  [?:?]
>   at 
> org.apache.tamaya.core.internal.OSGIServiceContext.getServices(OSGIServiceContext.java:97)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.getDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:398)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:171)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:51)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
> Checking the EnumConverter this makes sense because of missing default 
> constructor but I can't see how it has been added because it is not a part of 
> the core converters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (TAMAYA-305) InstantiationException on EnumConverter when adding default converters

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch resolved TAMAYA-305.
---
Resolution: Fixed

> InstantiationException on EnumConverter when adding default converters
> --
>
> Key: TAMAYA-305
> URL: https://issues.apache.org/jira/browse/TAMAYA-305
> Project: Tamaya
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.3-incubating
> Environment: Ubuntu 14.04
> Java 8
> Karaf 4.1.1
>Reporter: Christian Niehues
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> When I try to add the default property converters to the 
> ConfigurationContextBuilder like
> ConfigurationContextBuilder builder = 
> ConfigurationProvider.getConfigurationContextBuilder();
> builder.addDefaultPropertyConverters();
> I get the following error
> 2017-09-21T09:43:42,196 | ERROR | FelixDispatchQueue | core   
>   | 367 - org.apache.tamaya.core - 0.4.0.incubating-201709190608 | 
> FrameworkEvent ERROR - org.apache.tamaya.core
> org.osgi.framework.ServiceException: Service factory returned null. 
> (Component: org.apache.tamaya.core.internal.converters.EnumConverter (16))
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:380)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:247)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350)
>  [?:?]
>   at org.apache.felix.framework.Felix.getService(Felix.java:3720) [?:?]
>   at 
> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:470)
>  [?:?]
>   at 
> org.apache.tamaya.core.internal.OSGIServiceContext.getServices(OSGIServiceContext.java:97)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.getDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:398)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:171)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:51)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
> Checking the EnumConverter this makes sense because of missing default 
> constructor but I can't see how it has been added because it is not a part of 
> the core converters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-305) InstantiationException on EnumConverter when adding default converters

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538709#comment-16538709
 ] 

ASF subversion and git services commented on TAMAYA-305:


Commit 94e32c4e098236facb67824addc9ba62d98bc8ed in incubator-tamaya's branch 
refs/heads/configjsr from [~anatole]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;h=94e32c4 ]

TAMAYA-305 Removed useless OSGI component annotation, since enum converters are 
created and registered on the fly by Tamaya.

Signed-off-by: Anatole Tresch 


> InstantiationException on EnumConverter when adding default converters
> --
>
> Key: TAMAYA-305
> URL: https://issues.apache.org/jira/browse/TAMAYA-305
> Project: Tamaya
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.3-incubating
> Environment: Ubuntu 14.04
> Java 8
> Karaf 4.1.1
>Reporter: Christian Niehues
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> When I try to add the default property converters to the 
> ConfigurationContextBuilder like
> ConfigurationContextBuilder builder = 
> ConfigurationProvider.getConfigurationContextBuilder();
> builder.addDefaultPropertyConverters();
> I get the following error
> 2017-09-21T09:43:42,196 | ERROR | FelixDispatchQueue | core   
>   | 367 - org.apache.tamaya.core - 0.4.0.incubating-201709190608 | 
> FrameworkEvent ERROR - org.apache.tamaya.core
> org.osgi.framework.ServiceException: Service factory returned null. 
> (Component: org.apache.tamaya.core.internal.converters.EnumConverter (16))
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:380)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:247)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350)
>  [?:?]
>   at org.apache.felix.framework.Felix.getService(Felix.java:3720) [?:?]
>   at 
> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:470)
>  [?:?]
>   at 
> org.apache.tamaya.core.internal.OSGIServiceContext.getServices(OSGIServiceContext.java:97)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.getDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:398)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:171)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:51)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
> Checking the EnumConverter this makes sense because of missing default 
> constructor but I can't see how it has been added because it is not a part of 
> the core converters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-305) InstantiationException on EnumConverter when adding default converters

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538707#comment-16538707
 ] 

ASF subversion and git services commented on TAMAYA-305:


Commit e1817f2b4230bb3a13e1f99f9c5479a2d0d3ed2b in incubator-tamaya's branch 
refs/heads/master from [~anatole]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;h=e1817f2 ]

TAMAYA-305 Removed useless OSGI component annotation, since enum converters are 
created and registered on the fly by Tamaya.


> InstantiationException on EnumConverter when adding default converters
> --
>
> Key: TAMAYA-305
> URL: https://issues.apache.org/jira/browse/TAMAYA-305
> Project: Tamaya
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.3-incubating
> Environment: Ubuntu 14.04
> Java 8
> Karaf 4.1.1
>Reporter: Christian Niehues
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> When I try to add the default property converters to the 
> ConfigurationContextBuilder like
> ConfigurationContextBuilder builder = 
> ConfigurationProvider.getConfigurationContextBuilder();
> builder.addDefaultPropertyConverters();
> I get the following error
> 2017-09-21T09:43:42,196 | ERROR | FelixDispatchQueue | core   
>   | 367 - org.apache.tamaya.core - 0.4.0.incubating-201709190608 | 
> FrameworkEvent ERROR - org.apache.tamaya.core
> org.osgi.framework.ServiceException: Service factory returned null. 
> (Component: org.apache.tamaya.core.internal.converters.EnumConverter (16))
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:380)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:247)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350)
>  [?:?]
>   at org.apache.felix.framework.Felix.getService(Felix.java:3720) [?:?]
>   at 
> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:470)
>  [?:?]
>   at 
> org.apache.tamaya.core.internal.OSGIServiceContext.getServices(OSGIServiceContext.java:97)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.getDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:398)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:171)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:51)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
> Checking the EnumConverter this makes sense because of missing default 
> constructor but I can't see how it has been added because it is not a part of 
> the core converters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (TAMAYA-305) InstantiationException on EnumConverter when adding default converters

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch reassigned TAMAYA-305:
-

Assignee: Anatole Tresch  (was: Oliver B. Fischer)

> InstantiationException on EnumConverter when adding default converters
> --
>
> Key: TAMAYA-305
> URL: https://issues.apache.org/jira/browse/TAMAYA-305
> Project: Tamaya
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.3-incubating
> Environment: Ubuntu 14.04
> Java 8
> Karaf 4.1.1
>Reporter: Christian Niehues
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> When I try to add the default property converters to the 
> ConfigurationContextBuilder like
> ConfigurationContextBuilder builder = 
> ConfigurationProvider.getConfigurationContextBuilder();
> builder.addDefaultPropertyConverters();
> I get the following error
> 2017-09-21T09:43:42,196 | ERROR | FelixDispatchQueue | core   
>   | 367 - org.apache.tamaya.core - 0.4.0.incubating-201709190608 | 
> FrameworkEvent ERROR - org.apache.tamaya.core
> org.osgi.framework.ServiceException: Service factory returned null. 
> (Component: org.apache.tamaya.core.internal.converters.EnumConverter (16))
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:380)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:247)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350)
>  [?:?]
>   at org.apache.felix.framework.Felix.getService(Felix.java:3720) [?:?]
>   at 
> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:470)
>  [?:?]
>   at 
> org.apache.tamaya.core.internal.OSGIServiceContext.getServices(OSGIServiceContext.java:97)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.getDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:398)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:171)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:51)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
> Checking the EnumConverter this makes sense because of missing default 
> constructor but I can't see how it has been added because it is not a part of 
> the core converters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (TAMAYA-305) InstantiationException on EnumConverter when adding default converters

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch updated TAMAYA-305:
--
Affects Version/s: (was: 0.4-incubating)
   0.3-incubating

> InstantiationException on EnumConverter when adding default converters
> --
>
> Key: TAMAYA-305
> URL: https://issues.apache.org/jira/browse/TAMAYA-305
> Project: Tamaya
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.3-incubating
> Environment: Ubuntu 14.04
> Java 8
> Karaf 4.1.1
>Reporter: Christian Niehues
>Assignee: Oliver B. Fischer
>Priority: Major
> Fix For: 0.4-incubating
>
>
> When I try to add the default property converters to the 
> ConfigurationContextBuilder like
> ConfigurationContextBuilder builder = 
> ConfigurationProvider.getConfigurationContextBuilder();
> builder.addDefaultPropertyConverters();
> I get the following error
> 2017-09-21T09:43:42,196 | ERROR | FelixDispatchQueue | core   
>   | 367 - org.apache.tamaya.core - 0.4.0.incubating-201709190608 | 
> FrameworkEvent ERROR - org.apache.tamaya.core
> org.osgi.framework.ServiceException: Service factory returned null. 
> (Component: org.apache.tamaya.core.internal.converters.EnumConverter (16))
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:380)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:247)
>  [?:?]
>   at 
> org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350)
>  [?:?]
>   at org.apache.felix.framework.Felix.getService(Felix.java:3720) [?:?]
>   at 
> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:470)
>  [?:?]
>   at 
> org.apache.tamaya.core.internal.OSGIServiceContext.getServices(OSGIServiceContext.java:97)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.getDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:398)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:171)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
>   at 
> org.apache.tamaya.core.internal.DefaultConfigurationContextBuilder.addDefaultPropertyConverters(DefaultConfigurationContextBuilder.java:51)
>  [367:org.apache.tamaya.core:0.4.0.incubating-201709190608]
> Checking the EnumConverter this makes sense because of missing default 
> constructor but I can't see how it has been added because it is not a part of 
> the core converters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (TAMAYA-336) Configuration templates do not work with custom configurations

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch resolved TAMAYA-336.
---
Resolution: Fixed

> Configuration templates do not work with custom configurations
> --
>
> Key: TAMAYA-336
> URL: https://issues.apache.org/jira/browse/TAMAYA-336
> Project: Tamaya
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3-incubating
>Reporter: Harald Wellmann
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> h3.  Scenario
> I'm building a configuration template from an interface, passing a custom 
> configuration as a parameter. This configuration differs from the default 
> configuration obtained by {{ConfigurationProvider.getConfiguration()}}.
> {code}
> AppConfiguration appConfig = ConfigurationInjection.getConfigurationInjector()
> .createTemplate(AppConfiguration.class, customConfiguration);
> {code}
> h3. Expected Behaviour
> {{appConfig}} returns values from the {{customConfiguration}}.
> h3. Actual Behaviour
> {{appConfig}} returns values from the default configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (TAMAYA-336) Configuration templates do not work with custom configurations

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch updated TAMAYA-336:
--
Fix Version/s: 0.4-incubating

> Configuration templates do not work with custom configurations
> --
>
> Key: TAMAYA-336
> URL: https://issues.apache.org/jira/browse/TAMAYA-336
> Project: Tamaya
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3-incubating
>Reporter: Harald Wellmann
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> h3.  Scenario
> I'm building a configuration template from an interface, passing a custom 
> configuration as a parameter. This configuration differs from the default 
> configuration obtained by {{ConfigurationProvider.getConfiguration()}}.
> {code}
> AppConfiguration appConfig = ConfigurationInjection.getConfigurationInjector()
> .createTemplate(AppConfiguration.class, customConfiguration);
> {code}
> h3. Expected Behaviour
> {{appConfig}} returns values from the {{customConfiguration}}.
> h3. Actual Behaviour
> {{appConfig}} returns values from the default configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-336) Configuration templates do not work with custom configurations

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538697#comment-16538697
 ] 

ASF subversion and git services commented on TAMAYA-336:


Commit 092869379985c12315519d4e99e4ed2b198d8349 in 
incubator-tamaya-extensions's branch refs/heads/configjsr from [~anatole]
[ 
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=0928693
 ]

TAMAYA-336 Fixed config templates.

Signed-off-by: Anatole Tresch 


> Configuration templates do not work with custom configurations
> --
>
> Key: TAMAYA-336
> URL: https://issues.apache.org/jira/browse/TAMAYA-336
> Project: Tamaya
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3-incubating
>Reporter: Harald Wellmann
>Assignee: Anatole Tresch
>Priority: Major
>
> h3.  Scenario
> I'm building a configuration template from an interface, passing a custom 
> configuration as a parameter. This configuration differs from the default 
> configuration obtained by {{ConfigurationProvider.getConfiguration()}}.
> {code}
> AppConfiguration appConfig = ConfigurationInjection.getConfigurationInjector()
> .createTemplate(AppConfiguration.class, customConfiguration);
> {code}
> h3. Expected Behaviour
> {{appConfig}} returns values from the {{customConfiguration}}.
> h3. Actual Behaviour
> {{appConfig}} returns values from the default configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-336) Configuration templates do not work with custom configurations

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538696#comment-16538696
 ] 

ASF subversion and git services commented on TAMAYA-336:


Commit f5d49016fcfb31ed44a14ff76abe9d1a422884c1 in 
incubator-tamaya-extensions's branch refs/heads/master from [~anatole]
[ 
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=f5d4901
 ]

TAMAYA-336 Added javadoc.


> Configuration templates do not work with custom configurations
> --
>
> Key: TAMAYA-336
> URL: https://issues.apache.org/jira/browse/TAMAYA-336
> Project: Tamaya
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3-incubating
>Reporter: Harald Wellmann
>Assignee: Anatole Tresch
>Priority: Major
>
> h3.  Scenario
> I'm building a configuration template from an interface, passing a custom 
> configuration as a parameter. This configuration differs from the default 
> configuration obtained by {{ConfigurationProvider.getConfiguration()}}.
> {code}
> AppConfiguration appConfig = ConfigurationInjection.getConfigurationInjector()
> .createTemplate(AppConfiguration.class, customConfiguration);
> {code}
> h3. Expected Behaviour
> {{appConfig}} returns values from the {{customConfiguration}}.
> h3. Actual Behaviour
> {{appConfig}} returns values from the default configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-336) Configuration templates do not work with custom configurations

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538691#comment-16538691
 ] 

ASF subversion and git services commented on TAMAYA-336:


Commit 54351ccb3df31da60db456b18491533bd2b8b5b6 in 
incubator-tamaya-extensions's branch refs/heads/master from [~anatole]
[ 
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=54351cc
 ]

TAMAYA-336 Now forwarding target config instance.


> Configuration templates do not work with custom configurations
> --
>
> Key: TAMAYA-336
> URL: https://issues.apache.org/jira/browse/TAMAYA-336
> Project: Tamaya
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3-incubating
>Reporter: Harald Wellmann
>Assignee: Anatole Tresch
>Priority: Major
>
> h3.  Scenario
> I'm building a configuration template from an interface, passing a custom 
> configuration as a parameter. This configuration differs from the default 
> configuration obtained by {{ConfigurationProvider.getConfiguration()}}.
> {code}
> AppConfiguration appConfig = ConfigurationInjection.getConfigurationInjector()
> .createTemplate(AppConfiguration.class, customConfiguration);
> {code}
> h3. Expected Behaviour
> {{appConfig}} returns values from the {{customConfiguration}}.
> h3. Actual Behaviour
> {{appConfig}} returns values from the default configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-344) Lazy initialization of bundle

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538618#comment-16538618
 ] 

ASF subversion and git services commented on TAMAYA-344:


Commit f0043f47bf2ce025f6344dd8ab1551de635c0f48 in incubator-tamaya's branch 
refs/heads/master from [~anatole]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;h=f0043f4 ]

TAMAYA-344 Removed unnecessary lazy activation policy.


> Lazy initialization of bundle
> -
>
> Key: TAMAYA-344
> URL: https://issues.apache.org/jira/browse/TAMAYA-344
> Project: Tamaya
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.3-incubating
>Reporter: Alexander Suter
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> In this case the bundle gets automatically started, when one of its class get 
> loaded.
> So we don't have to start the bundle eagerly. It will be started 
> automatically when its needed.
> See pull request: [https://github.com/apache/incubator-tamaya/pull/23]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-344) Lazy initialization of bundle

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538614#comment-16538614
 ] 

ASF subversion and git services commented on TAMAYA-344:


Commit 2bebc0e4e574330aee142c5b0f9230afbdbb1019 in incubator-tamaya's branch 
refs/heads/configjsr from [~anatole]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;h=2bebc0e ]

TAMAYA-344 Added lazy initialization to core.

Signed-off-by: Anatole Tresch 


> Lazy initialization of bundle
> -
>
> Key: TAMAYA-344
> URL: https://issues.apache.org/jira/browse/TAMAYA-344
> Project: Tamaya
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.3-incubating
>Reporter: Alexander Suter
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> In this case the bundle gets automatically started, when one of its class get 
> loaded.
> So we don't have to start the bundle eagerly. It will be started 
> automatically when its needed.
> See pull request: [https://github.com/apache/incubator-tamaya/pull/23]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (TAMAYA-344) Lazy initialization of bundle

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch updated TAMAYA-344:
--
Affects Version/s: (was: 0.4-incubating)
   0.3-incubating

> Lazy initialization of bundle
> -
>
> Key: TAMAYA-344
> URL: https://issues.apache.org/jira/browse/TAMAYA-344
> Project: Tamaya
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.3-incubating
>Reporter: Alexander Suter
>Priority: Major
> Fix For: 0.4-incubating
>
>
> In this case the bundle gets automatically started, when one of its class get 
> loaded.
> So we don't have to start the bundle eagerly. It will be started 
> automatically when its needed.
> See pull request: [https://github.com/apache/incubator-tamaya/pull/23]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (TAMAYA-344) Lazy initialization of bundle

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch updated TAMAYA-344:
--
Fix Version/s: 0.4-incubating

> Lazy initialization of bundle
> -
>
> Key: TAMAYA-344
> URL: https://issues.apache.org/jira/browse/TAMAYA-344
> Project: Tamaya
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.3-incubating
>Reporter: Alexander Suter
>Priority: Major
> Fix For: 0.4-incubating
>
>
> In this case the bundle gets automatically started, when one of its class get 
> loaded.
> So we don't have to start the bundle eagerly. It will be started 
> automatically when its needed.
> See pull request: [https://github.com/apache/incubator-tamaya/pull/23]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (TAMAYA-344) Lazy initialization of bundle

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch reassigned TAMAYA-344:
-

Assignee: Anatole Tresch

> Lazy initialization of bundle
> -
>
> Key: TAMAYA-344
> URL: https://issues.apache.org/jira/browse/TAMAYA-344
> Project: Tamaya
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.3-incubating
>Reporter: Alexander Suter
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> In this case the bundle gets automatically started, when one of its class get 
> loaded.
> So we don't have to start the bundle eagerly. It will be started 
> automatically when its needed.
> See pull request: [https://github.com/apache/incubator-tamaya/pull/23]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (TAMAYA-344) Lazy initialization of bundle

2018-07-10 Thread Anatole Tresch (JIRA) 


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

Anatole Tresch resolved TAMAYA-344.
---
Resolution: Fixed

> Lazy initialization of bundle
> -
>
> Key: TAMAYA-344
> URL: https://issues.apache.org/jira/browse/TAMAYA-344
> Project: Tamaya
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.3-incubating
>Reporter: Alexander Suter
>Assignee: Anatole Tresch
>Priority: Major
> Fix For: 0.4-incubating
>
>
> In this case the bundle gets automatically started, when one of its class get 
> loaded.
> So we don't have to start the bundle eagerly. It will be started 
> automatically when its needed.
> See pull request: [https://github.com/apache/incubator-tamaya/pull/23]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-344) Lazy initialization of bundle

2018-07-10 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538611#comment-16538611
 ] 

ASF subversion and git services commented on TAMAYA-344:


Commit f33fb9d0c3a45311920b8d2554ce4dd3fc37e89a in incubator-tamaya's branch 
refs/heads/master from [~anatole]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;h=f33fb9d ]

TAMAYA-344 Added lazy activation policy to API/core.


> Lazy initialization of bundle
> -
>
> Key: TAMAYA-344
> URL: https://issues.apache.org/jira/browse/TAMAYA-344
> Project: Tamaya
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.4-incubating
>Reporter: Alexander Suter
>Priority: Major
>
> In this case the bundle gets automatically started, when one of its class get 
> loaded.
> So we don't have to start the bundle eagerly. It will be started 
> automatically when its needed.
> See pull request: [https://github.com/apache/incubator-tamaya/pull/23]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TAMAYA-345) Proposal: Change default key-value separator from :: to =

2018-07-10 Thread Anatole Tresch (JIRA) 


[ 
https://issues.apache.org/jira/browse/TAMAYA-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538609#comment-16538609
 ] 

Anatole Tresch commented on TAMAYA-345:
---

Actually, I dont know any either. But I am open for alternate proposals for the 
syntax to be used, e.g.

 
1) myMap=1=a, 2=b, 3=c, [4= ]
2) myMap=1::a, 2::b, 3::c, [4:: ]
3) myMap=1->a, 2->b, 3->c,[4-> ]
3) myMap=1||a, 2||b, 3||c, [4|| ]
3) myMap=1|a, 2|b, 3|c,[4| ]
3) myMap=1#a, 2#b, 3#c, [4# ]
 
WDYT?

> Proposal: Change default key-value separator from :: to = 
> --
>
> Key: TAMAYA-345
> URL: https://issues.apache.org/jira/browse/TAMAYA-345
> Project: Tamaya
>  Issue Type: Wish
>  Components: Sandbox
>Affects Versions: 0.4-incubating
>Reporter: Alexander Suter
>Assignee: Anatole Tresch
>Priority: Major
>
> I think this more common.
> [https://github.com/apache/incubator-tamaya-sandbox/pull/6]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)