JDT doesn't recognize the setters generated by @BeanProperty
Migrated from http://lampsvn.epfl.ch/trac/scala/ticket/2763
Reporter Alex.Savitsky
When using @BeanProperty, the generated getters are properly recognized by the Java compiler; however, setter access is reported as an unknown method in editor, even though it works at runtime.
Eclipse v.3.5.1
Build id: M20090917-0800
Scala Eclipse Plugin v.2.8.0.r19928-b20091129034731 (latest)
Reporter Alex.Savitsky
When using @BeanProperty, the generated getters are properly recognized by the Java compiler; however, setter access is reported as an unknown method in editor, even though it works at runtime.
Eclipse v.3.5.1
Build id: M20090917-0800
Scala Eclipse Plugin v.2.8.0.r19928-b20091129034731 (latest)
Leave a comment
on 2009-12-04 16:14 *
By tracImporter
on 2009-12-04 16:14 *
By tracImporter
Updating tickets (#1000069, #1000195, #1000213, #1000223, #1000006, #1000021, #1000038, #1000048, #1000051, #1000052, #1000075, #1000103, #1000109, #1000115, #1000119, #1000156, #1000186, #1000207, #1000238, #1000262, #1000263, #380, #389, #683, #1238, #1331, #1635, #1645, #1715, #1729, #1744, #1783, #1839, #1869, #1885, #1890, #1902, #1918, #1919, #1924, #1925, #1946, #1964, #1991, #2131, #2233, #2342, #2348, #2408, #2459, #2499, #2523, #2572, #2582, #2602, #2614, #2615, #2675, #2710, #2745, #2763, #2816, #2830, #2834, #2878, #2879, #2887, #2888, #2901, #2911, #2912, #2922, #2937, #2938, #2942, #2951, #2955, #2957, #2961, #2964, #2965, #2974, #2975, #2989, #2990, #3002, #3055, #3070, #3087, #3135, #3139, #3173, #3182, #3184, #3200, #3213, #3214, #3221, #3243, #3251)
Closing as invalid.
The test case reference the wrong class, but still, I cannot reproduce the problem on both 2.0.0-2.9 and master-2.10. This has likely been fixed during 2.0 development.
Please reopen with additional information if you still see the problem.
The test case reference the wrong class, but still, I cannot reproduce the problem on both 2.0.0-2.9 and master-2.10. This has likely been fixed during 2.0 development.
Please reopen with additional information if you still see the problem.