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
The project exports two artifacts, one is the primary jar artifact and the other is an assets artifact. However, the primary artifact also includes the assets it its META-INF/resources/webjars/metrics-portal// folder. The assets are not setup to be used as webjar assets (wrt cross-references) so they should be removed from the primary artifact and used only from the assets artifact. There is currently no blocking impact on projects extending metrics-portal and the metrics-portal uses the distribution artifact created by Play for deployment.
The text was updated successfully, but these errors were encountered:
cwbriones
pushed a commit
to cwbriones/metrics-portal
that referenced
this issue
Dec 15, 2018
However, we have not tested whether this is sufficient packaging when consumed by an extension project. The original issue arose because it was not sufficient under SBT.
The project exports two artifacts, one is the primary jar artifact and the other is an assets artifact. However, the primary artifact also includes the assets it its META-INF/resources/webjars/metrics-portal// folder. The assets are not setup to be used as webjar assets (wrt cross-references) so they should be removed from the primary artifact and used only from the assets artifact. There is currently no blocking impact on projects extending metrics-portal and the metrics-portal uses the distribution artifact created by Play for deployment.
The text was updated successfully, but these errors were encountered: