What’s new in Play 2.3
Introducing the activator command. You can use activator exactly like you would use play, but Activator brings new features too. (More about the Activator change.)
Better tooling for static assets. Play now uses sbt-web which gives faster asset processing, more features, and better extensibility.
Support for Java 8 (and continued support for Java 6 and 7).
Better Java performance. Simple Java controllers give 40–90% better throughput. (Thanks to YourKit for sponsoring licenses.)
Support for Scala 2.11 (and continued support for Scala 2.10).
Anorm enhancements: SQL string interpolation, multi-value parameters, new types, and more.
Web Services enhancements: separate client, SSL configuration, and more.
Play templates have become Twirl templates: separate project, new sbt plugin, still excellent integration with Play
Actors for WebSockets
Custom SSLEngine for HTTPS
Asset performance: faster serving, better caching.
One Result to rule them all: all the result types which were deprecated in 2.2 are now gone and only Result remains.
Lots of bug fixes. :)
For details see the Play 2.3 Highlights and the Play 2.3 Migration Guide.
Download Play 2.3
Play is now distributed through Activator. Visit the Play downloads page for information on how to download and install Activator, and get started with Play.
We would like in particular to thank the community for the many contributions made. A bit of git number crunching tells us that 168 unique contributors were involved in Play 2.3.x, and 132 of those had not contributed to Play before. This brings us to an all time total of 365 unique contributors to Play!
Fantastic! Can't wait to upgrade.
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Awesome, thanks for your great work!
--
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Anyway that's the goal, but it's a good point about being potentially confusing. What do you think we should do? E.g. one idea would be to provide an alias to activator called play.
Having one bloated executable that contains every possible feature is not the way to go. Activator is more than 100MB larger than Play was. It should be modularized, with dynamically loaded modules, or versions with various features provided.
Anyway that's the goal, but it's a good point about being potentially confusing. What do you think we should do? E.g. one idea would be to provide an alias to activator called play.
Thanks,
Mike
I'd like to suggest tweaking priorities:
- De-emphasize the importance of delivering big releases according to a demanding schedule. Instead focus on quality, integration, documentation and usability.
- More point releases, tuning work that has been done, less major releases with breaking features.
- More time spent planning and communicating; the current situation is a textbooks case that illustrates what happens when product management is lacking. We've got a mess at this time, with products (Scala 2.10/11, Slick and Play) that do not work effectively together.
- More engagement with community re. potential roadmaps
- More transparency and public accountability in the planning process; yes, being accountable to users should be a goal.
- Curated release notes
- Coordinated release schedule with Scala compiler and Slick.
- Fewer new features; make them really count and plan ahead so new or modified features rarely break functionality. My top wish list items are:
- Much better Slick integration (Play and Slick developers should work as one team). The Play community is Slick's biggest user base, so the needs of Play should be a major driver of the Slick roadmap.
- Overcome all arity 22 issues (which means supporting > 18 fields/form)
- Strong focus on testability of Play projects
Thanks,
Mike
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Rich
...<p dir="
The Play team is pleased to announce the release of Play 2.3.0!
What’s new in Play 2.3
Introducing the activator command. You can use activator exactly like you would use play, but Activator brings new features too. (More about the Activator change.)
Better tooling for static assets. Play now uses sbt-web which gives faster asset processing, more features, and better extensibility.
Support for Java 8 (and continued support for Java 6 and 7).
Better Java performance. Simple Java controllers give 40–90% better throughput. (Thanks to YourKit for sponsoring licenses.)
Support for Scala 2.11 (and continued support for Scala 2.10).
Anorm enhancements: SQL string interpolation, multi-value parameters, new types, and more.
Web Services enhancements: separate client, SSL configuration, and more.
Play templates have become Twirl templates: separate project, new sbt plugin, still excellent integration with Play
Actors for WebSockets
Custom SSLEngine for HTTPS
Asset performance: faster serving, better caching.
One Result to rule them all: all the result types which were deprecated in 2.2 are now gone and only Result remains.
Lots of bug fixes. :)
For details see the Play 2.3 Highlights and the Play 2.3 Migration Guide.
Download Play 2.3
Play is now distributed through Activator. Visit the Play downloads page for information on how to download and install Activator, and get started with Play.
We would like in particular to thank the community for the many contributions made. A bit of git number crunching tells us that 168 unique contributors were involved in Play 2.3.x, and 132 of those had not contributed to Play before. This brings us to an all time total of 365 unique contributors to Play!
Thanks,
The Play Team
Nice! I'm eager to try the new asset pipeline... But first: Has any of this been tested on Windows yet? :-)
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Play supports Windows but I will admit that we do rely a little more on end users to test Windows than we do on other platforms. I've recently looked at Codeship to provide CI on Windows but it needs more investigation.
I released this in activator 1.2.2 yesterday (AFAIK)
Thanks chanan..will try that..the existing play framework Jenkins plugin doesn't seem to work with play 2.3.
> --
> You received this message because you are subscribed to a topic in the Google Groups "play-framework" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/play-framework/bTvJbeR_zvU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to play-framewor...@googlegroups.com.
New features are always welcome... but after 7 years change play command to activator is not good.
This would make deprecated all available documentation regarding previous releases (online and books).
It's like Oracle changing "java.exe" to "activator-java.exe".
If the idea is to promote the activator, it should be another way to do it.
changing fundamental components like how to start the application
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
Epoch is for massive architectural changes = weeks to upgrade.Major is for incompatible changes that = days to upgrade.Minor is for bug fixes = hours to upgrade.Play 2.2 to 2.3 should not be expected to be a seamless upgrade.
On Thursday, June 19, 2014 5:30:22 AM UTC-7, James Ward wrote:Epoch is for massive architectural changes = weeks to upgrade.Major is for incompatible changes that = days to upgrade.Minor is for bug fixes = hours to upgrade.Play 2.2 to 2.3 should not be expected to be a seamless upgrade.
I think the scope of the changes for the 2.3 release was reasonable. However, some suggestions:
- Deprecate features at least one major release before removing them.
- Release bug fixes as soon they are ready, not once every few months.
> Somehow, we have to find a way to differentiate between our paidI think the business model is flawed if you have to keep _important_ fixes from being applied to the current branch in order to keep the cash flowing.
> subscription and the open source offerings, if we give identical service to
> both our paying customers and the open source community, then no one
> in their right mind would become a paying customer [...]
But I appreciate the fact that I can pull the latest fixes from a branch and publish into my local maven repo if I don't have a subscription.
For example, is the new netty release, with the important SSL updates, going to be available on the 2.3 branch any time soon?
(http://netty.io/news/2014/06/11/3.html) Sure I can update the dependency in my project, but people new to Play may well expect that the latest official release available from the web site will not have known vulnerabilities. (We deploy Play behind nginx -- so not an actual issue for me in this instance.)
I think it will better serve the Play community, and in the medium term Typesafe, to have shorter release cycles and to ensure that new people to Play don't encounter problems that are already solved.
This business problem is not new and all open source with paid support option projects have to deal with it. So I don't mean to single out Typesafe as worse than anyone else. And in many ways, Typesafe is better than many...
my 2c and all that...
On Tuesday, 24 June 2014 08:21:50 UTC+10, Eric Jain wrote:On Sun, Jun 22, 2014 at 11:21 PM, James Roper <james...@typesafe.com> wrote:
> I don't think there was anything deleted from 2.3 that wasn't deprecated in
> 2.2, if you have an example, please let us know.
Was minification of (non-rjs) js assets deprecated in 2.2?
> Somehow, we have to find a way to differentiate between our paid
> subscription and the open source offerings, if we give identical service to
> both our paying customers and the open source community, then no one
> in their right mind would become a paying customer [...]
The incentive to be a paying customer is usually to have more reliable
support than the mailing list can provide; making bugfix releases
available to paying customers only seems counterproductive.
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Sun, Jun 22, 2014 at 11:21 PM, James Roper <james...@typesafe.com> wrote:Was minification of (non-rjs) js assets deprecated in 2.2?
> I don't think there was anything deleted from 2.3 that wasn't deprecated in
> 2.2, if you have an example, please let us know.
> Somehow, we have to find a way to differentiate between our paid> in their right mind would become a paying customer [...]
> subscription and the open source offerings, if we give identical service to
> both our paying customers and the open source community, then no one
The incentive to be a paying customer is usually to have more reliable
support than the mailing list can provide; making bugfix releases
available to paying customers only seems counterproductive.
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
It sounds like you're referring to the Activator UI. The activator UI is an additional feature, the activator command works just like the play command, ie "activator run" === "play run", and both of these just delegate to "sbt run".
--
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Play 2.3 introduced breaking changes, so it would be appropriate to give it a new major version (3.0). I suggest to follow http://semver.org/. Version numbers are not a limited resource anymore! ;-)
The Play team is pleased to announce the release of Play 2.3.0!
What’s new in Play 2.3
Introducing the activator command. You can use activator exactly like you would use play, but Activator brings new features too. (More about the Activator change.)
Better tooling for static assets. Play now uses sbt-web which gives faster asset processing, more features, and better extensibility.
Support for Java 8 (and continued support for Java 6 and 7).
Better Java performance. Simple Java controllers give 40–90% better throughput. (Thanks to YourKit for sponsoring licenses.)
Support for Scala 2.11 (and continued support for Scala 2.10).
Anorm enhancements: SQL string interpolation, multi-value parameters, new types, and more.
Web Services enhancements: separate client, SSL configuration, and more.
Play templates have become Twirl templates: separate project, new sbt plugin, still excellent integration with Play
Actors for WebSockets
Custom SSLEngine for HTTPS
Asset performance: faster serving, better caching.
One Result to rule them all: all the result types which were deprecated in 2.2 are now gone and only Result remains.
Lots of bug fixes. :)
For details see the Play 2.3 Highlights and the Play 2.3 Migration Guide.
Download Play 2.3
Play is now distributed through Activator. Visit the Play downloads page for information on how to download and install Activator, and get started with Play.
We would like in particular to thank the community for the many contributions made. A bit of git number crunching tells us that 168 unique contributors were involved in Play 2.3.x, and 132 of those had not contributed to Play before. This brings us to an all time total of 365 unique contributors to Play!
Thanks,
The Play Team
--James Roper
Software Engineer
Hi, I think u can help me to solve my issues. I am using Play 2.2.6. I am unable to create a executable jar. I used dist command to package as a jar. But that jar does not contains lib folders for dependent Jars.