Closed TonioGela closed 3 months ago
Hey @TonioGela thanks for this. Could you say more about the "and fixes the scripted tests" bit?
So g8Test
is still a no-op until something is fixed upstream?
So
g8Test
is still a no-op until something is fixed upstream?
Yes. To the best of my understanding what happened is this:
scriptedDependencies
of the Giter8Plugin
is set to compile the template and place the compiled artifacts under target/sbt-test
g8Test
runs, it should honor what's present in scriptedDependencies
, so compile the template and then invoke the ScriptedPlugin
testing command to run the test present under targe/sbt-test
ScriptedPlugin
is part of sbt itself) either changed the evaluation strategy of the settings' overrides or (more probably) moved the setting scriptedDependencies
in the ScriptedPlugin
from being a global property to a project property (or something similar)..enablePlugins(ScriptedPlugin)
what will happen is that the scriptedDependencies
value set in ScriptedPlugin
will override the one in Giter8Plugin
, so the template won't compile and the scripted tests will simply turn into a no-op.enablePlugins(ScriptedPlugin)
declaration in the template's build fixes the problem as (I assume) Giter8Plugin
now it's the one that directly invokes the scripted test after having compiled the template.I can't tell if upstream will get fixed or if the new standard for g8 plugins will become not declaring the ScriptedPlugin
, what I can tell you is that I amended the giter8's giter8 official template in this PR and Eugene merged it already.
So, apparently giter8 recently introduced some kind of regression, or at least now there's a required change in all g8Templates that is to remove
.enablePlugins(ScriptedPlugin)
from the project, as was found out and reported here.The sad side effect of this regression is that now
g8Test
is a no-op, and taking a look recent builds confirms that.This PR removes that plugin and fixes the scripted tests