nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqujj3c8pf6jq8mwnejwjj2ng08w8f8qzjcskxmjcz6ayw7w304heqcu4x5y (nprofile…4x5y) One of my issues with mill (which might be an issue on my end) is that I don't find the discoverability of available tasks particularly great.
For example, say I want to test changes with testing (which is invalid).
sbt testing returns:
[error] Not a valid command: testing (similar: settings, session)
[error] Not a valid project ID: testing
[error] Expected ':'
[error] Not a valid key: testing (similar: testGrouping, test, testOnly)
[error] testing
[error]
scala-cli testing returns
[error] testing is not a scala-cli sub-command and it is not a valid path to an input file or directory.
Try viewing the relevant help to see the list of available sub-commands and options.
scala-cli --help
(with scala-cli --help showing the list of commands, including test)
Meanwhile, mill testing returns:
Cannot resolve testing. Try `mill resolve _` to see what's available.
But that command is not very helpful for noobs... For example, in oslib, I get:
clean
init
inspect
os
path
plan
resolve
show
showNamed
shutdown
version
visualize
visualizePlan
How do I test?
How do I compile?
Are those subprojects (e.g.os) or tasks (e.g. clean, init,...)?
Why is there no indication that I can do things like ./mill resolve os._ to get the subtasks?
João Costa /
npub1dn…djnjd
2025-05-29 12:33:09
in reply to nevent1q…6qww
Author Public Key
npub1dnu73kyya5th8ml2dw9m35znmgrnf688lnkxj8qzr8mysjtnhcwsedjnjdSeen on
wss://relay.mostr.pubPublished at
2025-05-29 12:33:09Event JSON
{
"id": "36fb6daefd4992b1f54afd8764ad1657788c6346629ca029c2521842871921a7",
"pubkey": "6cf9e8d884ed1773efea6b8bb8d053da0734e8e7fcec691c0219f6484973be1d",
"created_at": 1748521989,
"kind": 1,
"tags": [
[
"p",
"e4a51c1c29d4807dba7993a5254d0f3b8e938052c42c6dcb02d748ef3a2fadf2",
"wss://relay.mostr.pub"
],
[
"p",
"ee4b8687cbcc07bf9774ae83ddec3c679bb99ad48b73407c641ce5a101c7eac9",
"wss://relay.mostr.pub"
],
[
"e",
"73327c8f9eb97b9ee89a1f5dfa69100f029c1c69c7a21158e751b9435ce9bd86",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://blog.joaocosta.eu/o/910c2c56b8ed4a05aa7c6fd883417604",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.mostr.pub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqujj3c8pf6jq8mwnejwjj2ng08w8f8qzjcskxmjcz6ayw7w304heqcu4x5y One of my issues with mill (which might be an issue on my end) is that I don't find the discoverability of available tasks particularly great.\nFor example, say I want to test changes with testing (which is invalid).\nsbt testing returns:\n\n[error] Not a valid command: testing (similar: settings, session)\n[error] Not a valid project ID: testing\n[error] Expected ':'\n[error] Not a valid key: testing (similar: testGrouping, test, testOnly)\n[error] testing\n[error]\n\n\nscala-cli testing returns\n\n[error] testing is not a scala-cli sub-command and it is not a valid path to an input file or directory.\nTry viewing the relevant help to see the list of available sub-commands and options.\n scala-cli --help\n\n\n(with scala-cli --help showing the list of commands, including test)\nMeanwhile, mill testing returns:\n\nCannot resolve testing. Try `mill resolve _` to see what's available.\n\n\nBut that command is not very helpful for noobs... For example, in oslib, I get:\n\nclean\ninit\ninspect\nos\npath\nplan\nresolve\nshow\nshowNamed\nshutdown\nversion\nvisualize\nvisualizePlan\n\n\n\nHow do I test?\nHow do I compile?\nAre those subprojects (e.g.os) or tasks (e.g. clean, init,...)?\nWhy is there no indication that I can do things like ./mill resolve os._ to get the subtasks?\n\n",
"sig": "24aee4f1d29610a8ea4417bafa4e019e6eb78fdb0300372cb73c5ec67fe9b9df604686739dc5f549ea0dab5c819f717f24d0d24d7d602bfcecfdac0f60cb1437"
}