You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding the assignment of properties to each project, it also seems that everything is based on whether or not the plugin appears on the pom.
This way, if you delete or change the .settings files, you have to use Maven -> Update project to recreate them.
Although this is a correct solution, it is a bit confusing for the user, who sometimes doesn't know if the plugin appears in the pom or in one of its parents and if the correct format is being applied.
An eclipse nature could be used so that the user himself could add or remove it at will to the projects where he wants to use the format. You could clearly see whether or not the project has that nature and the properties are automatically assigned and reset. And it fits Eclipse style.
I've tried it and it works.
Thanks again.
The text was updated successfully, but these errors were encountered:
Regarding the assignment of properties to each project, it also seems that everything is based on whether or not the plugin appears on the
pom
.This way, if you delete or change the
.settings
files, you have to use Maven -> Update project to recreate them.Although this is a correct solution, it is a bit confusing for the user, who sometimes doesn't know if the plugin appears in the pom or in one of its parents and if the correct format is being applied.
An eclipse nature could be used so that the user himself could add or remove it at will to the projects where he wants to use the format. You could clearly see whether or not the project has that nature and the properties are automatically assigned and reset. And it fits Eclipse style.
I've tried it and it works.
Thanks again.
The text was updated successfully, but these errors were encountered: