[jira] [Created] (DELTASPIKE-960) WindowIdHtmlRenderer needs to use maxWindowIdCount for window-id cookies
Gerhard Petracek created DELTASPIKE-960: --- Summary: WindowIdHtmlRenderer needs to use maxWindowIdCount for window-id cookies Key: DELTASPIKE-960 URL: https://issues.apache.org/jira/browse/DELTASPIKE-960 Project: DeltaSpike Issue Type: Bug Components: JSF-Module Affects Versions: 1.4.1 Reporter: Gerhard Petracek Fix For: 1.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-951) validate the content of TestControl#startScopes
[ https://issues.apache.org/jira/browse/DELTASPIKE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-951: Fix Version/s: (was: 1.5.0) 1.4.2 validate the content of TestControl#startScopes --- Key: DELTASPIKE-951 URL: https://issues.apache.org/jira/browse/DELTASPIKE-951 Project: DeltaSpike Issue Type: Improvement Components: TestControl Affects Versions: 1.4.2 Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 1.4.2 a lot of users use it the wrong way - we should validate it and fail fast in case of a wrong usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (DELTASPIKE-957) Improve how TransactionStrategies are looked up
[ https://issues.apache.org/jira/browse/DELTASPIKE-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek closed DELTASPIKE-957. --- Improve how TransactionStrategies are looked up --- Key: DELTASPIKE-957 URL: https://issues.apache.org/jira/browse/DELTASPIKE-957 Project: DeltaSpike Issue Type: New Feature Components: Data-Module, Documentation, JPA-Module Affects Versions: 1.4.1 Reporter: John D. Ament Currently transaction strategies are implemented as alternatives. I created a WAR for WildFly 9, and ran into a lot of issues getting it to work. My WAR has many JARs in it, all with beans.xml files. I tried to enable the alternative in various spots, but no luck, even went through all 30 beans.xml files in my project and enabled it. Still went with the default transaction strategy. In order to fix, I had to enable a global alternative with the strategy. This seems to go against our docs, which indicate it should be a regular alternative. I'd recommend a few things to think about. - Expect a concrete producer. - Use a class look up in apache-deltaspike.properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-951) validate the content of TestControl#startScopes
[ https://issues.apache.org/jira/browse/DELTASPIKE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-951. - Resolution: Fixed validate the content of TestControl#startScopes --- Key: DELTASPIKE-951 URL: https://issues.apache.org/jira/browse/DELTASPIKE-951 Project: DeltaSpike Issue Type: Improvement Components: TestControl Affects Versions: 1.4.2 Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 1.4.2 a lot of users use it the wrong way - we should validate it and fail fast in case of a wrong usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-960) WindowIdHtmlRenderer needs to use maxWindowIdCount for window-id cookies
[ https://issues.apache.org/jira/browse/DELTASPIKE-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-960. - Resolution: Fixed WindowIdHtmlRenderer needs to use maxWindowIdCount for window-id cookies Key: DELTASPIKE-960 URL: https://issues.apache.org/jira/browse/DELTASPIKE-960 Project: DeltaSpike Issue Type: Bug Components: JSF-Module Affects Versions: 1.4.1 Reporter: Gerhard Petracek Fix For: 1.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-933) Upgrade to Arquillian 1.1.8.Final
[ https://issues.apache.org/jira/browse/DELTASPIKE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-933: Component/s: Build Upgrade to Arquillian 1.1.8.Final - Key: DELTASPIKE-933 URL: https://issues.apache.org/jira/browse/DELTASPIKE-933 Project: DeltaSpike Issue Type: Improvement Components: Build Affects Versions: 1.4.0 Reporter: Harald Wellmann Assignee: Harald Wellmann Fix For: 1.4.2 This upgrade should make tests with broken deployments fail. With 1.1.4, tests from broken deployments silently do not get run, without failing the build. See DELTASPIKE-929. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-958) remove outdated information
[ https://issues.apache.org/jira/browse/DELTASPIKE-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-958: Component/s: Documentation Build remove outdated information --- Key: DELTASPIKE-958 URL: https://issues.apache.org/jira/browse/DELTASPIKE-958 Project: DeltaSpike Issue Type: Bug Components: Build, Documentation Affects Versions: 1.4.1 Reporter: Gerhard Petracek Priority: Minor Fix For: 1.4.2 we are still adding e.g. the incubator-disclaimer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-934) @Query metadata should be considered for any method expression
[ https://issues.apache.org/jira/browse/DELTASPIKE-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632910#comment-14632910 ] Gerhard Petracek commented on DELTASPIKE-934: - @john: see https://git1-us-west.apache.org/repos/asf?p=deltaspike.git;a=commit;h=687e57e8 @Query metadata should be considered for any method expression -- Key: DELTASPIKE-934 URL: https://issues.apache.org/jira/browse/DELTASPIKE-934 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Affects Versions: 1.4.0 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Fix For: 1.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DELTASPIKE-962) Refactor windowhandler.html
Thomas Andraschko created DELTASPIKE-962: Summary: Refactor windowhandler.html Key: DELTASPIKE-962 URL: https://issues.apache.org/jira/browse/DELTASPIKE-962 Project: DeltaSpike Issue Type: Improvement Components: JSF-Module, JSF22-Module Affects Versions: 1.4.1 Reporter: Thomas Andraschko Assignee: Thomas Andraschko Fix For: 1.4.3 - allow JSF resource includes to include images and styles - include our windowhandler.js and reuse js methods like setUrlParam/isHtml5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-936) OSGi capability cleanup
[
https://issues.apache.org/jira/browse/DELTASPIKE-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-936:
Fix Version/s: (was: 1.4.2)
1.4.3
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
Fix For: 1.4.3
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
(v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-961) prepare v1.4.2
[ https://issues.apache.org/jira/browse/DELTASPIKE-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-961. - Resolution: Fixed prepare v1.4.2 -- Key: DELTASPIKE-961 URL: https://issues.apache.org/jira/browse/DELTASPIKE-961 Project: DeltaSpike Issue Type: Task Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 1.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release of Apache DeltaSpike 1.4.2
+1 Romain Manni-Bucau @rmannibucau https://twitter.com/rmannibucau | Blog http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau | LinkedIn https://www.linkedin.com/in/rmannibucau | Tomitriber http://www.tomitribe.com 2015-07-19 10:33 GMT-07:00 Cody Lerum cody.le...@gmail.com: Builds + tests + looks fine locally for me. +1 On Sun, Jul 19, 2015 at 11:11 AM, Gerhard Petracek gpetra...@apache.org wrote: Hi, I was running the needed tasks to get the 18th 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.4.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-1028/ [2] https://repository.apache.org/content/repositories/orgapachedeltaspike-1028/org/apache/deltaspike/deltaspike/1.4.2/deltaspike-1.4.2-source-release.zip [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.4.2 [4] https://github.com/os890/deltaspike-vote/tree/ds-1.4.2 [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
Re: [VOTE] Release of Apache DeltaSpike 1.4.2
There are some changes from newer team members where I can't find a relationship between code change and JIRA ticket. I've pinged on one ticket, I'd like to see that answered before giving a vote. John On Sun, Jul 19, 2015 at 1:11 PM Gerhard Petracek gpetra...@apache.org wrote: Hi, I was running the needed tasks to get the 18th 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.4.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-1028/ [2] https://repository.apache.org/content/repositories/orgapachedeltaspike-1028/org/apache/deltaspike/deltaspike/1.4.2/deltaspike-1.4.2-source-release.zip [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.4.2 [4] https://github.com/os890/deltaspike-vote/tree/ds-1.4.2 [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
[jira] [Updated] (DELTASPIKE-929) Weld test profile is broken
[
https://issues.apache.org/jira/browse/DELTASPIKE-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-929:
Component/s: Build
Weld test profile is broken
---
Key: DELTASPIKE-929
URL: https://issues.apache.org/jira/browse/DELTASPIKE-929
Project: DeltaSpike
Issue Type: Bug
Components: Build
Affects Versions: 1.4.0
Reporter: Harald Wellmann
Assignee: Harald Wellmann
Fix For: 1.4.2
The Weld test profile is broken, see e.g.
https://builds.apache.org/view/All/job/DeltaSpike%20Weld%201.1.28/4/consoleFull
The following exception causes most tests to be skipped without being
reported as failure:
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.jboss.weld.manager.api.WeldManager
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 47 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-931) Integration tests fail when dependencies are class folders, not JARs
[
https://issues.apache.org/jira/browse/DELTASPIKE-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-931:
Component/s: Tests
Integration tests fail when dependencies are class folders, not JARs
Key: DELTASPIKE-931
URL: https://issues.apache.org/jira/browse/DELTASPIKE-931
Project: DeltaSpike
Issue Type: Bug
Components: Tests
Affects Versions: 1.4.0
Reporter: Harald Wellmann
Assignee: Harald Wellmann
Fix For: 1.4.2
Arquillian-based tests fail when run from Eclipse, e.g.
{{org.apache.deltaspike.test.core.api.alternative.global.GlobalAlternativeTest}}
{noformat}
java.lang.IllegalStateException: Could not find beans for Type=class
org.apache.deltaspike.core.impl.scope.window.WindowBeanHolder and
qualifiers:[]
at
org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:153)
at
org.apache.deltaspike.core.impl.scope.DeltaSpikeContextExtension.initializeDeltaSpikeContexts(DeltaSpikeContextExtension.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.apache.webbeans.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:266)
at
org.apache.webbeans.event.NotificationManager.fireEvent(NotificationManager.java:482)
at
org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:446)
at
org.apache.webbeans.container.BeanManagerImpl.fireLifecycleEvent(BeanManagerImpl.java:436)
at
org.apache.webbeans.config.BeansDeployer.fireAfterDeploymentValidationEvent(BeansDeployer.java:374)
at
org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:205)
at
org.apache.webbeans.lifecycle.AbstractLifeCycle.bootstrapApplication(AbstractLifeCycle.java:141)
at
org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:107)
at
org.apache.webbeans.arquillian.standalone.OwbStandaloneContainer.deploy(OwbStandaloneContainer.java:122)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at
org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at
org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at
org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at
org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at
org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at
org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at
[jira] [Updated] (DELTASPIKE-887) ds:windowId should initialize the windowhandler script
[ https://issues.apache.org/jira/browse/DELTASPIKE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-887: Component/s: JSF-Module ds:windowId should initialize the windowhandler script -- Key: DELTASPIKE-887 URL: https://issues.apache.org/jira/browse/DELTASPIKE-887 Project: DeltaSpike Issue Type: Bug Components: JSF-Module Affects Versions: 1.3.0 Reporter: Thomas Andraschko Assignee: Thomas Andraschko Fix For: 1.4.2 Currently the windowhandler will be initialized with window.onload but if the user defined an onload attribute on the body, the js version will be ignored. This requires an bigger refactoring on the client side, therefore i will fix in the future when developing the new mixed mode between LAZY/CLIENT_WINDOW. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-934) @Query metadata should be considered for any method expression
[ https://issues.apache.org/jira/browse/DELTASPIKE-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632906#comment-14632906 ] John D. Ament commented on DELTASPIKE-934: -- [~danielsoro] I'm not able to find any commits related to this ticket in git. What does this fix? @Query metadata should be considered for any method expression -- Key: DELTASPIKE-934 URL: https://issues.apache.org/jira/browse/DELTASPIKE-934 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Affects Versions: 1.4.0 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Fix For: 1.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-921) OSGi support for Servlet Module
[ https://issues.apache.org/jira/browse/DELTASPIKE-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-921: Fix Version/s: (was: 1.4.2) 1.4.3 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 Fix For: 1.4.3 Goal: Users can work with DeltaSpike Servlet in OSGi applications, using Pax CDI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-897) discuss configuration of a ClassDeactivator
[ https://issues.apache.org/jira/browse/DELTASPIKE-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-897: Fix Version/s: (was: 1.4.2) 1.5.0 discuss configuration of a ClassDeactivator --- Key: DELTASPIKE-897 URL: https://issues.apache.org/jira/browse/DELTASPIKE-897 Project: DeltaSpike Issue Type: Task Components: Core Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 1.5.0 currently it's needed to configure a custom ClassDeactivator via apache-deltaspike.properties, but not via META-INF/services/org.apache.deltaspike.core.spi.activation.ClassDeactivator this limitation was required, because it isn't possible to deactivate/overrule a ClassDeactivator configured via the std. spi-config, but via config-sources and ordinals it's possible to overrule it. that's basically fine, but not that intuitive esp. because it's a spi for a low-level functionality - users expect a std. spi-config. therefore we should combine both or provide a corresponding hint/warning. #1 usually there is just one configured ClassDeactivator and therefore we can support both config formats easily. once there is at least one ClassDeactivator configured in apache-deltaspike.properties, we can ignore all implementations of ClassDeactivator configured via the std. spi-config. that allows to deactivate/overrule such a configuration. currently we just support one ClassDeactivator at runtime. that's limited by the config-format itself. since a std. spi-config allows multiple config-entries, we would need to use an internal instance which aggregates instances of the configured classes. #2 we just check if there is an active spi-config for 1-n implementations of ClassDeactivator and in such cases we log a warning that they are ignored and how to configure a ClassDeactivator correctly (and that only one active implementation is supported). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-645) review sonar findings
[ https://issues.apache.org/jira/browse/DELTASPIKE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-645: Fix Version/s: (was: 1.4.2) 1.5.0 review sonar findings - Key: DELTASPIKE-645 URL: https://issues.apache.org/jira/browse/DELTASPIKE-645 Project: DeltaSpike Issue Type: Task Affects Versions: 1.0.0 Reporter: Gerhard Petracek Assignee: Matt Benson Fix For: 1.5.0 a lot of the sonar findings are wrong, because sonar isn't aware of cdi and there are still some old rules in there. however, we should review the findings on a regular basis. see http://deltaspike.apache.org/build.html#sonar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-724) upgrade version of the tomee-arquillian adapter
[ 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.4.2) 1.5.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.5.0 to test against tomee 1.7.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-440) discuss helper for adding deployment-problems
[ https://issues.apache.org/jira/browse/DELTASPIKE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-440: Fix Version/s: (was: 1.4.2) 1.5.0 discuss helper for adding deployment-problems - Key: DELTASPIKE-440 URL: https://issues.apache.org/jira/browse/DELTASPIKE-440 Project: DeltaSpike Issue Type: Task Components: Core Reporter: Gerhard Petracek Assignee: Rafael Benevides Fix For: 1.5.0 in many cases it's possible to detect deployment-problems before AfterDeploymentValidation. it's possible to throw an exception at any time, however, it might be useful to unify it. e.g. collecting problems via a helper which adds all issues via AfterDeploymentValidation#addDeploymentProblem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-872) Support mocking on proxied beans
[ https://issues.apache.org/jira/browse/DELTASPIKE-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-872: Fix Version/s: (was: 1.4.2) 1.5.0 Support mocking on proxied beans Key: DELTASPIKE-872 URL: https://issues.apache.org/jira/browse/DELTASPIKE-872 Project: DeltaSpike Issue Type: Improvement Components: TestControl Affects Versions: 1.3.0 Reporter: Rafael Assignee: Thomas Andraschko Fix For: 1.5.0 Currently test control mock feature is not supported on proxies (e.g: beans with interceptors), a sample test which fails because of this limitation can be found here: https://github.com/rmpestano/ee6-ds-demo/blob/master/src/test/java/org/os890/demo/ee6/test/MockTest.java . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-813) improve basic core documentation
[ 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.4.2) 1.5.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: Ron Smeral Fix For: 1.5.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)
Re: [VOTE] Release of Apache DeltaSpike 1.4.2
Builds + tests + looks fine locally for me. +1 On Sun, Jul 19, 2015 at 11:11 AM, Gerhard Petracek gpetra...@apache.org wrote: Hi, I was running the needed tasks to get the 18th 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.4.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-1028/ [2] https://repository.apache.org/content/repositories/orgapachedeltaspike-1028/org/apache/deltaspike/deltaspike/1.4.2/deltaspike-1.4.2-source-release.zip [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.4.2 [4] https://github.com/os890/deltaspike-vote/tree/ds-1.4.2 [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
[VOTE] Release of Apache DeltaSpike 1.4.2
Hi, I was running the needed tasks to get the 18th 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.4.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-1028/ [2] https://repository.apache.org/content/repositories/orgapachedeltaspike-1028/org/apache/deltaspike/deltaspike/1.4.2/deltaspike-1.4.2-source-release.zip [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.4.2 [4] https://github.com/os890/deltaspike-vote/tree/ds-1.4.2 [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
Re: [VOTE] Release of Apache DeltaSpike 1.4.2
+1 regards, gerhard 2015-07-19 19:11 GMT+02:00 Gerhard Petracek gpetra...@apache.org: Hi, I was running the needed tasks to get the 18th 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.4.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-1028/ [2] https://repository.apache.org/content/repositories/orgapachedeltaspike-1028/org/apache/deltaspike/deltaspike/1.4.2/deltaspike-1.4.2-source-release.zip [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.4.2 [4] https://github.com/os890/deltaspike-vote/tree/ds-1.4.2 [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
