Hi, I have the same issue. After renaming my projects, maven cannot resolve dependencies anymore. I check the projects group ids, artifacts ids, and versions. All looks fine but I have a similar message than the one you described.
I have the following error : [ERROR] \workspaces\workspace-pm\project\src\main\java\com\company\portal\emc\WBEMConstants.java:[9,0] cannot access GenericClient [ERROR] file GenericClient.class not found But the GenericClient class exists. I also founded the following error : [ERROR] found : com.company.portal.common.model.Discovery [ERROR] required: Discovery I think that dependency is resolved against the simple name, that's why classes are not found (it should resolve it with their full name). But how can I fix it ? Do you have solve this issue ? Any help would be welcomed. Thanks, Christophe. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-project-can-t-access-class-file-tp4599976p4888217.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
