[ROO-3466] [ERROR] FloatBox cannot be resolved to a type when defining a field of type java.lang.Float in gwt project Created: 04/Dec/13  Updated: 12/Apr/14  Resolved: 12/Apr/14

Status: Resolved
Project: Spring Roo
Component/s: @ CORE, GWT
Affects Version/s: 1.2.4.RELEASE, 1.2.5.RELEASE
Fix Version/s: 1.3.0.RELEASE

Type: Bug Priority: Major
Reporter: Mario Jauvin Assignee: Alan Stewart
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Pull Request URL: https://github.com/spring-projects/spring-roo/pull/67

 Description   

If I run the following script:

GWT script
project --topLevelPackage t.com --projectName t --java 7 --packaging JAR jpa setup --database DERBY_EMBEDDED --provider HIBERNATE 
entity jpa --class ~.domain.Person --testAutomatically
field string --fieldName name
field number --type java.lang.Float --fieldName price
web gwt setup
web gwt all --proxyPackage ~.client.proxy --requestPackage ~.client.request

when I type

command
perform command --mavenCommand gwt:run

I get the following errors

Errors
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building t 0.1.0.BUILD-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] n.Person roo>
[INFO] >>> gwt-maven-plugin:2.5.0:run (default-cli) @ t >>>
[INFO] n.Person roo>
[INFO] --- aspectj-maven-plugin:1.4:compile (default) @ t ---
[ERROR] FloatBox cannot be resolved to a type
The command 'mvn.bat gwt:run' did not complete successfully
~.domain.Person roo> [WARNING] advice defined in org.springframework.scheduling.
aspectj.AbstractAsyncExecutionAspect has not been applied [Xlint:adviceDidNotMat
ch]
[WARNING] advice defined in org.springframework.mock.staticmock.AnnotationDrivenStaticEntityMockingControl has not been applied [Xlint:adviceDidNotMatch]
[WARNING] advice defined in org.springframework.mock.staticmock.AbstractMethodMo
ckingControl has not been applied [Xlint:adviceDidNotMatch]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.176s
[INFO] Finished at: Wed Dec 04 19:13:20 EST 2013
[INFO] Final Memory: 15M/230M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:aspectj-maven-plugin:1.4:compile (default) on project t: Compiler errors:
[ERROR] error at FloatBox price;
[ERROR] ^^^rson roo>
[ERROR] D:\Users\mario\Documents\sts\applets\troo\src\main\java\t\com\client\managed\ui\desktop\PersonDesktopEditView_Roo_Gwt.java:41:0::0 FloatBox cannot be resolved to a type
[ERROR] -> [Help 1]>
[ERROR] .Person roo>
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] .Person roo>
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


 Comments   
Comment by Mario Jauvin [ 04/Dec/13 ]

Seems to be broken for java.lang.Byte also. It was working in roo 1.2.3.

Why has this not been reported. roo 1.2.4 has been out for a while?

Comment by Mario Jauvin [ 06/Dec/13 ]

Any chance this may get looked at soon. This is rather a show stopper.

Comment by Alan Stewart [ 14/Dec/13 ]

The only way that this will be be fixed is if you provide a pull request. Given that GWT is now community driven there will be no new development of the Roo GWT add-on.

Let me know if you want to fix it, otherwise I will close.

Comment by Alan Stewart [ 22/Dec/13 ]

Waited but no response

Comment by Mario Jauvin [ 23/Dec/13 ]

Alan, what do you mean by community driven? Is the GWT Roo plugin no longer supported? When and why did it stop being supported?

Comment by Alan Stewart [ 23/Dec/13 ]

GWT is now a community project (gwtproject.org) and I would be surprised it gets the same attention now that it once did being part of Google. The Roo GWT add-on was developed in co-operation with former Google GWT engineers but those guys are no longer with Google and moreover the GWT add-on is complex, not easily maintained, and the Roo engineer who developed the add-on is no longer with VMware and the Roo team either

Given the lack of value add, I would like to remove it from the Roo codebase altogether. I don't have the skills myself to maintain the add-on and would prefer anyway to devote time to other new Roo features

Comment by Mario Jauvin [ 19/Feb/14 ]

I finally figured out how to do this and fixed this bug. You can find the pull request url in the proper field.

Comment by Mario Jauvin [ 12/Apr/14 ]

I tested under Roo 1.2.6.BUILD-SNAPSHOT [rev 32b413d] and the bug is fixed. Is it possible to indicate that this will be fixed in Roo 1.2.6.RELEASE ? I cannot edit this JIRA or change the fixed in release.

Comment by Alan Stewart [ 12/Apr/14 ]

Re-opened and resolved now as complete. Thanks for checking the fix

Generated at Fri Jan 24 04:38:51 UTC 2020 using Jira 7.13.8#713008-sha1:1606a5c1e7006e1ab135aac81f7a9566b2dbc3a6.