For the project that contains references to fr.ldcom.sql.DataHandler,
can you expand "Maven Dependencies" node in Package Explorer view and
check if all expected dependencies are there? The dependency project
should be at the bottom of the list and have folder-like icon that
denotes project reference (as apposed to jar icon).
If you don't see the project dependency, please check pom.xml has proper
dependency declaration, i.e. groupId, artifactId and version must match.
Also make sure the project has workspace artifact resolution is enabled
for the project.
Yves Dessertine wrote:
Hi Everybody,
I have a problem with one of my projects.
In a class, two imports are marked as error in Eclipse:
import fr.ldcom.sql.DataHandler;
import fr.ldcom.sql.MyPreparedStatement;
Message in Eclipse:
"The import fr.ldcom.sql cannot be resolved"
Fine, but one project marked as a dependency provides this package and
class, and is declared in the POM.
When I click on the string "DataHandler" in Eclipse, it opens the
class javax.activation.DataHandler. Yes, I have two "DataHandler", but
in two projects, and declared in two different packages. Both of these
projects are declared as a dependency.
The activation-1.1.jar is also marked as a dependency.
Could there be a kind of "conflict" between:
- fr.ldcom.sql.DataHandler;
- javax.activation.DataHandler
Isn't Eclipse supposed to handle this properly ?
Regards,
Yves Dessertine
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
