Community
Participate
Working Groups
This can best be seen on the JPA properties page. - Open the properties on a JPA project that uses a User Library provider. - Go to the facets page and change the facets (using 'Apply'). - Go back to the JPA properties page. - Change the particular library used. - Commit with 'OK' - The library is not actually changed. This does not happen when skipping the side trip to the facets page, it does not happen without first populating the JPA properties page, and it does not happen when 'Apply' is used to commit the library change. It seems there is an extra refresh() done on the LibraryInstallDelegate which ends up re-init()-ing the library install config, and throwing away the UI changes.
Will take a look at this scenario.
I am not reproducing what you are seeing. I am able to apply facet changes then go to jpa page change the library and have the changes stick after ok.
Are you populating the JPA facets page, THEN changing the facets, THEN going back and changing the library configuration?