Maven weird behaviour
Hi, I just started using Maven to manage my project structure as this was needed for a package which I could not find online to download.
And now, when I try to compile or run my program, it throws shitty errors which make 0 sense and were never a thing before (for example, that imported packages/dependencies are not found or do not have a class or something). Does anyone know why that happens?
7 Replies
⌛ This post has been reserved for your question.
Hey @netty.bootstrap! Please useTIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here./closeor theClose Postbutton above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically closed after 300 minutes of inactivity.
Ah yes the famous "there are some shit that aren't working here" error message. Of course we totally know why it happens
Generally speaking, using maven is different to not using it, and therefore you'll get errors instead of what you had before if you try to do the same things after you've switched to use Maven. I guess we know that
Bruhhh why tf is that
makes no sense
Does gradle have those issues also
Bruuuuh nobody has a clue what you're doing. When you're replacing a car with a train going to your destination won't be the same. That's how it is.
rip
Unknown User•8mo ago
Message Not Public
Sign In & Join Server To View
💤 Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.