I was having same issue then realized that the version of commons-io getting picked up was lower than what I need (2.4)....I need to Override the already managed version as below to get the right one picked up:

<dependency>
     <groupId>commons-io</groupId>
     <artifactId>commons-io</artifactId>
     <version>2.4</version>
 </dependency>

The mentioned package/classes are not present in the compiletime classpath. Basically, Java has no idea what you're talking about when you say to import this and that. It can't find them in the classpath.

drop the jars in /WEB-INF/lib folder of the project and this error should disappear.

You can download the jars from here commons-io and commons-fileupload

you can try these steps:

1.Right-click the project name (in the "Projects" window) -> New -> Folder, call it (say) "lib". Now open your file browser, navigate to that folder and drop all the custom libraries that you have.

2.Right-click the project -> Properties -> Libraries -> Compile (tab) -> Add JAR/Folder and add the jar files.

First remove your local repository (may be only the commons-io etc folder) furthermore check only Maven Central under the following URL:

http://search.maven.org/

where you find the your needed dependencies:

<dependency>
    <groupId>commons-fileupload</groupId>
    <artifactId>commons-fileupload</artifactId>
    <version>1.2.2</version>
</dependency>

<dependency>
    <groupId>commons-io</groupId>
    <artifactId>commons-io</artifactId>
    <version>2.4</version>
</dependency>

File repositoryPath = new File("\\temp");
File uploadedFile = new File("\\applets");

By trying to access these files without any sort of leading or absolute path, you are trying to write to files (not directories) named temp and applets under the current working directory. In an app server, the current working directory is usually the bin folder (depends on what app server you use, etc).

Some suggestions:

1. Use an absolute path (preferably stored in web.xml or a properties file) to refer to the directory you want to save files to.
2. You have to specify the name of the file you want to write to, you probably want to create some sort of random/unique name per request.
3. Save yourself some keystrokes and use a member variable instead of all the Logger.getLogger(UploadGameServlet.class.getName()) references!
4. Add some debugging, especially to see where you are writing your data to - log the result of repositoryPath.getAbsolutePath(), for example.

Look in the deployed web-app to see if the JAR file is present. (It should be in the webapp's WEB-INF/lib directory.) If it is missing, check the WAR file contents, and then the maven sandbox you used to create it.

(If you really did manage to package the WAR properly, you've probably run into a deployment glitch.)