On 22.02.22 12:22, Neil C Smith wrote:
On Tue, 22 Feb 2022 at 10:59, Michael Bien <[email protected]> wrote:
i mean, ideally, ant clean should work :)
But yeah why not add another task as nuclear option. Judging from the
responses on this thread and other places (e.g
https://github.com/apache/netbeans/pull/3392 ), everyone seems to be
using git already for cleaning.
Also read https://github.com/apache/netbeans/pull/2421
There's a reason `ant clean` shouldn't clean that. Also note the
comment on that PR from Matthias about binaries cache.
So, yes, I do think a "nuclear option" should be separate to `ant
clean`, because nuking all cached downloaded data is probably not what
you want in general?!
like i said, i have nothing against multiple clean targets.
but regarding cleaning everything:
I am doing this for full rebuilds usually. At some point i started to
build in ramdisk after i couldn't trust ant clean anymore. I don't
clean, i just unmount once i am done.
When i try to investigate things like the maven indexer modules which
loaded the wrong lucene jars i don't want to have to second guess the
build itself too (and this thread shows that nb-javac was not the only
problem) - it simply has to work, one jar hell at a time is enough.
i just leave this tweet here to lighten the mood :)
https://twitter.com/LEGO_Group/status/1456663358434914308
-mbien
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
