`tapmoc.Severity` is not resolved when using FQDN

[martinbonnin]

Description

This is because tapmoc (the package name) clashes with tapmoc (the autogenerated accessor)

Before:

After:

See https://youtrack.jetbrains.com/issue/KTIJ-26575/
See https://youtrack.jetbrains.com/issue/KTIJ-8463/

[OliverO2]

Hit this one again during an upgrade. Can we get package com.gradleup.tapmoc?

[martinbonnin]

I've been trying it but IJ insists on adding the full qualified name, which is better but still not great...

Screen.Recording.2025-12-28.at.23.59.52.mov

I'm tempted to just make Severity a String:

tapmoc {
  java(11)
  kotlin("1.9.0")
  checkDependencies("ERROR")
}

No breaking change, no import => no typesafety, but also no problem.

Thoughts?

[OliverO2]

Do we need to worry about IJ inserting the FQN? I happen to use that quite often in Gradle scripts as it makes copy-pasting easy.

[martinbonnin]

checkDependencies("ERROR") is even simpler. No need to import and/or FQN there. Easy copy/pasta, even for folks that use imports. Of course it's not 100% typesafe but it's not like there are lots of options...

[OliverO2]

Of course, stringly typed is often simpler. Until things change and then it isn't. In this case, if you check validity immediately and things don't break somewhere deep in callstacks, it's probably not a big deal. Just more Groovy than Kotlin.

[martinbonnin]

Yea... The YouTrack has seen some activity lately. Let's wait a couple of weeks in the new year see if this gets fixed in IntelliJ before changing everything.