[2.0] play 2.0.3

Showing 1-18 of 18 messages
[2.0] play 2.0.3 peter hausel 8/3/12 6:07 AM
Hi all,

We are pleased to announce the availability of play 2.0.3

highlights:
--------------
- introduce ExternalAssets controller (useful in dev mode when one needs to deal with lots of assets)
- switch date handling in Assets controller to Joda Time
- switch time zone in Assets controller from UTC to GMT 
- make date parsing in Assets controller more resilient  
- Global.onStop is now invoked properly in prod mode

2.0.3 milestone in Lighthouse:
------------------------------------------

how to upgrade:
----------------------
download play-2.0.3.zip from http://www.playframework.org/download

or change the play version in project/plugin.sbt to 2.0.3

compatibility:
-----------------
this release is fully compatible with 2.0.2

Let us know what you think!

Happy playin'!


Play Team

Re: [play-framework] [2.0] play 2.0.3 Mariot Chauvin 8/3/12 6:30 AM
Hi Peter,

Thanks for this new version !

Quick question about the archive size, is the repository/cache folder of about 100 MB expected ?

Regards,

Mariot

2012/8/3 peter hausel <peter....@gmail.com>

--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/YiefRedLKlUJ.
To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/play-framework?hl=en.

Re: [play-framework] [2.0] play 2.0.3 peter hausel 8/3/12 6:41 AM
Hi Mariot, the difference is that framework/sbt/boot is now part of the archive  (which directory would have been created and filled the first time you'd run the play console).As far as I could tell this would save the time to populate sbt/boot, but I will double check if it's actually buying us anything (if not, I will remove it). Either way, it's not causing any trouble.
Re: [2.0] play 2.0.3 bulupe 8/3/12 6:42 AM
Hello,

We are having problems while setting headers for promises and WS results, is this issue addressed in 2.0.3?

Thank you
Re: [play-framework] [2.0] play 2.0.3 Mariot Chauvin 8/3/12 6:52 AM
Thanks for the explanation.

2012/8/3 peter hausel <peter....@gmail.com>
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/IhDRVNXz2t4J.

To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/play-framework?hl=en.

Re: [2.0] play 2.0.3 peter hausel 8/3/12 7:02 AM
Please see https://play.lighthouseapp.com/projects/82401-play-20/milestones/150181-203 for more details.
Re: [2.0] play 2.0.3 bulupe 8/3/12 7:02 AM
Hello,

I have tested and it is still not possible to set headers for async result;

Code Not working 1:

     public static Result asyncResult() {
            return async(Akka.future(new Callable<String>() {
                @Override
                public String call() {
                    return "success";
                }
            }).map(new Function<String, Result>() {
                @Override
                public Result apply(String a) {
                    response().setHeader("header_test", "header_val");
                    response().setCookie("cookie_test", "cookie_val");
                    session("session_test", "session_val");
                    flash("flash_test", "flash_val");
                    return ok(a);
                };
            }));
        }

I got "[error] play - Waiting for a promise, but got an error: There is no HTTP Context available from here."


Code Not working 2:

     public static Result asyncResult() {
         final Response res = response();
            return async(Akka.future(new Callable<String>() {
                @Override
                public String call() {
                    return "success";
                }
            }).map(new Function<String, Result>() {
                @Override
                public Result apply(String a) {
                    res.setHeader("header_test", "header_val");
                    return ok(a);
                };
            }));
        }

And this time no headers set in result.


Is there any plans about this problem? I will issue a ticket in Lighthouse about this.

Thank you
Bulent


On Friday, August 3, 2012 4:07:28 PM UTC+3, peter hausel wrote:
On Friday, August 3, 2012 4:07:28 PM UTC+3, peter hausel wrote:
Re: [2.0] play 2.0.3 peter hausel 8/3/12 7:11 AM
Hi Bulent,

I can not remember off the top of my head whether this is fixed already or not (there were many changes around async and promises recently), could you please try it against master?

If it's still not working, please check if there is a ticket about this in LH already, if not please create one.

Thanks in advance.

Best,
Peter
Re: [2.0] play 2.0.3 Sean Brady 8/3/12 7:32 AM
+1 for compatibility statement! :-)
Re: [2.0] play 2.0.3 bulupe 8/3/12 8:23 AM
Thank you, I opened a ticket but there was already one opened so I linked to old one too.
Re: [2.0] play 2.0.3 Marc Carré 8/3/12 9:51 AM
Hi,

I (and some others on the web) have faced some issues with 2.0.3 when creating new projects: 
[error] play#play_2.9.1;2.0.3!play_2.9.1.jar origin location must be absolute: /Users/phausel/i/play-2.0.3/hh/../framewo
[error] {file:/C:/Apps/myFirstApp/project/}default-817509/*:update: java.lang.IllegalArgumentException: play#play_2.9.1;
Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore?
See also this post on Stackoverflow. 

It seems related to the repository\cache folder, which contains stuff that it should not contain (see also my comments here)?
Could this be confirmed (and if required, fixed)?

Is there a better way to fix it than removing the cache folder (some play command maybe)?

Thank you very much for this new version in any case! 

Cheers,

M.
Re: [2.0] play 2.0.3 peter hausel 8/3/12 10:22 AM
looking into it.
Re: [2.0] play 2.0.3 peter hausel 8/3/12 10:38 AM
Hi Marc,

apologies about the trouble!

here is the correct version, will get it uploaded this to playframework.org in a sec:

Please let me know if you still see problems.

Thanks,
Peter



On Friday, August 3, 2012 12:51:24 PM UTC-4, Marc CARRÉ wrote:
Re: [2.0] play 2.0.3 Brandyn Kusenda 8/4/12 12:58 PM
Great.  Keep up the good work.

Thanks!
Re: [2.0] play 2.0.3 Eric Jain 8/5/12 3:31 PM
On Friday, August 3, 2012 6:07:28 AM UTC-7, peter hausel wrote:
We are pleased to announce the availability of play 2.0.3

When I try to run after upgrading from 2.0.3-RC2 to 2.0.3, I get:

[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: org.junit.contrib#truth;0.7.0: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::

Re: [2.0] play 2.0.3 peter hausel 8/6/12 5:38 AM
I can not replicate that, are you sure that's a dependency on play?
Re: [play-framework] Re: [2.0] play 2.0.3 Eric Jain 8/6/12 9:45 AM
On Mon, Aug 6, 2012 at 5:38 AM, peter hausel <peter....@gmail.com> wrote:
> I can not replicate that, are you sure that's a dependency on play?

Can't replicate this either, so it must have been a temporary problem...

Other than that, upgrading to the latest release worked fine. Keep up
the frequent releases!
Re: [2.0] play 2.0.3 tlarhices 8/6/12 5:45 PM
The home page is still linking to play 2.0.2:
"Play framework 2.0.2 Final is out!"