-

can I ask you a question? why do you use scanner.close() at the end?
edit: this question has nothing to do with the error but in never used .close() on Scanner and I don't know what is used for in this case.

Did you ever
import java.util.scanner?

I got basic java class like 3 years ago and forgot almost all of it .

Could you host somewhere archive with whole project, it could help us a bit?

Better paste it to pastebin.com or sth like that. Cuz some things are messed up (replaced by eg. <).

"Your problem is caused by trying to read too much input. Imagine that you have 3 items in your file. Then you try and read 4 items from it. Obivously the fourth time you attempt to read there is nothing left, hence the exception. Now it is your job to find out where and or why you are doing this."

google

try printing the value of scanner.nextint enclosed by a catch try block

I can do Helloworld with 5 different languages but I have no idea what your problem is.

Try this:
System.out.println("Where do you want to bomb? (Input row first, then column)");
String str = scanner.nextLine();
try {
y = Integer.parseInt(str);
} catch (NumberFormatException e) {
System.out.println("That wasn't a number");
continue;
}
y--;

The "NoSuchElementException" is caused by trying to read after the end of the input. If you were reading the input from a file it would be easy to see, but from the standard input it may be difficult.
Be careful not to press Control+D or Control+Z in the console where you are writing the input as it is sometimes (depending on the platform) as the end of file.

Am i the only one not getting how you give the player time to enter something?

Are you sure you have your System.in in the right place? I'm not sure how scanners work exactly, but it looks like you are only giving it input once on initialisation and not in the loop, after it asks for the input, so when it looks for the next int there isn't any input there yet.

Interesting... I know very little about java code, I am learning VB and Python and will soon start C++.
All I can say is that I know your pain very well.

Looking at the nextInt from the Scanner class, you can see that it said

NoSuchElementException - if input is exhausted

and you also said that hasNext just skip the damn line, you know why? because I'm assuming there is nothing next, so trying to call nextInt will clearly throw the input is exhausted exception.

the issue is here

y = scanner.nextInt();
y--;
if (y > 4 || y < 0)

then if your y is < 0 (or higher than 4, but I'm assuming it's not) , it call another nextInt() without checking for the hasNext.

     x = scanner.nextInt();
                    x--;
                    if (x > 4 || x < 0)

so let's say in the scanner there is only 1 item, nextInt from your y will return the first item, but then when it hit the x, it will try to find the second item (which there is none, and will throw that exception)

I hope it helped a little.

l don't have access to a computer to check now, but a quick Google search suggested that the problem is with your closing of the scanner in the placement class. Apparently that also closes System.in, so when you make a new Scanner on System.in, it won't find anything.

Try this.

This is mainly a guess, since I'm in a computer without Java and I'm programming from notepad, but I took a look at the whole code and I think you could correct it by using a sing program wide Scanner object this way:
1) put "Scanner scanner = new Scanner(System.in);" in the main method, right after the field declaration.
2) remove "Scanner scanner = new Scanner(System.in);" from every other part of your program.
3) change firstPlacementPlayer method to firstPlacementPlayer(short[][] field, Scanner scanner)
4) change bombingPlayer method to bombingPlayer (short[][] field, Scanner scanner)
5) change the calls to firstPlacementPlayer and bombingPlayer to firstPlacementPlayer(field, scanner) and bombingPlayer(field, scanner)
6) remove every instance of scanner.close();

The idea is to have only one Scanner instance to avoid locking the standard input.

Personally I'm not trusting this scanner class, as that seems to be causing the problem somehow.

I would go for a BufferedReader for the input and then string.split to separate the number strings and Integer.parseInt to get the numbers as ints.

Did you look at the API?
More specifically this
My guess would be that it's because you try reading constantly; you never wait userinput. As such, it breaks.
I'd give you a pastebin of something that works, but it'll take me a bit to find. Hang in there. :P

http://stackoverflow.com/questions/14142853/close-a-scanner-linked-to-system-in

This is not for the problem but I would make the below code (and others like it) a for loop not a while loop
while (placement != 5)
{
y = (short) r.nextInt(5);
x = (short) r.nextInt(5);
field[y][x] = 1;
placement++;
}

for (int i = 0; i < 5; i++)
{
y = (short) r.nextInt(5);
x = (short) r.nextInt(5);
field[y][x] = 1;
}

Don't close the scanner... by doing so early, you end up closing the System.in...

EDIT
Oh as I noticed that someone had already mentioned :p

EDIT
You should do what someone mentioned earlier and simply open up the inputstream in the beginning of your program and then simply close it after the game is over and the program is about to exit.