Re: jira cleanup

2022-04-06 Thread Daniel Dias Dos Santos 
+1

On Wed, Apr 6, 2022, 11:59 Romain Manni-Bucau  wrote:

> +1
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le mer. 6 avr. 2022 à 16:58, Mark Struberg  a
> écrit :
>
> > hi folks!
> >
> > I'd love to go through our old tickets and close feature requests where
> we
> > didn't receive any contributions as won't fix.
> > Once people pop up again and ship patches I'm happy to open them up
> again.
> >
> > wdyt?
> >
> > LieGrue,
> > strub
> >
> >
>

[jira] [Closed] (DELTASPIKE-1084) Integrate configuration sources expressed as URLs.

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-1084.
-
Resolution: Won't Fix

closing due to no patch since a long time

> Integrate configuration sources expressed as URLs.
> --
>
> Key: DELTASPIKE-1084
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1084
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Pablo Pita Leira
>Assignee: Mark Struberg
>Priority: Minor
>
> The PropertyFileUtils class can load the properties file as follows :
> {code}
> String root = System.getProperty("user.dir");
>   String path = root + "/src/test/resources/myurlconfig.properties";
> String urlPath = "file:/" + path;
>   URL propertyFileUrl = new URL(urlPath);
>   Poperties p = PropertyFileUtils.loadProperties(propertyFileUrl);
> {code}
> Using the following code to incorporate the properties does not work:
> {code}
> public class MyUrlCustomPropertyFileConfig implements PropertyFileConfig
> {
>   
> @Override
> public String getPropertyFileName()
> {
>   String root = System.getProperty("user.dir");
>   String path = root + "/src/test/resources/myurlconfig.properties";
> return "file:/" + path;
> }
> @Override
> public boolean isOptional()
> {
> return false;
> }
> }
> {code}
> I get an exception as follows:
> {code}
> java.lang.IllegalStateException: com.example.MyUrlCustomPropertyFileConfig 
> points to an invalid file: 
> 'file:/D:\Dev\GIT\example-test/src/test/resources/myurlconfig.properties'
>   at 
> org.apache.deltaspike.core.impl.config.ConfigurationExtension.createPropertyConfigSource(ConfigurationExtension.java:210)
>   at 
> org.apache.deltaspike.core.impl.config.ConfigurationExtension.registerUserConfigSources(ConfigurationExtension.java:135)
>   at 
> org.apache.deltaspike.core.impl.config.ConfigurationExtension$Proxy$_$$_WeldClientProxy.registerUserConfigSources(ConfigurationExtension$Proxy$_$$_WeldClientProxy.java)
> {code}
> By looking into the test code in DeltaSpike I do not see any usage of the URL 
> mechanism as a property configuration source. This should be improved.
> There should be a way to integrate easily configuration sources expressed as 
> URLs. As user, I would like that the way to integrate URL paths as 
> configuration sources is also documented (including those starting with 
> file:/).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-996) org.apache.deltaspike.test.core.api.config.propertyconfigsource.ConfigPropertyWARTest#testInjectConfig fails for weblogic

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-996.

Resolution: Won't Fix

closing due to no patch since a long time

> org.apache.deltaspike.test.core.api.config.propertyconfigsource.ConfigPropertyWARTest#testInjectConfig
>  fails for weblogic
> -
>
> Key: DELTASPIKE-996
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-996
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 1.5.0
>Reporter: JJ Snyder
>Assignee: Mark Struberg
>Priority: Major
>
> org.apache.deltaspike.test.core.api.config.propertyconfigsource.ConfigPropertyWARTest#testInjectConfig
>  fails when run against weblogic.  This is failing because 
> ConfigResolver.configSources is getting populated during deployment using the 
> Thread's context class loader.  At runtime the current Thread's context class 
> loader is used to access configSources.  The problem is that the context 
> class loaders are not the same.  Afaict there is nothing in the specs that 
> says the context class loaders must be the same.  So I think the test is bad 
> and needs to be written differently.  If I force the class loader to be the 
> same in a debugger then I can make the test pass.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-591) Add a ProjectStage aware resource Servlet

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-591.

Resolution: Won't Fix

> Add a ProjectStage aware resource Servlet
> -
>
> Key: DELTASPIKE-591
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-591
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Servlet-Module
>Reporter: Daniel Sachse
>Assignee: Romain Manni-Bucau
>Priority: Major
> Attachments: DELTASPIKE-591.patch
>
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Reopened] (DELTASPIKE-591) Add a ProjectStage aware resource Servlet

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg reopened DELTASPIKE-591:
--

> Add a ProjectStage aware resource Servlet
> -
>
> Key: DELTASPIKE-591
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-591
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Servlet-Module
>Reporter: Daniel Sachse
>Assignee: Romain Manni-Bucau
>Priority: Major
> Attachments: DELTASPIKE-591.patch
>
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-858) @Exclude usage of != operator in onExpression should match when the property is not defined

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-858.

Resolution: Won't Fix

> @Exclude usage of != operator in onExpression should match when the property 
> is not defined
> ---
>
> Key: DELTASPIKE-858
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-858
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.3.0
> Environment: weld-se
>Reporter: Arrault
>Priority: Minor
> Attachments: ExcludeOnAbsentPropertyTest.java
>
>
> When using @Exclude(onExpression="property!=value"), 
> I expect the bean to be excluded if the "property" is not defined which is 
> not the case the current implementation



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Reopened] (DELTASPIKE-858) @Exclude usage of != operator in onExpression should match when the property is not defined

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg reopened DELTASPIKE-858:
--

> @Exclude usage of != operator in onExpression should match when the property 
> is not defined
> ---
>
> Key: DELTASPIKE-858
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-858
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.3.0
> Environment: weld-se
>Reporter: Arrault
>Priority: Minor
> Attachments: ExcludeOnAbsentPropertyTest.java
>
>
> When using @Exclude(onExpression="property!=value"), 
> I expect the bean to be excluded if the "property" is not defined which is 
> not the case the current implementation



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-687) Let users disable Query Method Expressions

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-687.

Resolution: Won't Fix

> Let users disable Query Method Expressions
> --
>
> Key: DELTASPIKE-687
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-687
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Affects Versions: 1.0.1
>Reporter: Dominik Obermaier
>Assignee: Daniel Cunha
>Priority: Major
>
> While Query Method Expressions are very useful, it would be great to disable 
> this feature globally or on a per-method basis if this automatic 
> implementation is not desired.
> The following approaches could be worth investigating:
> - Disable the Query Method Expressions feature globally with the 
> apache-deltaspike.properties
> - Introduce a new annotation to mark methods for getting ignored by the Query 
> Method Expression Parser



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Reopened] (DELTASPIKE-687) Let users disable Query Method Expressions

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg reopened DELTASPIKE-687:
--

> Let users disable Query Method Expressions
> --
>
> Key: DELTASPIKE-687
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-687
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Affects Versions: 1.0.1
>Reporter: Dominik Obermaier
>Assignee: Daniel Cunha
>Priority: Major
>
> While Query Method Expressions are very useful, it would be great to disable 
> this feature globally or on a per-method basis if this automatic 
> implementation is not desired.
> The following approaches could be worth investigating:
> - Disable the Query Method Expressions feature globally with the 
> apache-deltaspike.properties
> - Introduce a new annotation to mark methods for getting ignored by the Query 
> Method Expression Parser



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-844) Separate the concerns of context and container control

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-844.

Resolution: Won't Fix

> Separate the concerns of context and container control
> --
>
> Key: DELTASPIKE-844
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-844
> Project: DeltaSpike
>  Issue Type: Improvement
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
>
> There are currently 3 modules which use some form of a context controller, to 
> start contexts in an interceptor.
> Modules may optionally need to start scopes, but it shouldn't be required.
> Allow these modules to have a separation of concern with context control.  If 
> the context controller cannot be found add logs indicating that context 
> control is disabled due to missing classes.
> Add a similar ability that these modules use in a central location in context 
> control.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Reopened] (DELTASPIKE-844) Separate the concerns of context and container control

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg reopened DELTASPIKE-844:
--

> Separate the concerns of context and container control
> --
>
> Key: DELTASPIKE-844
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-844
> Project: DeltaSpike
>  Issue Type: Improvement
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
>
> There are currently 3 modules which use some form of a context controller, to 
> start contexts in an interceptor.
> Modules may optionally need to start scopes, but it shouldn't be required.
> Allow these modules to have a separation of concern with context control.  If 
> the context controller cannot be found add logs indicating that context 
> control is disabled due to missing classes.
> Add a similar ability that these modules use in a central location in context 
> control.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-977) discuss handling of custom scope-annotations

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-977.

Resolution: Won't Fix

closing due to no patch since a long time

> discuss handling of custom scope-annotations
> 
>
> Key: DELTASPIKE-977
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-977
> Project: DeltaSpike
>  Issue Type: Task
>  Components: CdiControl
>Affects Versions: 1.5.0
>Reporter: Gerhard Petracek
>Assignee: Mark Struberg
>Priority: Major
>
> e.g. we could introduce a deactivatable validator for the scope-annotations 
> passed to ContextControl#startContext and ContextControl#stopContext (similar 
> to what we have in the test-control module) to avoid wrong usages.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-688) OSGi Support for DeltaSpike JSF and its dependencies

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-688.

Resolution: Won't Fix

> OSGi Support for DeltaSpike JSF and its dependencies
> 
>
> Key: DELTASPIKE-688
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-688
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: JSF-Module, Security-Module
>Affects Versions: 1.0.1
>Reporter: Harald Wellmann
>Assignee: Harald Wellmann
>Priority: Major
>
> Goal:
> Users can work with DeltaSpike JSF in OSGi applications, using Pax CDI.
> This includes adding OSGi support to DeltaSpike Security, a runtime 
> dependency of DeltaSpike JSF.
> (Actually, I think this indicates the JSF module is not modular enough, but 
> that's a different story.  JSF should not depend on security at all.)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Reopened] (DELTASPIKE-688) OSGi Support for DeltaSpike JSF and its dependencies

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg reopened DELTASPIKE-688:
--

> OSGi Support for DeltaSpike JSF and its dependencies
> 
>
> Key: DELTASPIKE-688
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-688
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: JSF-Module, Security-Module
>Affects Versions: 1.0.1
>Reporter: Harald Wellmann
>Assignee: Harald Wellmann
>Priority: Major
>
> Goal:
> Users can work with DeltaSpike JSF in OSGi applications, using Pax CDI.
> This includes adding OSGi support to DeltaSpike Security, a runtime 
> dependency of DeltaSpike JSF.
> (Actually, I think this indicates the JSF module is not modular enough, but 
> that's a different story.  JSF should not depend on security at all.)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-921) OSGi support for Servlet Module

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-921.

Resolution: Fixed

closing due to no patch since a long time

> OSGi support for Servlet Module
> ---
>
> Key: DELTASPIKE-921
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-921
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Servlet-Module
>Affects Versions: 1.4.0
>Reporter: Harald Wellmann
>Assignee: Harald Wellmann
>Priority: Major
>
> Goal:
> Users can work with DeltaSpike Servlet in OSGi applications, using Pax CDI.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-936) OSGi capability cleanup

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-936.

Resolution: Fixed

closing due to no patch since a long time

> OSGi capability cleanup
> ---
>
> Key: DELTASPIKE-936
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-936
> Project: DeltaSpike
>  Issue Type: Improvement
>Affects Versions: 1.4.1
>Reporter: Harald Wellmann
>Assignee: Harald Wellmann
>Priority: Major
>
> OSGi capabilities and requirements are somewhat inconsistent at the moment.
> {noformat}
> osgi.extender; filter:="(osgi.extender=pax.cdi)"
> {noformat}
> must be required by all modules providing CDI beans.
> {noformat}
> org.ops4j.pax.cdi.extension;  filter:="(extension=pax-cdi-extension)"
> {noformat}
> is not required, since DeltaSpike modules do not provide or consume OSGi 
> services.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-687) Let users disable Query Method Expressions

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-687.

Resolution: Fixed

closing due to no patch since a long time

> Let users disable Query Method Expressions
> --
>
> Key: DELTASPIKE-687
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-687
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Affects Versions: 1.0.1
>Reporter: Dominik Obermaier
>Assignee: Daniel Cunha
>Priority: Major
>
> While Query Method Expressions are very useful, it would be great to disable 
> this feature globally or on a per-method basis if this automatic 
> implementation is not desired.
> The following approaches could be worth investigating:
> - Disable the Query Method Expressions feature globally with the 
> apache-deltaspike.properties
> - Introduce a new annotation to mark methods for getting ignored by the Query 
> Method Expression Parser



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-688) OSGi Support for DeltaSpike JSF and its dependencies

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-688.

Resolution: Fixed

closing due to no patch since a long time

> OSGi Support for DeltaSpike JSF and its dependencies
> 
>
> Key: DELTASPIKE-688
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-688
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: JSF-Module, Security-Module
>Affects Versions: 1.0.1
>Reporter: Harald Wellmann
>Assignee: Harald Wellmann
>Priority: Major
>
> Goal:
> Users can work with DeltaSpike JSF in OSGi applications, using Pax CDI.
> This includes adding OSGi support to DeltaSpike Security, a runtime 
> dependency of DeltaSpike JSF.
> (Actually, I think this indicates the JSF module is not modular enough, but 
> that's a different story.  JSF should not depend on security at all.)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-844) Separate the concerns of context and container control

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-844.

Resolution: Fixed

closing due to no patch since a long time

> Separate the concerns of context and container control
> --
>
> Key: DELTASPIKE-844
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-844
> Project: DeltaSpike
>  Issue Type: Improvement
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
>
> There are currently 3 modules which use some form of a context controller, to 
> start contexts in an interceptor.
> Modules may optionally need to start scopes, but it shouldn't be required.
> Allow these modules to have a separation of concern with context control.  If 
> the context controller cannot be found add logs indicating that context 
> control is disabled due to missing classes.
> Add a similar ability that these modules use in a central location in context 
> control.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-858) @Exclude usage of != operator in onExpression should match when the property is not defined

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-858.

Resolution: Fixed

closing due to no patch since a long time

> @Exclude usage of != operator in onExpression should match when the property 
> is not defined
> ---
>
> Key: DELTASPIKE-858
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-858
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.3.0
> Environment: weld-se
>Reporter: Arrault
>Priority: Minor
> Attachments: ExcludeOnAbsentPropertyTest.java
>
>
> When using @Exclude(onExpression="property!=value"), 
> I expect the bean to be excluded if the "property" is not defined which is 
> not the case the current implementation



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-591) Add a ProjectStage aware resource Servlet

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-591.

Resolution: Fixed

closing due to no patch since a long time

> Add a ProjectStage aware resource Servlet
> -
>
> Key: DELTASPIKE-591
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-591
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Servlet-Module
>Reporter: Daniel Sachse
>Assignee: Romain Manni-Bucau
>Priority: Major
> Attachments: DELTASPIKE-591.patch
>
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (DELTASPIKE-1200) Deltaspike unusable in OSGi

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg closed DELTASPIKE-1200.
-
  Assignee: Mark Struberg  (was: Harald Wellmann)
Resolution: Won't Fix

closing due to no patch since a long time

> Deltaspike unusable in OSGi
> ---
>
> Key: DELTASPIKE-1200
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1200
> Project: DeltaSpike
>  Issue Type: Bug
>Affects Versions: 1.4.2
> Environment: OSGi, Pax-CDI
>Reporter: Guillaume Nodet
>Assignee: Mark Struberg
>Priority: Blocker
>
> Deltaspike is now quite unusable in modular environments, in particular OSGi 
> due to static fields that are not supposed to be shared.
> This is particularly true for 
> {{org.apache.deltaspike.core.api.config.base.CoreBaseConfig}} inner 
> interfaces which causes lots of problems.   In my scenario, 
> {{deltaspike-core-api}} is loaded on itself as a CDI application, which cause 
> the {{BeanManagerIntegration.BeanManagerIntegration.DELEGATE_LOOKUP}} field 
> to be initialized, but this initialization fails because no config provider 
> can be found (the {{deltaspike-core-impl}} jar is not available).   
> Later on, when a real application is loaded, nothing works because the class 
> has failed initialization and thus delta pike becomes completely unusable.
> Even if I can make the initialization work in my test by changing the order 
> of the bundles and making sure the first time the classes are loaded, a 
> config provider is available, I think this means that Deltaspike can't be 
> shared at all, because those configuration bits are supposed to change from 
> one CDI app to another.
> This seems to be all caused by 
> https://github.com/apache/deltaspike/commit/25b2b8cc0c955a28743f9a84925c8e410f0d298d
>  and DELTASPIKE-892.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (DELTASPIKE-1133) Don't override the log level

2022-04-06 Thread ASF subversion and git services (Jira) 


[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17518211#comment-17518211
 ] 

ASF subversion and git services commented on DELTASPIKE-1133:
-

Commit ecf45785a120b8f6a221363cd317b83fb09ff04f in deltaspike's branch 
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=ecf45785 ]

DELTASPIKE-1133 remove setting logger level


> Don't override the log level
> 
>
> Key: DELTASPIKE-1133
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1133
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: TestControl
>Affects Versions: 1.6.0
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
> Attachments: DELTASPIKE-1133-PATCHONE.patch
>
>
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/test-control/api/src/main/java/org/apache/deltaspike/testcontrol/api/junit/CdiTestSuiteRunner.java#L155
> We override the logger level in place here, and reset it.  We shouldn't do 
> that, as you may want to have no logging output.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Resolved] (DELTASPIKE-1133) Don't override the log level

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg resolved DELTASPIKE-1133.
---
Fix Version/s: 1.9.6
   Resolution: Fixed

> Don't override the log level
> 
>
> Key: DELTASPIKE-1133
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1133
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: TestControl
>Affects Versions: 1.6.0
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
> Fix For: 1.9.6
>
> Attachments: DELTASPIKE-1133-PATCHONE.patch
>
>
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/test-control/api/src/main/java/org/apache/deltaspike/testcontrol/api/junit/CdiTestSuiteRunner.java#L155
> We override the logger level in place here, and reset it.  We shouldn't do 
> that, as you may want to have no logging output.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: jira cleanup

2022-04-06 Thread Romain Manni-Bucau 
+1

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mer. 6 avr. 2022 à 16:58, Mark Struberg  a
écrit :

> hi folks!
>
> I'd love to go through our old tickets and close feature requests where we
> didn't receive any contributions as won't fix.
> Once people pop up again and ship patches I'm happy to open them up again.
>
> wdyt?
>
> LieGrue,
> strub
>
>

jira cleanup

2022-04-06 Thread Mark Struberg 
hi folks!

I'd love to go through our old tickets and close feature requests where we 
didn't receive any contributions as won't fix.
Once people pop up again and ship patches I'm happy to open them up again.

wdyt?

LieGrue,
strub

[jira] [Assigned] (DELTASPIKE-1451) wrong docs links on https://deltaspike.apache.org/javadoc.html

2022-04-06 Thread Mark Struberg (Jira) 


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

Mark Struberg reassigned DELTASPIKE-1451:
-

Assignee: Mark Struberg

> wrong docs links on https://deltaspike.apache.org/javadoc.html
> --
>
> Key: DELTASPIKE-1451
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1451
> Project: DeltaSpike
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Documentation
>Affects Versions: 1.9.5
>Reporter: Buddha Bas
>Assignee: Mark Struberg
>Priority: Major
>  Labels: JavaDoc, links
>
> wrong docs links on https://deltaspike.apache.org/javadoc.html



--
This message was sent by Atlassian Jira
(v8.20.1#820001)