I'd say learn to make a game in Java first so you get the hang of programming, and then consider switching. C++ is not a beginner friendly language to learn. It's like someone tried to make an octopus by nailing 4 legs onto a greyhound ;)

c++ is much better for making games than java

People argue that java is a little slower than C++, which may be true in numbers, but honestly it doesn't hinder its ability to make great games.

C++ is more difficult and complex than java and since you have already been learning java, you will prevent many headaches by sticking with java.

I won't tell you to not learn C++, it will certainly prove to be an excellent tool, but don't leave java behind just because someone said c++ was better.

Edit: I take back what I said about slapping in the face, but honestly people that think this are stuck in the days when java wasn't what it is today.

If you aren't sure if you should use language X or language Y, chances are you aren't experienced enough to be doing anything that would make a significant difference either way. So just pick one. Using language X now doesn't stop you from learning/using language Y later. I've learned several languages, and I use them all (for different projects). Chances are, you will too.

I started dabbling in making games about a month ago in java following some tutorials on YouTube and have found that I enjoy it quite a bit.

Other than the Youtube bit, you answered your own question. You've been using Java for a few months, are making progress with it and are enjoying it.

Stick with it.

What other people tell you, tell them to blow it out their arse. Opinions are like... oh wait, already covered that orifice.

Simply said, you've got a hell of a lot to learn still from the Java side of things, you are making progress and it's going well, so stick with it. When you run into an actual barrier that you can't surmount, not a contrived one "other people" tell you that you are going to hit, then switch languages.

C++ if you enjoy low level optimization, complete control over your code, and/or knowing that your language is designed to run as fast as possible even if that means leaving open the possibility of making big mistakes. Most game engines are wrote in c++ for these reasons.

Java is also a pretty good language. It does a lot of extra work for you in attempt to prevent mistakes, it does this extra work even when you don't make mistakes. Therefore it is not as fast as c++, nor does it offer you the same kind of control over your machine. However the trade off means less mistakes, and therefor increased productivity.

complete control over your code,

Just curious, but what exactly in real world terms, do you mean by this.

At the tier of skill we are talking about at the beginner level, this expression comes up so often, but I cant imagine beginners really find they don't have the level of control over Java/C#/JavaScript/Lua/VB/etc... that they do over C++. In 99% of my coding experiences, even though I've been at this professionally for almost 15 years, I rarely run into situations where I don't have complete control over my code. I have on a few occasions thought I ran into such a situation, but generally it was my ignorance of how the language I was working in actually worked. The few examples I can think of are time of the time of garbage collection, byte ordering, implicit memory allocation and direct hardware access... and again, none of those things are something a beginner ( or often intermediate ) programmer ever runs into.

complete control over your code,

Just curious, but what exactly in real world terms, do you mean by this.

At the tier of skill we are talking about at the beginner level, this expression comes up so often, but I cant imagine beginners really find they don't have the level of control over Java/C#/JavaScript/Lua/VB/etc... that they do over C++. In 99% of my coding experiences, even though I've been at this professionally for almost 15 years, I rarely run into situations where I don't have complete control over my code. I have on a few occasions thought I ran into such a situation, but generally it was my ignorance of how the language I was working in actually worked. The few examples I can think of are time of the time of garbage collection, byte ordering, implicit memory allocation and direct hardware access... and again, none of those things are something a beginner ( or often intermediate ) programmer ever runs into.

I know I'm not the original poster, but you would have more control over the hardware with things like inline assembly, right? I'm fairly new to java, and correct me if I'm wrong, but you certainly wouldn't write an OS in Java, would you? But this thread is on Java or C++ for games so I won't pull the conversation that way.

I think both are great languages. I think since you're new and have already started with Java, stick with Java. I started with C++ and it took a few years for it to completely click (granted I was 10 when I started), Java has a kinder learning curve.