How did you fix your imports? I have errors relating to forms.
Thanks
Jason
On Friday, 21 December 2012 23:48:28 UTC, Brian Hanafee wrote:
The migration guide suggests adding javaCore, javaJdbc and javaEbean to
appDependencies. It mentions as an aside that it's no longer necessary to
specify mainLang because enabling javaCore is sufficient to enable Java
support. It then describes the move of play.mvc.Controller#form() to
play.data.Form#form(). When I recompiled after upgrading, I had a bunch of
compilation errors related to forms, so dove into those changes to figure
out what had gone wrong and fix my imports. It would have save me a ton of
time if the migration guide had mentioned that, unrelated to moving the
form() methods, adding javaCore to the path of a *Scala* project breaks
it.
--The migration guide suggests adding javaCore, javaJdbc and javaEbean to
appDependencies. It mentions as an aside that it's no longer necessary to
specify mainLang because enabling javaCore is sufficient to enable Java
support. It then describes the move of play.mvc.Controller#form() to
play.data.Form#form(). When I recompiled after upgrading, I had a bunch of
compilation errors related to forms, so dove into those changes to figure
out what had gone wrong and fix my imports. It would have save me a ton of
time if the migration guide had mentioned that, unrelated to moving the
form() methods, adding javaCore to the path of a *Scala* project breaks
it.
On Monday, November 26, 2012 5:53:24 AM UTC-8, peter hausel wrote:
Hi,
The `form` package was decoupled from the `mvc` package due to
modularization. That is, the java `data` package and its dependencies are
part of the `javaCore` artifact now while play.mvc is part of playCore.
This way if you are using only playCore you won't get the spring
dependencies for example.
FYI, I updated the migration guide with some relevant information:
http://play2-docs-snapshot.herokuapp.com/render/Migration
Thanks,
Peter
Hi,
The `form` package was decoupled from the `mvc` package due to
modularization. That is, the java `data` package and its dependencies are
part of the `javaCore` artifact now while play.mvc is part of playCore.
This way if you are using only playCore you won't get the spring
dependencies for example.
FYI, I updated the migration guide with some relevant information:
http://play2-docs-snapshot.herokuapp.com/render/Migration
Thanks,
Peter
On Sunday, November 25, 2012 3:59:17 PM UTC-5, jsinghfoss wrote:
I'm running into a similar problem. What's the benefit? Seems like bug.
I'm running into a similar problem. What's the benefit? Seems like bug.
On Sun, Nov 25, 2012 at 3:54 PM, mirkoadari wrote:
I know that Form has static methods and I already use IntelliJ. However
it bothers me to go through my code to add imports in the first place. I
really don't see what is the benefit of such a change that affects 99% of
apps out there.
I know that Form has static methods and I already use IntelliJ. However
it bothers me to go through my code to add imports in the first place. I
really don't see what is the benefit of such a change that affects 99% of
apps out there.
On Sunday, November 25, 2012 10:52:36 PM UTC+2, Ondřej Kroupa wrote:
Use play.data.Form.form. BTW I recommend to use IntelliJ IDEA with
Scala plugin. It will hint you, what to import.
On Sunday, November 25, 2012 at 9:50 PM, mirkoadari wrote:
Is Controller.form() removed? What is the substitute and why such a
reckless breakage of existing code?
On Monday, November 19, 2012 3:27:07 PM UTC+2, peter hausel wrote:
Hi all,
We are very pleased to announce the availability of play 2.1-RC1!
What's new? https://github.com/**playframework/Play20/wiki/**
Highlights <https://github.com/playframework/Play20/wiki/Highlights>
Migration guide: https://github.com/**playframework/Play20/wiki/**
Migration <https://github.com/playframework/Play20/wiki/Migration>
Lighthouse milestone: https://play.**lighthouseapp.com/projects/**
82401-play-20/milestones/**current<https://play.lighthouseapp.com/projects/82401-play-20/milestones/current>
How to install:
1) read the migration guide
2) download package from http://www.playframework.**org/download<http://www.playframework.org/download>
3) change project/build.properties to 0.12.1 and the play version in
project/plugins.sbt to 2.1-RC1
Let us know if you have questions or run into problems.
Play Team
--
--
Use play.data.Form.form. BTW I recommend to use IntelliJ IDEA with
Scala plugin. It will hint you, what to import.
On Sunday, November 25, 2012 at 9:50 PM, mirkoadari wrote:
Is Controller.form() removed? What is the substitute and why such a
reckless breakage of existing code?
On Monday, November 19, 2012 3:27:07 PM UTC+2, peter hausel wrote:
Hi all,
We are very pleased to announce the availability of play 2.1-RC1!
What's new? https://github.com/**playframework/Play20/wiki/**
Highlights <https://github.com/playframework/Play20/wiki/Highlights>
Migration guide: https://github.com/**playframework/Play20/wiki/**
Migration <https://github.com/playframework/Play20/wiki/Migration>
Lighthouse milestone: https://play.**lighthouseapp.com/projects/**
82401-play-20/milestones/**current<https://play.lighthouseapp.com/projects/82401-play-20/milestones/current>
How to install:
1) read the migration guide
2) download package from http://www.playframework.**org/download<http://www.playframework.org/download>
3) change project/build.properties to 0.12.1 and the play version in
project/plugins.sbt to 2.1-RC1
Let us know if you have questions or run into problems.
Play Team
--
--
