[JBoss JIRA] (ISPN-8125) Refactor server to utilise wildfly-core
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8125?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8125:
----------------------------------
Fix Version/s: 9.3.0.Final
(was: 9.2.0.Final)
> Refactor server to utilise wildfly-core
> ---------------------------------------
>
> Key: ISPN-8125
> URL: https://issues.jboss.org/browse/ISPN-8125
> Project: Infinispan
> Issue Type: Sub-task
> Components: Server
> Affects Versions: 9.1.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.3.0.Final
>
>
> The current server is based upon the full wildfly distribution which includes many dependencies/components that are not required by Infinispan. Therefore, we should aim to refactor the server based upon wildfly-core. This will provide users with the existing standalone/domain operating modes and DMR operations that they're accustomed to, but without the overhead of additional JavaEE dependencies that aren't used.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-8124) Create Lean Infinispan Server
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8124?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8124:
----------------------------------
Fix Version/s: 9.3.0.Final
(was: 9.2.0.Final)
> Create Lean Infinispan Server
> -----------------------------
>
> Key: ISPN-8124
> URL: https://issues.jboss.org/browse/ISPN-8124
> Project: Infinispan
> Issue Type: Sub-task
> Components: Server
> Affects Versions: 9.1.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.3.0.Final
>
>
> We need to create an infinispan server that utilises the minimum number of dependencies during run time. This is in order to reduce the server's memory footprint as much as possible. The resulting server will have the following characteristics:
> * Based upon jboss-modules
> * Compatible with existing standalone configuration
> * Expose management operations via Jolokia
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-8241) Refactor RocksDB clearThreshold
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8241?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8241:
----------------------------------
Fix Version/s: 9.3.0.Final
(was: 9.2.0.Final)
> Refactor RocksDB clearThreshold
> -------------------------------
>
> Key: ISPN-8241
> URL: https://issues.jboss.org/browse/ISPN-8241
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 9.1.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.3.0.Final
>
>
> Currently the RocksDB store utilises a "clearThreshold" to try to delete entries individually before deleting and re-initiating the database. We should deprecate this threshold and always delete/reinit the database.
> Currently when deleting the database, we utilise Util.recursiveFileRemove which does not confirm that the file has actually been deleted. Instead, we should provide a nio based implementation instead, similar to the one stated [here|https://stackoverflow.com/questions/779519/delete-directories-recurs...]. This has the advantage that an IOException is thrown by java.nio.file.Files::delete
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-8356) Embedded distribution names are confusing
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8356?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8356:
----------------------------------
Fix Version/s: 9.3.0.Final
(was: 9.2.0.Final)
> Embedded distribution names are confusing
> -----------------------------------------
>
> Key: ISPN-8356
> URL: https://issues.jboss.org/browse/ISPN-8356
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Affects Versions: 9.1.1.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.3.0.Final
>
>
> The binary distribution names for embedded libraries are confusing:
> I propose the following names
>
> - infinispan-${version}-all.zip -> infinispan-embedded-${version}-all.zip
> - infinispan-${version}-minimal.zip -> infinispan-embedded-${version}-minimal.zip
> - infinispan-${version}-remote.zip -> infinispan-remote-${version}.zip
> The website labelling needs to be modified accordingly too
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-8320) Javadoc comments contain malformed HTML
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8320?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8320:
----------------------------------
Fix Version/s: 9.3.0.Final
(was: 9.2.0.Final)
> Javadoc comments contain malformed HTML
> ---------------------------------------
>
> Key: ISPN-8320
> URL: https://issues.jboss.org/browse/ISPN-8320
> Project: Infinispan
> Issue Type: Bug
> Components: Documentation-Core
> Affects Versions: 9.1.0.Final
> Reporter: Dan Berindei
> Priority: Trivial
> Fix For: 9.3.0.Final
>
>
> In Java 8, {{javadoc}} started reporting malformed HTML tags in Javadoc comments. Our distribution build is ignoring the errors, and the normal build doesn't generate Javadoc at all. However, invoking {{mvn javadoc:javadoc}} directly fails:
> {noformat}
> [INFO] [ERROR] Exit code: 1 - /home/dan/Work/infinispan/target/checkout/checkstyle/src/main/java/org/infinispan/checkstyle/filters/ExcludeTestPackages.java:17: error: malformed HTML
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months