Win a copy of The Journey To Enterprise Agility this week in the Agile and Other Processes forum! And see the welcome thread for 20% off.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

Eclipse automatically adding final keyword...  RSS feed

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi
Simple question: How do I turn off Eclipse behaviour that automatically adds the final modifier to all local and parameter members?
It's driving me crazy, since in the following example I have a constructor with one parameter:
.
.
.

.
.
.

I don't need that final modifier insíde the constructor header. And besides, it's giving me a compiler error "The blank final field btpApp may not have been initialized"

Thanks in advance

/R
 
Rickard Engstrom
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Rickard Engstrom wrote:Hi
Simple question: How do I turn off Eclipse behaviour that automatically adds the final modifier to all local and parameter members?
It's driving me crazy, since in the following example I have a constructor with one parameter:
.
.
.

.
.
.

I don't need that final modifier insíde the constructor header. And besides, it's giving me a compiler error "The blank final field btpApp may not have been initialized"

Thanks in advance

/R





Found it...
Windows -> Preferences -> Java -> Editor -> Save Actions
And I think I also have to mention that it actually occured upon saving a file in Eclipse!
/R
 
Bartender
Posts: 19656
92
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would pay more attention to the message "The blank final field btpApp may not have been initialized". It's trying to tell you something important. Rename the parameter btpApp (but NOT the field btpApp) to something else while keeping the "final" attributes and see.
 
Rickard Engstrom
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Tim Holloway wrote:I would pay more attention to the message "The blank final field btpApp may not have been initialized". It's trying to tell you something important. Rename the parameter btpApp (but NOT the field btpApp) to something else while keeping the "final" attributes and see.



Thanks for the reply, and in fact I noticed that the cause was not the constructor parameter but instead a class member.

Cheers

/R
 
Tim Holloway
Bartender
Posts: 19656
92
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Rickard Engstrom wrote:

Tim Holloway wrote:I would pay more attention to the message "The blank final field btpApp may not have been initialized". It's trying to tell you something important. Rename the parameter btpApp (but NOT the field btpApp) to something else while keeping the "final" attributes and see.



Thanks for the reply, and in fact I noticed that the cause was not the constructor parameter but instead a class member.

Cheers

/R

 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!