Eclipse automatically adding final keyword...

[Rickard Engstrom]

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:
.
.
.

  
  public PdfGeneratorServiceImpl(final BTPApplication btpApp) {
    this.btpApp = btpApp;
  }
 

.
.
.

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]

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:
.
.
.

  
  public PdfGeneratorServiceImpl(final BTPApplication btpApp) {
    this.btpApp = btpApp;
  }
 

.
.
.

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

[Tim Holloway]

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]

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]

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