java.lang.IllegalArgumentException: requirement failed: Source file 'D:\Projects\trunk\Projects\MSFITS_AZURE\MSFITS_AZURE\AzureScalaQueueService\QueueHandlerBL\target\streams\_global\assemblyOption\_global\streams\assembly\5181d4d9456869cffee25db7cf40862afd4b5731_eea687e8f56f58f889b68f00ac267b8f9e328876_da39a3ee5e6b4b0d3255bfef95601890afd80709\META-INF\license' is a directory.

[champion-054]

No description provided.

[champion-054]

This is an issue that we are receiving while trying to assemble. The license directory is causing issues. Could you please suggest the solution for this. We have been breaking our heads for a long time now. None of the answers available help.
Thanks.

[eed3si9n]

Thanks for the report. Could you provide reproduction steps so we can reproduce your problem on our computers?

[luisffranca]

I had the same problem and the workaround proposed here worked for me.

[khujo]

Hey @eed3si9n,
I have created a repository reproducing the issue: https://github.com/khujo/sbt-assembly-on-windows
Running assembly, clean and then assembly again will raise an error like this one:

[error] stack trace is suppressed; run 'last assembly' for the full output
[error] (assembly) java.lang.IllegalArgumentException: requirement failed: Source file 'C:\Users\khujo\sbt-assembly-on-windows\target\streams\_global\assembly\_global\streams\assembly\919b9dff7940ba085b23a727d673b902a50cc84f_b039a2a0d771f071b57bae72e65222356693388e_da39a3ee5e6b4b0d3255bfef95601890afd80709\META-INF\license' is a directory.
[error] Total time: 4 s, completed 12.10.2022, 13:36:14

I was not able to reproduce the issue in WSL, so it's probably an issue with Windows only.
What if noticed so far is that you will need a dependency that has a /META-INF/license directory. After running clean the \target\streams\_global\assembly\_global\streams\assembly directory is still present and not empty as I would have expected. So maybe clean is unable to clean all the files produced during assembly. Hope that helps.

[martinring]

i can confirm, this issue was fixed by the recent changes to in memory processing in release 2.0.0

[eed3si9n]

Closing this as fixed.

[eed3si9n]

Likely this was fixed in #478