Clone Tools
  • last updated a few minutes ago
Constraints: committers
Constraints: files
Constraints: dates
ISPN-4008 Rename cli-server to a more meaningful cli-interpreter

  1. … 149 more files in changeset.
ISPN-4063 Remove Infinispan 5.2.x compatibility code

  1. … 125 more files in changeset.
Undo lost comments and CDATA sections from POM introduced by maven-release-plugin during 6.0.1 release

  1. … 26 more files in changeset.
Change version to 7.0.0-SNAPSHOT

  1. … 64 more files in changeset.
'Release Script: update versions for 6.0.2-SNAPSHOT'

  1. … 66 more files in changeset.
ISPN-3712 Pull in the optional compatibility package so that the CLI upgrade test passes

'Release Script: update versions for 6.0.1-SNAPSHOT'

  1. … 54 more files in changeset.
ISPN-3569 Remove spurious server dependencies from RemoteCacheStore and CLI server

  1. … 1 more file in changeset.
ISPN-3458 Move the HotRod target migrator to the remotecachestore - Also drop the upgrade-tools module as its become useless now

  1. … 13 more files in changeset.
Update name of infinispan-cli-server module to prevent potential confusion with the query DSL

  1. … 4 more files in changeset.
ISPN-3185 License and copyright header update

  1. … 3170 more files in changeset.
changed release number on master to 6.0.0-SNAPSHOT

  1. … 49 more files in changeset.
Modified versions in pom.xml files to 5.3.0-SNAPSHOT

  1. … 45 more files in changeset.
ISPN-2785 Complete the CLI server codecs implementations

  1. … 8 more files in changeset.
ISPN-2326 c3p0 not part of the release

* c3p0 dependency was ignored by maven assembly plugin because this dependency is referenced by multiple modules, in multiple scopes (including test scope). The processing order of modules (and their dependencies) becomes important because only the first one is considered, so if that happens to have 'test' scope it won't make it into the distro. This is a consequence of a broader issue/limitation that is already documented in the plugin user guide and to overcome it we should avoid multiple moduleSets (not doable). The current solution consists of adding a FIRST moduleSet that aggregates all jar deps in 'proper' order and removing dependency processing from existing moduleSets.

* Made some trivial changes in bin.xml assembly to reduce the amount of text differences to all.xml (bin.xml is a subset of all.xml and any irrelevant differences should go away to simplify maintaining them in parallel)

* Force dependency resolution for commons-codec and commons-collections to use a global common version (otherwise they would diverge)

* Remove some duplicated dependencies in spring/pom.xml and cli-server/pom.xml.

  1. … 6 more files in changeset.
ISPN-2606 Implement UpgradeSynchronizer as MBean

  1. … 29 more files in changeset.
ISPN-2524: Implement a method for wrapping keys/values appropriately for the container ISPN-2668: Remove the putifabsent command in favour of an --ifabsent option to the put command

  1. … 40 more files in changeset.
ISPN-1453: Infinispan CLI

  1. … 114 more files in changeset.