All Versions
Latest Version
Avg Release Cycle
43 days
Latest Release
2896 days ago

Changelog History
Page 3

  • v1.0.0 Changes

    • Name changed from Content Manager to RoboSpice
    • published on Github
    • published on Maven Central
  • v0.0.13 Changes

    • ๐Ÿ‘ป minor enhancement of simple requests, exception stack traces were lost.
  • v0.0.12 Changes

    • back to previous dependency injection model inside services.
    • content manager is now more robust and more stable
    • โฌ‡๏ธ dropped the idea of integrating AsyncTasks into the framework.
    • minor enhancements.
  • v0.0.11 Changes

    • ๐Ÿ”ง configuration is now entirely mavenized. No libs folder anymore, every dependency is controlled by maven. Most dependencies are standard although some of the android dependencies are still missing in maven, in that case, developpers will have to create them through mvn import-file goal. ๐Ÿ”ง content-manager-it, the test app can't be used under eclipse yet (as the android configurator is not ready yet) : devs should disable maven nature and add the sample ๐Ÿ— as a project in the test app java build path.
    • various attempts have been made to enable canceling a spring android request but that failed. It's not possible and won't be possible in a near future to cancel a request ๐Ÿ‘ that has started its network connection. That's a real concern but spring android doesn't support this feature yet.
    • ๐Ÿš€ mostly released for Samy to give content manager a circuit run.
  • v0.0.10 Changes

    • ๐Ÿš€ revisited maven configuration for deployment
  • v0.0.9 Changes

    • life cycle of the ContentManager has improved
    • ๐Ÿ’ป InputStream based requests had a logical problem : they were processing InputStream on the UI Thread, and that is prohibited as of HoneyComb (and a bad practice), they now process the network stream in the background and offer either a memory stream or file stream to be processed by listeners (who can still delegate the processing to an asynctask for buttering).
    • Injection Dependency changed to some more standard option : developpers will have to create an Application Class that will provide ContentService instances all their required dependencies.
  • v0.0.8 Changes

    • AndroidManifest check. ContentManager will get sure a ContentService has been declared in manifest
  • v0.0.6 Changes

    • ๐Ÿš€ changed deploy url
  • v0.0.5 Changes

    • async operations for ObjectPersisters are available (and optional)
    • ๐Ÿ”จ persistence layer cleaning, refactoring and renaming
    • โž• added BigInputStream and SmallInputStream requests
    • โž• added README
    • โœ… testing
    • more cache cleaning methods
    • โœ‚ removed roboguice dependency :(
    • split of spring android and json modules
  • v0.0.4 Changes

    • first maven and jenkins integrations
    • renaming of maven artefacts
    • ๐Ÿš€ nexus deployment
    • local service binding
    • โœ‚ removed all bundlization stuff