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
When opening https://github.com/spring-projects/spring-petclinic in VS Code, everything is fine except that static css resources are not compiled. The reason for this is that this project uses a 3rd party maven plugin wro4j-maven-plugin to generate css from less files, but the plugin does not seem to be executed by Java builder of VS Code Java extension.
This issue is similar as #935 and #177, where some custom source generation maven goals are not executed by m2e builder.
Since it is not trivial to improve m2e to automatically recognize these 3rd party maven plugins, one idea in my mind is that we provide quick fixes in the pom.xml if there are maven execution goals not executed by Java builder. If the user clicks the quick fix, it will insert the inline m2e lifecycle mapping to the pom.xml for the corresponding maven plugin.
When opening https://github.com/spring-projects/spring-petclinic in VS Code, everything is fine except that static css resources are not compiled. The reason for this is that this project uses a 3rd party maven plugin wro4j-maven-plugin to generate css from less files, but the plugin does not seem to be executed by Java builder of VS Code Java extension.
The text was updated successfully, but these errors were encountered: