[JBoss JIRA] (ISPN-7458) Publish modules for Hibernate Search integration with both WildFly main version and latest upstream
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-7458?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero updated ISPN-7458:
----------------------------------
Summary: Publish modules for Hibernate Search integration with both WildFly main version and latest upstream (was: Publish modules for Hibernate Search integrationw with both WildFly main version and latest upstream)
> Publish modules for Hibernate Search integration with both WildFly main version and latest upstream
> ---------------------------------------------------------------------------------------------------
>
> Key: ISPN-7458
> URL: https://issues.jboss.org/browse/ISPN-7458
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build process, Lucene Directory, WildFly modules
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Fix For: 9.0.0.CR1
>
>
> Currently the Lucene Directory module is packaged for two use cases:
> - Hibernate Search (integrating with the relational databases) users
> - Infinispan Query users
> The Hibernate Search version being targeted has typically been the "main" slot from the latest WildFly release. Occasionally we'd target the latest Hibernate Search release *instead* depending on how old the version in WildFly would be.
> I'm changing this now to actually build the module for both use cases; so that no user is left behind. Occasionally we'll have to disable one or the other, depending on divergence of versions (e.g. Lucene) we use, but at least commenting out a couple of tests should be easier than going back and forth with refactoring the whole build each year.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7455) Lucene Directory integration tests on WildFly are broken
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7455?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7455:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Lucene Directory integration tests on WildFly are broken
> --------------------------------------------------------
>
> Key: ISPN-7455
> URL: https://issues.jboss.org/browse/ISPN-7455
> Project: Infinispan
> Issue Type: Task
> Components: Build process, WildFly modules
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Fix For: 9.0.0.CR1
>
>
> The following tests are broken as they need overrides of version when running on WildFly:
> {noformat}
> SearchNewEntityJmsMasterSlaveUsingInfinispanAs2ndCacheAndModulesIT.org.infinispan.test.integration.as.jms.SearchNewEntityJmsMasterSlaveUsingInfinispanAs2ndCacheAndModulesIT
> SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT.org.infinispan.test.integration.as.jms.infinispan.SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT
> InfinispanModuleMemberRegistrationIT.org.infinispan.test.integration.as.wildfly.InfinispanModuleMemberRegistrationIT
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7458) Publish modules for Hibernate Search integrationw with both WildFly main version and latest upstream
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7458?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7458:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Publish modules for Hibernate Search integrationw with both WildFly main version and latest upstream
> ----------------------------------------------------------------------------------------------------
>
> Key: ISPN-7458
> URL: https://issues.jboss.org/browse/ISPN-7458
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build process, Lucene Directory, WildFly modules
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Fix For: 9.0.0.CR1
>
>
> Currently the Lucene Directory module is packaged for two use cases:
> - Hibernate Search (integrating with the relational databases) users
> - Infinispan Query users
> The Hibernate Search version being targeted has typically been the "main" slot from the latest WildFly release. Occasionally we'd target the latest Hibernate Search release *instead* depending on how old the version in WildFly would be.
> I'm changing this now to actually build the module for both use cases; so that no user is left behind. Occasionally we'll have to disable one or the other, depending on divergence of versions (e.g. Lucene) we use, but at least commenting out a couple of tests should be easier than going back and forth with refactoring the whole build each year.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-6038) ClientAsymmetricClusterTest.testAsymmetricCluster random failures
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6038?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6038:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> ClientAsymmetricClusterTest.testAsymmetricCluster random failures
> -----------------------------------------------------------------
>
> Key: ISPN-6038
> URL: https://issues.jboss.org/browse/ISPN-6038
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols, Test Suite - Server
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Priority: Minor
> Labels: testsuite_stability
> Fix For: 9.0.0.CR1
>
>
> {{ClientAsymmetricClusterTest.testAsymmetricCluster}} is failing since the ISPN-5981 fix, which enabled {{pingOnStartup}} by default, and now returns {{null}} if the first server to be pinged doesn't have the cache defined.
> {noformat}
> 10:23:07,862 WARN (testng-ClientAsymmetricClusterTest:) [Codec21] ISPN004005: Error received from the server: org.infinispan.server.hotrod.CacheNotFoundException: Cache with name 'asymmetricCache' not found amongst the configured caches
> 10:23:07,862 ERROR (testng-ClientAsymmetricClusterTest:) [UnitTestTestNGListener] Test testAsymmetricCluster(org.infinispan.client.hotrod.ClientAsymmetricClusterTest) failed.
> java.lang.NullPointerException
> at org.infinispan.client.hotrod.ClientAsymmetricClusterTest.testAsymmetricCluster(ClientAsymmetricClusterTest.java:38) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7425) Enable admins to delete configuration subsections
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7425?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7425:
--------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Enable admins to delete configuration subsections
> -------------------------------------------------
>
> Key: ISPN-7425
> URL: https://issues.jboss.org/browse/ISPN-7425
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 9.0.0.Beta2
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.CR1
>
>
> We need to add the ability to remove configuration subsections (locking, expiration etc) and make it consistent across configuration screens.
> UI perspective: We could have a delete icon (red cross or trash can etc) in the "panel-title" div of the section that a user is editing. If the user chooses to delete this sections config, then they should be presented with a message screen saying "<section> has not been defined, would you like to define this now?" similar to how we ask users to define container security when they click on the security section. Similarly, if a user loads an existing config with a section undefined, the aforementioned message should be displayed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month