[GitHub] [deltaspike] Daniel-Dos commented on issue #88: DELTASPIKE-1374: fix version to 1.9.0
Daniel-Dos commented on issue #88: DELTASPIKE-1374: fix version to 1.9.0 URL: https://github.com/apache/deltaspike/pull/88#issuecomment-476232553 your welcome This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (DELTASPIKE-1328) Add a Java 8 base repository
[
https://issues.apache.org/jira/browse/DELTASPIKE-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko updated DELTASPIKE-1328:
--
Fix Version/s: (was: 1.9.1)
> Add a Java 8 base repository
>
>
> Key: DELTASPIKE-1328
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1328
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Data-Module
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
>
> Add a base repository, like {{EntityRepository}} but for Java 8
> {{Optional/Stream}} use cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (DELTASPIKE-1367) JNDI Config Source should support alternate JNDI base names
[ https://issues.apache.org/jira/browse/DELTASPIKE-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Andraschko reassigned DELTASPIKE-1367: - Assignee: Mark Struberg (was: Thomas Andraschko) > JNDI Config Source should support alternate JNDI base names > --- > > Key: DELTASPIKE-1367 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1367 > Project: DeltaSpike > Issue Type: Improvement > Components: Configuration >Affects Versions: 1.9.0 >Reporter: John Schneider >Assignee: Mark Struberg >Priority: Major > > JNDI Config is hard-coded to only support "java:comp/env/deltaspike/" as a > base name. This doesn't work for EAR deployments where we must have the > DeltaSpike jars deployed in top-level app lib directory with JNDI resource > reference in application.xml, for which name prefix is java:app/env > Furthermore, it's sometimes desirable to have server-level config, such as > for ProjectStage. For example, a JNDI name > java:global/env/deltaspike/org.apache.deltaspike/ProjectStage might be > defined at the server level configuration. > I understand a custom config source can be created to overcome this. > However, the standard JNDI config source should be more flexible. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1370) Deltaspike documentation states the latest release is 1.8.2
[ https://issues.apache.org/jira/browse/DELTASPIKE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800564#comment-16800564 ] Thomas Andraschko commented on DELTASPIKE-1370: --- I changed it via the apache CMS now > Deltaspike documentation states the latest release is 1.8.2 > --- > > Key: DELTASPIKE-1370 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1370 > Project: DeltaSpike > Issue Type: Task > Components: Documentation >Reporter: Alexander Falb >Priority: Trivial > > Our [Download|https://deltaspike.apache.org/download.html] page says the > latest version of DeltaSpike is 1.8.2, but it should be 1.9.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (DELTASPIKE-1367) JNDI Config Source should support alternate JNDI base names
[ https://issues.apache.org/jira/browse/DELTASPIKE-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Andraschko reassigned DELTASPIKE-1367: - Assignee: Thomas Andraschko > JNDI Config Source should support alternate JNDI base names > --- > > Key: DELTASPIKE-1367 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1367 > Project: DeltaSpike > Issue Type: Improvement > Components: Configuration >Affects Versions: 1.9.0 >Reporter: John Schneider >Assignee: Thomas Andraschko >Priority: Major > > JNDI Config is hard-coded to only support "java:comp/env/deltaspike/" as a > base name. This doesn't work for EAR deployments where we must have the > DeltaSpike jars deployed in top-level app lib directory with JNDI resource > reference in application.xml, for which name prefix is java:app/env > Furthermore, it's sometimes desirable to have server-level config, such as > for ProjectStage. For example, a JNDI name > java:global/env/deltaspike/org.apache.deltaspike/ProjectStage might be > defined at the server level configuration. > I understand a custom config source can be created to overcome this. > However, the standard JNDI config source should be more flexible. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1368) Repository doesn't work in Java SE
[ https://issues.apache.org/jira/browse/DELTASPIKE-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800567#comment-16800567 ] Thomas Andraschko commented on DELTASPIKE-1368: --- Can you provide a example project? Otherwise hard to help. > Repository doesn't work in Java SE > -- > > Key: DELTASPIKE-1368 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1368 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Affects Versions: 1.9.0 >Reporter: Ehsan Zaery Moghaddam >Priority: Minor > > Hi Guys > I'm trying to use the repository implementation in a Java SE environment. I > start the Weld container using deltaspike cdi control module. When I try to > persist an entity using the repository class, it doesn't report any error, > but nothing get persisted in the DB. > Is there any limitation/configuration in using repositories in Java SE? It > works fine when I try to persist it directly via JPA. > I've already described it in more details in this > [stackoverflow|https://stackoverflow.com/questions/53783775/deltaspike-repository-transaction-commits-but-nothing-persists-in-db-in-java-se] > issue but got no answer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (DELTASPIKE-1370) Deltaspike documentation states the latest release is 1.8.2
[ https://issues.apache.org/jira/browse/DELTASPIKE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Andraschko closed DELTASPIKE-1370. - Resolution: Fixed > Deltaspike documentation states the latest release is 1.8.2 > --- > > Key: DELTASPIKE-1370 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1370 > Project: DeltaSpike > Issue Type: Task > Components: Documentation >Reporter: Alexander Falb >Priority: Trivial > > Our [Download|https://deltaspike.apache.org/download.html] page says the > latest version of DeltaSpike is 1.8.2, but it should be 1.9.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [deltaspike] tandraschko commented on issue #88: DELTASPIKE-1374: fix version to 1.9.0
tandraschko commented on issue #88: DELTASPIKE-1374: fix version to 1.9.0 URL: https://github.com/apache/deltaspike/pull/88#issuecomment-476132259 Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (DELTASPIKE-1366) Add Junit5 testing support
[
https://issues.apache.org/jira/browse/DELTASPIKE-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800551#comment-16800551
]
Thomas Andraschko commented on DELTASPIKE-1366:
---
[~javatesting] it would be really great if you could work on it.
> Add Junit5 testing support
> --
>
> Key: DELTASPIKE-1366
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1366
> Project: DeltaSpike
> Issue Type: Wish
> Components: TestControl, Tests
>Affects Versions: 1.9.0
>Reporter: John Smith
>Priority: Major
>
> Are there any plans to provide a junit5 extension like the CdiTestRunner in
> the test-control module for junit4?
> {{Especially the feature of the DynamicMockManager that allows you to add
> mocks on per test basis is pretty nice for testing.}}
> {{This would be highly appreciated. }}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1374) Site has no reference to the release of version 1.9.0
[ https://issues.apache.org/jira/browse/DELTASPIKE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800542#comment-16800542 ] ASF subversion and git services commented on DELTASPIKE-1374: - Commit 1c72e46de94421a1cb4458ff4511ba8f956b2ebb in deltaspike's branch refs/heads/master from Daniel Dias [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=1c72e46 ] DELTASPIKE-1374: fix version to 1.9.0 > Site has no reference to the release of version 1.9.0 > - > > Key: DELTASPIKE-1374 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1374 > Project: DeltaSpike > Issue Type: Bug > Components: Documentation >Affects Versions: 1.9.0 >Reporter: Daniel Dias >Priority: Major > Fix For: 1.9.1 > > Attachments: DELTASPIKE-1374.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > 1 - In main page still has 1.8.2 ([https://deltaspike.apache.org/)] > 2 - In Dowload page too ([https://deltaspike.apache.org/download.html)] > 3 - here too (https://deltaspike.apache.org/documentation/configure.html) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [deltaspike] tandraschko commented on issue #83: Fix wrong JDK version in README.md.
tandraschko commented on issue #83: Fix wrong JDK version in README.md. URL: https://github.com/apache/deltaspike/pull/83#issuecomment-476132577 Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [deltaspike] tandraschko merged pull request #83: Fix wrong JDK version in README.md.
tandraschko merged pull request #83: Fix wrong JDK version in README.md. URL: https://github.com/apache/deltaspike/pull/83 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Resolved] (DELTASPIKE-1374) Site has no reference to the release of version 1.9.0
[ https://issues.apache.org/jira/browse/DELTASPIKE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Andraschko resolved DELTASPIKE-1374. --- Resolution: Fixed > Site has no reference to the release of version 1.9.0 > - > > Key: DELTASPIKE-1374 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1374 > Project: DeltaSpike > Issue Type: Bug > Components: Documentation >Affects Versions: 1.9.0 >Reporter: Daniel Dias >Priority: Major > Fix For: 1.9.1 > > Attachments: DELTASPIKE-1374.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > 1 - In main page still has 1.8.2 ([https://deltaspike.apache.org/)] > 2 - In Dowload page too ([https://deltaspike.apache.org/download.html)] > 3 - here too (https://deltaspike.apache.org/documentation/configure.html) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [deltaspike] tandraschko closed pull request #75: DELTASPIKE-1299: fixed orderby item order
tandraschko closed pull request #75: DELTASPIKE-1299: fixed orderby item order URL: https://github.com/apache/deltaspike/pull/75 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Resolved] (DELTASPIKE-1372) Test-Control module has a undeclared and undocumented de-facto runtime dependency on core-impl
[
https://issues.apache.org/jira/browse/DELTASPIKE-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko resolved DELTASPIKE-1372.
---
Resolution: Fixed
Fix Version/s: 1.9.1
> Test-Control module has a undeclared and undocumented de-facto runtime
> dependency on core-impl
> --
>
> Key: DELTASPIKE-1372
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1372
> Project: DeltaSpike
> Issue Type: Bug
> Components: TestControl
>Affects Versions: 1.9.0
>Reporter: Juri Berlanda
>Priority: Major
> Fix For: 1.9.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When setting up Test-Control Module like described in
> [http://deltaspike.apache.org/documentation/test-control.html] I end up with:
> {{java.lang.ExceptionInInitializerError}}
> {{ at
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner.(CdiTestRunner.java:87)}}
> {{ at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)}}
> {{ at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)}}
> {{ at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)}}
> {{ at
> org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:33)}}
> {{ Caused by: java.lang.RuntimeException: Could not load ConfigProvider}}
> {{ at
> org.apache.deltaspike.core.api.config.ConfigResolver.getConfigProvider(ConfigResolver.java:628)}}
> {{ at
> org.apache.deltaspike.core.api.config.ConfigResolver.resolve(ConfigResolver.java:613)}}
> {{ at
> org.apache.deltaspike.testcontrol.api.junit.TestBaseConfig$ContainerIntegration.(TestBaseConfig.java:29)}}
> {{ ... 15 more}}
> The reason is, that {{deltaspike-core-impl}} is missing on the classpath.
> Adding it solves the problem.
> So imho. we should add a {{runtime}} dependency on {{deltaspike-core-impl}}
> to {{deltaspike-test-control-module-impl}}. It should be a matter of
> replacing {{test}} to {{runtime}} on
> {{deltaspike-core-impl}} in {{deltaspike-test-control-module-impl}}'s
> {{pom.xml}}.
> I'll create a pull-request doing exactly that in a moment.
> EDIT: Pull-request exists at https://github.com/apache/deltaspike/pull/86
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DELTASPIKE-1375) Correctly spell futurable
Thomas Andraschko created DELTASPIKE-1375: - Summary: Correctly spell futurable Key: DELTASPIKE-1375 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1375 Project: DeltaSpike Issue Type: Improvement Reporter: Thomas Andraschko Assignee: Thomas Andraschko Fix For: 1.9.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (DELTASPIKE-1369) [Scheduler] Enable/Disable based on custom condition
[
https://issues.apache.org/jira/browse/DELTASPIKE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko resolved DELTASPIKE-1369.
---
Resolution: Fixed
Fix Version/s: 1.9.1
Looks like already applied
> [Scheduler] Enable/Disable based on custom condition
>
>
> Key: DELTASPIKE-1369
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1369
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Scheduler
>Reporter: Juri Berlanda
>Priority: Major
> Fix For: 1.9.1
>
>
> As discussed on the mailing list, I propose to introduce some kind of
> pluggable Bean, which would allow to control both whether the Scheduler as a
> whole should start, as well as to provide a hook for controlling each single
> task invocation.
> The default implementation would always return true on both, which makes sure
> the default behavior is the same as it has always been. Being a Bean, it can
> be customized via CDI mechanisms (Specializes, Alternative, etc.).
> The Bean should provide the following signature:
> {{boolean isSchedulerEnabled();}}
> {{boolean vetoJobExecution(Class);}}
> TBD:
> * Provide support for multiple implementations of {{SchedulerControl}}
> * -Better name for shouldJobBeStarted?- Found
> * -Use JobName in shouldJobBeStarted?- Not needed as discussed on mailing
> list
> Development takes place at
> [https://github.com/j-be/deltaspike/tree/scheduler-control]
> Pull request can be found at https://github.com/apache/deltaspike/pull/84
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (DELTASPIKE-1375) Correctly spell futurable
[ https://issues.apache.org/jira/browse/DELTASPIKE-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Andraschko resolved DELTASPIKE-1375. --- Resolution: Fixed > Correctly spell futurable > - > > Key: DELTASPIKE-1375 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1375 > Project: DeltaSpike > Issue Type: Improvement >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko >Priority: Major > Fix For: 1.9.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [deltaspike] tandraschko commented on issue #75: DELTASPIKE-1299: fixed orderby item order
tandraschko commented on issue #75: DELTASPIKE-1299: fixed orderby item order URL: https://github.com/apache/deltaspike/pull/75#issuecomment-476133537 Already applied This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [deltaspike] tandraschko commented on issue #76: List 'void' as valid Futureable return
tandraschko commented on issue #76: List 'void' as valid Futureable return URL: https://github.com/apache/deltaspike/pull/76#issuecomment-476133082 Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Closed] (DELTASPIKE-1355) counfByXXX failed with deltaspike and thorntail arquillian test
[
https://issues.apache.org/jira/browse/DELTASPIKE-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko closed DELTASPIKE-1355.
-
Resolution: Cannot Reproduce
No response, will close it for now.
If you can provide a reproducer, feel free to create a new issue again.
> counfByXXX failed with deltaspike and thorntail arquillian test
> ---
>
> Key: DELTASPIKE-1355
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1355
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
>Affects Versions: 1.8.2
> Environment: Windows 10 / Maven 3.5 / Java 8
>Reporter: Sylvain Bonnemaison
>Assignee: Thomas Andraschko
>Priority: Major
>
> The following Repository class is defined :
> {{@Repository public interface UserRepository extends EntityRepository Long> {}}
> {{ long countByUid(String uid);}}
> {{ Stream findByUid(String uid);}}
> {{ ...}}
> {{}}}
> {{Stackstrace :}}
> {{Caused by: org.apache.deltaspike.data.api.QueryInvocationException: Failed
> calling Repository:
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,exception=class
> org.apache.deltaspike.data.api.QueryInvocationException,message=Failed
> calling Repository:
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,
> at
> org.apache.deltaspike.data.impl.handler.QueryHandler.process(QueryHandler.java:163)
> at
> org.apache.deltaspike.data.impl.handler.QueryHandler.invoke(QueryHandler.java:130)
> at
> org.apache.deltaspike.data.impl.handler.QueryHandler$Proxy$_$$_WeldClientProxy.invoke(Unknown
> Source) at
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler.proceed(DeltaSpikeProxyInvocationHandler.java:97)
> at
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler.invoke(DeltaSpikeProxyInvocationHandler.java:78)
> at
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler$Proxy$_$$_WeldClientProxy.invoke(Unknown
> Source) at
> com.timm.demo.thorntail.deltaspike.persistence.UserRepository$$DSPartialBeanProxy.countByUid(Unknown
> Source) ... 46 more Caused by:
> org.apache.deltaspike.data.api.QueryInvocationException: Failed calling
> Repository:
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,
> at
> org.apache.deltaspike.data.impl.builder.DelegateQueryBuilder.execute(DelegateQueryBuilder.java:85)
> at
> org.apache.deltaspike.data.impl.builder.QueryBuilder.executeQuery(QueryBuilder.java:57)
> at
> org.apache.deltaspike.data.impl.builder.DelegateQueryBuilder$Proxy$_$$_WeldClientProxy.executeQuery(Unknown
> Source) at
> org.apache.deltaspike.data.impl.tx.TransactionalQueryRunner.executeNonTransactional(TransactionalQueryRunner.java:62)}}
> The findByXXX method works fine.
> Source code is on GitHub : [https://github.com/ruddy32/thorntail-deltaspike].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] [deltaspike] tandraschko merged pull request #76: List 'void' as valid Futureable return
tandraschko merged pull request #76: List 'void' as valid Futureable return URL: https://github.com/apache/deltaspike/pull/76 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [deltaspike] tandraschko merged pull request #88: DELTASPIKE-1374: fix version to 1.9.0
tandraschko merged pull request #88: DELTASPIKE-1374: fix version to 1.9.0 URL: https://github.com/apache/deltaspike/pull/88 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (DELTASPIKE-1374) Site has no reference to the release of version 1.9.0
[ https://issues.apache.org/jira/browse/DELTASPIKE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800543#comment-16800543 ] ASF subversion and git services commented on DELTASPIKE-1374: - Commit a1dece59fed4bddfecc310b9a3ae7152a1c11827 in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=a1dece5 ] Merge pull request #88 from Daniel-Dos/fix-deltaspike-version DELTASPIKE-1374: fix version to 1.9.0 > Site has no reference to the release of version 1.9.0 > - > > Key: DELTASPIKE-1374 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1374 > Project: DeltaSpike > Issue Type: Bug > Components: Documentation >Affects Versions: 1.9.0 >Reporter: Daniel Dias >Priority: Major > Fix For: 1.9.1 > > Attachments: DELTASPIKE-1374.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > 1 - In main page still has 1.8.2 ([https://deltaspike.apache.org/)] > 2 - In Dowload page too ([https://deltaspike.apache.org/download.html)] > 3 - here too (https://deltaspike.apache.org/documentation/configure.html) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1375) Correctly spell futurable
[ https://issues.apache.org/jira/browse/DELTASPIKE-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800548#comment-16800548 ] ASF subversion and git services commented on DELTASPIKE-1375: - Commit 8ed131eac40d598ba630ec9aba77569551a2db5c in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=8ed131e ] DELTASPIKE-1375 > Correctly spell futurable > - > > Key: DELTASPIKE-1375 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1375 > Project: DeltaSpike > Issue Type: Improvement >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko >Priority: Major > Fix For: 1.9.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
