rogue and rogue-field split

[John Gallagher]

Hi all,

Rogue-Field (https://github.com/foursquare/rogue-field) has gone rogue, and split into an independent project.  The maven package name and interface remains the same as before, so this should not have any impact on your use of rogue.

Why:

The Rogue-Field set of interfaces is used by Rogue, as well as Foursquare's scala code generator for Thrift, Spindle (https://github.com/foursquare/spindle). Rogue-Field is updated infrequently, so breaking out Rogue-Field allows the rest of Rogue to iterate without having to keep Spindle up to date.  It will also allow us to do something like create a Spindle adapter for Rogue, while keeping the package dependency structure clear.

What this means for you:

The code of Rogue-Field is still the same.  The maven and scala package names are the same.  The only thing that will change is that Rogue-Field will have a different (slower) release cycle.

As a result, your code will stay the same, but your library dependencies in sbt will change slightly to look like the following:

val rogueField = "com.foursquare" %% "rogue-field" % "2.2.1"

val rogueCore = "com.foursquare" %% "rogue-core" % myLatestRogueVersion 

val rogueLift =   "com.foursquare" %% "rogue-lift"   % myLatestRogueVersion 

... etc, with Rogue-Field's version being relatively constant, and independent from the rest of Rogue.

The Installation section of README.md for Rogue will keep you up to date on the correct version of Rogue-Field.

Rogue-Field 2.2.0 and 2.2.1 are identical, the only difference is that Rogue-Field 2.2.1 is published from the new repository, and is likely the last version of Rogue-Field for awhile.

John