[jira] [Closed] (DELTASPIKE-1018) Automatic RequestScope activation for @MBean invocations

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek closed DELTASPIKE-1018.


> Automatic RequestScope activation for @MBean invocations 
> -
>
> Key: DELTASPIKE-1018
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1018
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 1.0.2
>Reporter: Falko Modler
>Priority: Minor
>
> When a {{@JmxManaged}} method is called (via jconsole for instance) on a 
> CDI-Bean which has been registered as a MBean via {{@MBean}} annotation, the 
> RequestScope is not active.
> It would be handy if RequestScope could be actived automatically, perhaps 
> configurable via a new {{@MBean}} attribute and/or 
> {{apache-deltaspike.properties}}.
> Workaround: Implement and register an Interceptor which actives/deactivates 
> the scope via {{ContextControl}} around the method invocation.



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

[jira] [Updated] (DELTASPIKE-1015) Support hierarchical BeanManager and Extensions

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-1015:
-
Issue Type: Improvement  (was: Bug)

> Support hierarchical BeanManager and Extensions
> ---
>
> Key: DELTASPIKE-1015
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1015
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 1.5.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.5.2
>
>
> Some Containers use a BeanManager hierarchy for EARs. Means the BeanManagers 
> (and their Extensions) follow the ClassLoaders. 
> To support EARs we need to introduce a 'getParentExtension' mechanism. All 
> other ways (e.g. sharing Extensions over wars) lead to corrupt classloaders 
> and easily trash the application in a random manner (depending on the startup 
> order).



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

[jira] [Closed] (DELTASPIKE-1017) spi for config-validation

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek closed DELTASPIKE-1017.


> spi for config-validation
> -
>
> Key: DELTASPIKE-1017
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1017
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 1.5.1
>Reporter: Gerhard Petracek
>Assignee: Gerhard Petracek
> Fix For: 1.5.2
>
>
> some config-sources get added quite late.
> e.g. implementations of PropertyFileConfig via an AfterDeploymentValidation 
> observer.
> => it isn't possible to validate e.g. type-safe configs based on the 
> partial-bean-module, because there is no portable way to trigger the 
> validation after the observer-method of ds and before the application is 
> started.
> therefore we need a spi for it.



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

[jira] [Resolved] (DELTASPIKE-1011) re-visit excluded tests for the wls profiles

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek resolved DELTASPIKE-1011.
--
Resolution: Fixed

> re-visit excluded tests for the wls profiles
> 
>
> Key: DELTASPIKE-1011
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1011
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Build, Tests
>Affects Versions: 1.5.1
>Reporter: Gerhard Petracek
>Assignee: Gerhard Petracek
>Priority: Minor
> Fix For: 1.5.2
>
>




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

Re: @ConfigProperty and constructors

[John D. Ament]

What's the use case? Also why does your patch mark a bunch of stuff as
deprecated?

On Fri, Dec 4, 2015 at 2:01 PM Romain Manni-Bucau 
wrote:

> Oh yep just set the n+1 as a default. Thanks for updating it.
> Le 4 déc. 2015 19:53, "Gerhard Petracek"  a
> écrit :
>
> > +1
> > (i just mentioned it, because "Fix Version" is currently 1.5.2.)
> >
> > regards,
> > gerhard
> >
> >
> >
> > 2015-12-04 19:45 GMT+01:00 Romain Manni-Bucau :
> >
> > > well we can discuss it even if we dont push anything yet  ;)
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Github <
> > > https://github.com/rmannibucau> |
> > > LinkedIn  | Tomitriber
> > > 
> > >
> > > 2015-12-04 19:22 GMT+01:00 Gerhard Petracek <
> gerhard.petra...@gmail.com
> > >:
> > >
> > > > hi romain,
> > > >
> > > > i'll start with the release-steps for v1.5.2 soon -> let's discuss it
> > for
> > > > v1.5.3.
> > > >
> > > > regards,
> > > > gerhard
> > > >
> > > >
> > > >
> > > > 2015-12-04 15:49 GMT+01:00 Romain Manni-Bucau  >:
> > > >
> > > > > Hi guys,
> > > > >
> > > > > opened https://issues.apache.org/jira/browse/DELTASPIKE-1037
> > > > >
> > > > > WDYT about this feature?
> > > > >
> > > > > Side note: wondered if we should support List/Map with the same
> > > coercing
> > > > > logic, these types are quite common IMHO.
> > > > >
> > > > > Romain Manni-Bucau
> > > > > @rmannibucau  |  Blog
> > > > >  | Github <
> > > > > https://github.com/rmannibucau> |
> > > > > LinkedIn  | Tomitriber
> > > > > 
> > > > >
> > > >
> > >
> >
>

Re: @ConfigProperty and constructors

[Romain Manni-Bucau]

use case: be able to convert more types than the one planned in our default
producer (later we would wire converters to the producing logic IMO, today
it is kind of split)
deprecation: cause all this code is not needed, was there cause we never
supported "generic" producers but nothing technically preventing it (this
patch is just one step to this goal)


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber


2015-12-06 15:52 GMT+01:00 John D. Ament :

> What's the use case? Also why does your patch mark a bunch of stuff as
> deprecated?
>
> On Fri, Dec 4, 2015 at 2:01 PM Romain Manni-Bucau 
> wrote:
>
> > Oh yep just set the n+1 as a default. Thanks for updating it.
> > Le 4 déc. 2015 19:53, "Gerhard Petracek"  a
> > écrit :
> >
> > > +1
> > > (i just mentioned it, because "Fix Version" is currently 1.5.2.)
> > >
> > > regards,
> > > gerhard
> > >
> > >
> > >
> > > 2015-12-04 19:45 GMT+01:00 Romain Manni-Bucau :
> > >
> > > > well we can discuss it even if we dont push anything yet  ;)
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau  |  Blog
> > > >  | Github <
> > > > https://github.com/rmannibucau> |
> > > > LinkedIn  | Tomitriber
> > > > 
> > > >
> > > > 2015-12-04 19:22 GMT+01:00 Gerhard Petracek <
> > gerhard.petra...@gmail.com
> > > >:
> > > >
> > > > > hi romain,
> > > > >
> > > > > i'll start with the release-steps for v1.5.2 soon -> let's discuss
> it
> > > for
> > > > > v1.5.3.
> > > > >
> > > > > regards,
> > > > > gerhard
> > > > >
> > > > >
> > > > >
> > > > > 2015-12-04 15:49 GMT+01:00 Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >:
> > > > >
> > > > > > Hi guys,
> > > > > >
> > > > > > opened https://issues.apache.org/jira/browse/DELTASPIKE-1037
> > > > > >
> > > > > > WDYT about this feature?
> > > > > >
> > > > > > Side note: wondered if we should support List/Map with the same
> > > > coercing
> > > > > > logic, these types are quite common IMHO.
> > > > > >
> > > > > > Romain Manni-Bucau
> > > > > > @rmannibucau  |  Blog
> > > > > >  | Github <
> > > > > > https://github.com/rmannibucau> |
> > > > > > LinkedIn  | Tomitriber
> > > > > > 
> > > > > >
> > > > >
> > > >
> > >
> >
>

[jira] [Resolved] (DELTASPIKE-1038) prepare v1.5.2

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek resolved DELTASPIKE-1038.
--
Resolution: Fixed

> prepare v1.5.2
> --
>
> Key: DELTASPIKE-1038
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1038
> Project: DeltaSpike
>  Issue Type: Task
>Reporter: Gerhard Petracek
>Assignee: Gerhard Petracek
> Fix For: 1.5.2
>
>




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

[jira] [Resolved] (DELTASPIKE-1020) improve core documentation

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek resolved DELTASPIKE-1020.
--
Resolution: Fixed

> improve core documentation
> --
>
> Key: DELTASPIKE-1020
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1020
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: 1.5.1
>Reporter: Gerhard Petracek
>Assignee: Gerhard Petracek
> Fix For: 1.5.2
>
>




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

[jira] [Resolved] (DELTASPIKE-1017) spi for config-validation

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek resolved DELTASPIKE-1017.
--
Resolution: Fixed

> spi for config-validation
> -
>
> Key: DELTASPIKE-1017
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1017
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 1.5.1
>Reporter: Gerhard Petracek
>Assignee: Gerhard Petracek
> Fix For: 1.5.2
>
>
> some config-sources get added quite late.
> e.g. implementations of PropertyFileConfig via an AfterDeploymentValidation 
> observer.
> => it isn't possible to validate e.g. type-safe configs based on the 
> partial-bean-module, because there is no portable way to trigger the 
> validation after the observer-method of ds and before the application is 
> started.
> therefore we need a spi for it.



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

Re: [VOTE] Release of Apache DeltaSpike 1.5.2

[John D. Ament]

+1
On Dec 6, 2015 14:54, "Gerhard Petracek"  wrote:

> Hi,
>
> I was running the needed tasks to get the 21th release of Apache DeltaSpike
> out.
> The artifacts are deployed to Nexus [1] (and [2]).
>
> The tag is available at [3] and the release-branch at [4].
> They will get pushed to the ASF repository once the vote passed.
>
> Please take a look at the 1.5.2 artifacts and vote!
>
> Please note:
> This vote is "majority approval" with a minimum of three +1 votes (see
> [5]).
>
> 
> [ ] +1 for community members who have reviewed the bits
> [ ] +0
> [ ] -1 for fatal flaws that should cause these bits not to be released, and
> why..
> 
>
> Thanks,
> Gerhard
>
> [1]
>
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1031/
> [2]
>
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1031/org/apache/deltaspike/deltaspike/1.5.2/deltaspike-1.5.2-source-release.zip
> [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.5.2
> [4] https://github.com/os890/deltaspike-vote/tree/ds-1.5.2
> [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
>

[jira] [Closed] (DELTASPIKE-1030) Initial redirect does not encode URL properly

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek closed DELTASPIKE-1030.


> Initial redirect does not encode URL properly
> -
>
> Key: DELTASPIKE-1030
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1030
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.5.1
> Environment: JBoss EAP 6.4.4
> -Dorg.apache.catalina.connector.URI_ENCODING=UTF-8
>Reporter: Armin Schaberl
>Assignee: Rafael Benevides
>Priority: Minor
>
> Unicode Parameters on the initial request to an application won't get encoded 
> properly.
> They are currently encoded by the response's default encoding (i.e. 
> ISO8859-1). The encoding for the servers URL parameters could possible be 
> another one. I.e. we are using a UTF-8 (due to vm parameter 
> -Dorg.apache.catalina.connector.URI_ENCODING=UTF-8 on our JBoss EAP 6.4).
> So Deltaspike generates a redirect URL to the same Application/Server with an 
> incorrect encoding.
> The test ist quite simple, just use parameters with German umlauts on the 
> initial request to a server which supports UTF-8 URL parameters.



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

[jira] [Resolved] (DELTASPIKE-1030) Initial redirect does not encode URL properly

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek resolved DELTASPIKE-1030.
--
Resolution: Won't Fix

please create a new ticket for a spi (if it's still needed)

> Initial redirect does not encode URL properly
> -
>
> Key: DELTASPIKE-1030
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1030
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.5.1
> Environment: JBoss EAP 6.4.4
> -Dorg.apache.catalina.connector.URI_ENCODING=UTF-8
>Reporter: Armin Schaberl
>Assignee: Rafael Benevides
>Priority: Minor
>
> Unicode Parameters on the initial request to an application won't get encoded 
> properly.
> They are currently encoded by the response's default encoding (i.e. 
> ISO8859-1). The encoding for the servers URL parameters could possible be 
> another one. I.e. we are using a UTF-8 (due to vm parameter 
> -Dorg.apache.catalina.connector.URI_ENCODING=UTF-8 on our JBoss EAP 6.4).
> So Deltaspike generates a redirect URL to the same Application/Server with an 
> incorrect encoding.
> The test ist quite simple, just use parameters with German umlauts on the 
> initial request to a server which supports UTF-8 URL parameters.



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

[jira] [Updated] (DELTASPIKE-1033) BeanManagerProvider might create mem leaks

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-1033:
-
Fix Version/s: (was: 1.5.2)
   1.6.0

> BeanManagerProvider might create mem leaks
> --
>
> Key: DELTASPIKE-1033
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1033
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.5.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.6.0
>
>
> We currently use a Map in BeanManagerProvider. 
> This is a class 1 candidate to generate mem leaks when a webapp gets 
> undeployed. We should switch to using WeakReferences instead.



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

[jira] [Updated] (DELTASPIKE-724) upgrade version of the tomee-arquillian adapter

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-724:

Fix Version/s: (was: 1.5.2)
   1.6.0

> upgrade version of the tomee-arquillian adapter
> ---
>
> Key: DELTASPIKE-724
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-724
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Build, Tests
>Reporter: Gerhard Petracek
>Assignee: Romain Manni-Bucau
> Fix For: 1.6.0
>
>
> to test against tomee 1.7.1



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

[jira] [Updated] (DELTASPIKE-813) improve basic core documentation

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-813:

Fix Version/s: (was: 1.5.2)
   1.6.0

> improve basic core documentation
> 
>
> Key: DELTASPIKE-813
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-813
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: 1.2.1
>Reporter: Gerhard Petracek
>Assignee: Rafael Benevides
> Fix For: 1.6.0
>
>
> in this first step we should improve everything which is marked red or yellow 
> in the documentation column and green or yellow in the "importance for 
> average users" column ( see 
> https://cwiki.apache.org/confluence/display/DeltaSpike/DS-Core+Overview )



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

[jira] [Updated] (DELTASPIKE-839) Data module test deployments pack individual classes instead of JARs

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-839:

Fix Version/s: 1.5.2

> Data module test deployments pack individual classes instead of JARs
> 
>
> Key: DELTASPIKE-839
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-839
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module, Tests
>Affects Versions: 1.2.1
>Reporter: Ron Smeral
>Assignee: Daniel Cunha
>Priority: Minor
> Fix For: 1.5.2
>
>
> Tests of all other modules pack dependencies using ShrinkWrap's 
> {{addLibrary}}, but data module tests add api and impl classes individually 
> using {{addClass}}. This reduces the fidelity of the tests.



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

[VOTE] Release of Apache DeltaSpike 1.5.2

[Gerhard Petracek]

Hi,

I was running the needed tasks to get the 21th release of Apache DeltaSpike
out.
The artifacts are deployed to Nexus [1] (and [2]).

The tag is available at [3] and the release-branch at [4].
They will get pushed to the ASF repository once the vote passed.

Please take a look at the 1.5.2 artifacts and vote!

Please note:
This vote is "majority approval" with a minimum of three +1 votes (see [5]).


[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released, and
why..


Thanks,
Gerhard

[1]
https://repository.apache.org/content/repositories/orgapachedeltaspike-1031/
[2]
https://repository.apache.org/content/repositories/orgapachedeltaspike-1031/org/apache/deltaspike/deltaspike/1.5.2/deltaspike-1.5.2-source-release.zip
[3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.5.2
[4] https://github.com/os890/deltaspike-vote/tree/ds-1.5.2
[5] http://www.apache.org/foundation/voting.html#ReleaseVotes

[jira] [Updated] (DELTASPIKE-1030) Initial redirect does not encode URL properly

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-1030:
-
Fix Version/s: (was: 1.5.2)

> Initial redirect does not encode URL properly
> -
>
> Key: DELTASPIKE-1030
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1030
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.5.1
> Environment: JBoss EAP 6.4.4
> -Dorg.apache.catalina.connector.URI_ENCODING=UTF-8
>Reporter: Armin Schaberl
>Assignee: Rafael Benevides
>Priority: Minor
>
> Unicode Parameters on the initial request to an application won't get encoded 
> properly.
> They are currently encoded by the response's default encoding (i.e. 
> ISO8859-1). The encoding for the servers URL parameters could possible be 
> another one. I.e. we are using a UTF-8 (due to vm parameter 
> -Dorg.apache.catalina.connector.URI_ENCODING=UTF-8 on our JBoss EAP 6.4).
> So Deltaspike generates a redirect URL to the same Application/Server with an 
> incorrect encoding.
> The test ist quite simple, just use parameters with German umlauts on the 
> initial request to a server which supports UTF-8 URL parameters.



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

[jira] [Commented] (DELTASPIKE-1033) BeanManagerProvider might create mem leaks

[John D. Ament (JIRA)]

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

John D. Ament commented on DELTASPIKE-1033:
---

I wonder, can `PreDestroy` methods be invoked on extensions?  I've never tried, 
but it may be a way to fix this.
If so, may be worthwhile to remove static references, and in the predestroy 
clear out the map.

> BeanManagerProvider might create mem leaks
> --
>
> Key: DELTASPIKE-1033
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1033
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.5.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.6.0
>
>
> We currently use a Map in BeanManagerProvider. 
> This is a class 1 candidate to generate mem leaks when a webapp gets 
> undeployed. We should switch to using WeakReferences instead.



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

Re: [VOTE] Release of Apache DeltaSpike 1.5.2

[Christian Kaltepoth]

+1

2015-12-06 21:01 GMT+01:00 John D. Ament :

> +1
> On Dec 6, 2015 14:54, "Gerhard Petracek"  wrote:
>
> > Hi,
> >
> > I was running the needed tasks to get the 21th release of Apache
> DeltaSpike
> > out.
> > The artifacts are deployed to Nexus [1] (and [2]).
> >
> > The tag is available at [3] and the release-branch at [4].
> > They will get pushed to the ASF repository once the vote passed.
> >
> > Please take a look at the 1.5.2 artifacts and vote!
> >
> > Please note:
> > This vote is "majority approval" with a minimum of three +1 votes (see
> > [5]).
> >
> > 
> > [ ] +1 for community members who have reviewed the bits
> > [ ] +0
> > [ ] -1 for fatal flaws that should cause these bits not to be released,
> and
> > why..
> > 
> >
> > Thanks,
> > Gerhard
> >
> > [1]
> >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1031/
> > [2]
> >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1031/org/apache/deltaspike/deltaspike/1.5.2/deltaspike-1.5.2-source-release.zip
> > [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.5.2
> > [4] https://github.com/os890/deltaspike-vote/tree/ds-1.5.2
> > [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >
>



-- 
Christian Kaltepoth
Blog: http://blog.kaltepoth.de/
Twitter: http://twitter.com/chkal
GitHub: https://github.com/chkal