1.4.0

Core

Bugs

• Header added twice (#312)

1.2.1

Core

Bugs

• Header added twice (#289, #290)

1.4-beta1

This release is designed for Play 2.4.0 and more and is not compatible with Play 2.3.x and less.

Plugin

Enhancements

• Compatibility with Play 2.4.0 (#278)

1.3-beta3

This release is designed for Play 2.3.2 and more and is not compatible with Play 2.3.0 to 2.3.2.

Plugin

Enhancements

• Compatibility with Play 2.3.8 (#280, #281)

1.3-beta2

This release is designed for Play 2.3.2 and more and is not compatible with Play 2.3.0 and 2.3.1.

Plugin

Enhancements

• Compatibility with Play 2.3.2 and more series (#259)

1.3-beta1

Plugin

Enhancements

• Compatibility with Play 2.3 series (#247)

v1.2

Play2War 1.2 contains the follwing main enhancements:

• Compatibility with Play 2.2 is out of beta
• Use of servlet 3.1 features (async IO) on 3.1 Servlet containers

Plugin

Enhancements

• Compatibility with Play 2.2.x series (#188)

Bugs

• Project's JAR can be packaged exploded in final WAR again (#224)
• Custom MANIFEST.MF in war/ subdirectory prevents build from completing (#216)

Core

Enhancements

• Compatibility with Play 2.2.x series (#188)
• Use asynchronous IO on 3.1 Servlet containers (#95, #235, #239, #243)
• Various enhancements (#244, #245, #248)

v1.0.2

Plugin

• Bugs
  • Unmanaged dependencies are not included in the WAR (#189)
  • Custom MANIFEST.MF in war/ subdirectory prevents build from completing (#215, #208)

v1.2-beta4

Play2war 1.2.x series will be dedicated to Play 2.2. This is the 4th release compatible with Play 2.2.

This version is not compatible with Play 2.0.x or 2.1.x series anymore.

Plugin

• Bugs
  • The root project jar is packaged as jar twice (#205)
  • Custom MANIFEST.MF in war/ subdirectory prevents build from completing (#216)

Don't look for 1.2-beta3 version, it has been "lost" ;-)

v1.2-beta2

Play2war 1.2.x series will be dedicated to Play 2.2. This is the 2nd release compatible with Play 2.2, much more stable.

This version is not compatible with Play 2.0.x or 2.1.x series anymore.

Details of compatibility status can be seen in issue #188.

No known bug.