[JBoss JIRA] (ISPN-6818) Ensure that embedded mode compiles and runs with Java 9
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-6818?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-6818:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.0.Alpha3
Resolution: Done
> Ensure that embedded mode compiles and runs with Java 9
> -------------------------------------------------------
>
> Key: ISPN-6818
> URL: https://issues.jboss.org/browse/ISPN-6818
> Project: Infinispan
> Issue Type: Task
> Components: Build process, Core
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.0.0.Alpha3, 9.0.0.Final
>
>
> In order for Infinispan (embedded) to compile and run with Java 9, we need to at least do the following:
> - Upgrade to JBoss Marshalling 1.4.11
> - Remove usage of Javassist, including the maven-injection-plugin
> - Use special compiler flags to ensure that special modules are enabled (java.annotations.common)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (ISPN-6835) Improve user guide section "The Problem of Caching Arrays"
by Dan Berindei (JIRA)
Dan Berindei created ISPN-6835:
----------------------------------
Summary: Improve user guide section "The Problem of Caching Arrays"
Key: ISPN-6835
URL: https://issues.jboss.org/browse/ISPN-6835
Project: Infinispan
Issue Type: Task
Components: Documentation-Servers
Affects Versions: 9.0.0.Alpha2
Reporter: Dan Berindei
Priority: Minor
We should make it clear that a proper implementation of equals() and hashCode() is always required for keys, but it's only necessary for values if one intends to use conditional operations.
The section should also say more about how Infinispan uses equals() and hashCode() and what our requirements are, instead of how "users would like to call" one method or another.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (ISPN-6834) Add Google Analytics tracker to guides
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-6834:
-------------------------------------
Summary: Add Google Analytics tracker to guides
Key: ISPN-6834
URL: https://issues.jboss.org/browse/ISPN-6834
Project: Infinispan
Issue Type: Sub-task
Components: Documentation-Core
Reporter: Tristan Tarrant
The documentation generated from the infinispan repository doesn't contain the google analytics tracker.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (ISPN-6832) Proof of correctness for complex distributed patterns
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-6832?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec updated ISPN-6832:
--------------------------------------
Component/s: Core
> Proof of correctness for complex distributed patterns
> -----------------------------------------------------
>
> Key: ISPN-6832
> URL: https://issues.jboss.org/browse/ISPN-6832
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Reporter: Sebastian Łaskawiec
>
> The core of Infinispan can be represented in very simple "primitives": a set of nodes send messages to each other. The fundamental rules are also relatively simple:
> * a message can't be received before it's sent
> * a message could be lost
> * a node could be killed at any time
> From these basic building blocks one can start building some logical consequences:
> * messages sent to multiple nodes might arrive at different times
> * multiple messages sent to multiple nodes might be delivered in different order
> Some of these problems are resolved by JGroups - but even then it must be configured accordingly, meaning Infinispan' s usage of it is sensible to using the wrong method or flags.
> While the Java/Scala code in Infinispan is not overly complex, it's not suited for reasoning on the consequences of often-needed changes in the codebase. It would be very useful to be able to define patterns in an ad-hoc meta language, and provide a proof correctness of the patterns it uses, or at least proof the events it should avoid can not happen.
> A great help for the project would be to sketch such a language and try it out on some of the distribution schemes Infinispan uses to proof they are correct or identify flaws in correctness. In a second step (optional) one could build some tooling around this to provide automatic demonstration / simulation for proposed changes expressed in this meta language.
> The Promela language could be used for this purpose; so one could build tooling around it, try to apply it on Infinispan, and possibly work on ad-hoc extesions.
> See also previous proposal: "Visualization and tracing of messages between nodes" -> that would make it possible to trace the real Infinispan behaviour and then demonstrate it's correctness or identify problems before they happen.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months