After some digging, I stumbled onto this bug which I think is the problem:
https://github.com/foundweekends/giter8/issues/860
So SBT broke something in SBT 1.9.7 making testing a no-op. The suggested fix of
removing "enablePlugins(ScriptedPlugin)" from build.sbt seems to fix it for me.
I just created a PR to fix this:
https://github.com/apache/daffodil-schema.g8/pull/11
On 2025-02-26 08:00 PM, Mike Beckerle wrote:
Any insight into this weirdness is welcome...
You are not going to believe this is possible, so I'm sure some of you will
try to reproduce this.
I am adding a feature to daffodil-schema.g8.
But a very weird thing just started happening.
'Sbt test' used to test this project just fine. It would generate a project
under target that I could inspect, and then sbt test that, which would tell
me if its little unit test (the one it creates as a stub) works.
And that was working just fine all afternoon.
Then suddenly.... Now ‘sbt test’ just seems to publish a bunch of jars to
.ivy2/local.
I can't recall doing anything that could have caused this.
I have done a git clean -xdf to eliminate all the caches/projects/etc.
I have switched back to the origin/main branch to eliminate any impact of
my changes that could possibly be causing this.
I checkout main. Same problem is happening now even if I just checkout the
main branch.
It’s like sbt has changed behavior suddenly.
This is all on the command line. No IDE involvement.
I’ve done git clean -xdf to delete anything not in the git repo.
So, I deleted all directories named ‘target’ under ~/.sbt
I blew away ~/.ivy2 even.
No change in behavior. ‘sbt test’ just publishes some jars and there is no
little example under target where I can see the generated files.
So, I went home and using my home linux computer there, ... I had never
even cloned the daffodil-schema.g8 repo.
So I clone it, verify main branch aka origin/main is checked out.
sbt test
Yup. Same problem.... sbt test no longer tests the generation of the
project. It now just publishes some jars locally.
Here's the output from sbt.
$ sbt
copying runtime jar...
[info] welcome to sbt 1.10.7 (Ubuntu Java 21.0.6)
[info] loading settings for project global-plugins from global.sbt,
plugins.sbt...
[info] loading global plugins from /home/mbeckerle/.sbt/1.0/plugins
[info] loading settings for project daffodil-schema-g8-build from
plugins.sbt...
[info] loading project definition from
/home/mbeckerle/dataiti/opensource/daffodil-schema.g8/project
[info] loading settings for project root from build.sbt...
[info] set current project to daffodil-schema.g8 (in build
file:/home/mbeckerle/dataiti/opensource/daffodil-schema.g8/)
[info] sbt server started at
local:///home/mbeckerle/.sbt/1.0/server/1b4ad77b5f1aabf50b5b/sock
[info] started sbt server
sbt:daffodil-schema.g8> test
[info] Wrote
/home/mbeckerle/dataiti/opensource/daffodil-schema.g8/target/scala-2.12/daffodil-schema-g8_2.12-0.1.0-SNAPSHOT.pom
[info] :: delivering ::
daffodil-schema-g8#daffodil-schema-g8_2.12;0.1.0-SNAPSHOT :: 0.1.0-SNAPSHOT
:: integration :: Wed Feb 26 19:41:38 EST 2025
[info] delivering ivy file to
/home/mbeckerle/dataiti/opensource/daffodil-schema.g8/target/scala-2.12/ivy-0.1.0-SNAPSHOT.xml
[info] published daffodil-schema-g8_2.12 to
/home/mbeckerle/.ivy2/local/daffodil-schema-g8/daffodil-schema-g8_2.12/0.1.0-SNAPSHOT/poms/daffodil-schema-g8_2.12.pom
[info] published daffodil-schema-g8_2.12 to
/home/mbeckerle/.ivy2/local/daffodil-schema-g8/daffodil-schema-g8_2.12/0.1.0-SNAPSHOT/jars/daffodil-schema-g8_2.12.jar
[info] published daffodil-schema-g8_2.12 to
/home/mbeckerle/.ivy2/local/daffodil-schema-g8/daffodil-schema-g8_2.12/0.1.0-SNAPSHOT/srcs/daffodil-schema-g8_2.12-sources.jar
[info] published daffodil-schema-g8_2.12 to
/home/mbeckerle/.ivy2/local/daffodil-schema-g8/daffodil-schema-g8_2.12/0.1.0-SNAPSHOT/docs/daffodil-schema-g8_2.12-javadoc.jar
[info] published ivy to
/home/mbeckerle/.ivy2/local/daffodil-schema-g8/daffodil-schema-g8_2.12/0.1.0-SNAPSHOT/ivys/ivy.xml
[success] Total time: 2 s, completed Feb 26, 2025, 7:41:39 PM
sbt:daffodil-schema.g8>
I am fully baffled by this. Different computers even. No patches have been
applied to any of these computers that would explain any of this.
Any ideas on what to try are welcome.
