Initialized multivalued variables fail to generate variables and initialization

[TimLethbridge]

emails and incoming number are not initialized as variables in the following, however the get and other methods appear, and the attributes appear in diagrams

class Office {
   Integer number;
   String[] emails = {"abc@umple.org", "def@umple.org"}
   Integer [] incomingNumber = {765432, 987654}
} 

Regular multivalued attributes (without initialization) seem OK.

[TimLethbridge]

But if a semicolon is added to the end it works. It should either generate and error in all cases or work without the semicolon in all cases.

[TimLethbridge]

In in the following example we have an attempt to initialize a derived attribute that also has a 'List'. This should create an error message saying:

If you have intended to specify a derived attribute there should not be a list indicator []. If you intended to create list initializer, there should be a semicolon on the end.

class X {
  
  String firstName;
  String lastName;
  
  String [] fullName = {firstName+" "+lastName}
}

[TimLethbridge]

You need to look in UmpleInternalParser_CodeClass.ump analyzeAttribute() starts on line 4315
You will need to ensure that new error 83 is only produced in the spefic casae where we have a 'List' with code as above (i.e. no semicolon).

You will have to add a test in UmpleParserTest.java just after the test for message 81 about line 3042