Errors: no manifest attribute in jar for Mac, and skip non existing resourceDirectory **Error:, when directory does exist?

[Sushi-roll89]

Apache NetBeans version

Apache NetBeans 22

What happened

I can not open jar files, I keep getting these errors even though the directory does exist.

Language / Project Type / NetBeans Component

Java maven

How to reproduce

n/a

Did this work correctly in an earlier version?

No / Don't know

Operating System

Mac Monterey and windows 11

JDK

jdk 21, 17, and 22

Apache NetBeans packaging

Apache NetBeans provided installer

Anything else

no

Are you willing to submit a pull request?

Yes

[matthiasblaesing]

What do you want to do? What is the error you are seeing? You literally don't give anything to help you.

[Sushi-roll89]

Everything this guy said is default stuff. My problem is passed this.

[matthiasblaesing]

I read to many attempts in your very short description. You randomly mix build systems and don't form a description of what you did, what you saw, what you expected. I suggest StackOverflow for general programming questions or questions how to use your IDE.

[Sushi-roll89]

Yes, I had to try so many different options with different builds, and still kept getting the same problems, I watched dozens of videos with so called solutions but none of them worked. I'll provide more information. I'm just getting ready to work on this stuff in a few moments so I'll update more with extreme detail.

[matthiasblaesing]

STOP: Don't run around. Keep focused. Don't switch build systems. Do a minimal demonstrator. Before everybody created $random video for $trivial problem, people created simple, self contained samples with description what they did (with steps), what they expected and what they saw. Doing this nearly always solved the issue, because with this approach you analyse the problem and find your own failures.

[Sushi-roll89]

I agree with you, when I switching builds it was after 12 hours of trouble
shooting and getting no where on maven. Then I switch build and went back
to maven. I did terminal work with maven, and more. I even tried on Windows
and Mac. I figured someone had already run into this problem.