ansaurus

Question

Answer 1

A:

You could try running the "mvn site" command and see what transitive dependencies you have, and then resolve potential conflicts (by ommitting an implicit dependency somewhere). Just a guess (it's a bit difficult to know what the problem could be without seeing your pom info)...

davek 2009-10-19 15:19:18

actually they are no site goals for the parent and the child, i am getting the failure when it starts compiling the project b though the project a is getting successful

dagg 2009-10-19 16:05:04

Answer 2

A:

My guess is a wrong version of project A jar in your local maven repository. It seems that the dependency is resolved otherwise I think maven does not start compiling but usually these compiling error means that you have a version mix up. try to make a maven clean install of your project A and see if it changes something for the project B... Also a little more information on your setting could be useful:

How is maven launched? what command? on a shell, an IDE (using a plugin or not), on a CI server?
What maven command are you using?

florent 2009-10-19 15:42:51

versions are perfect, i am using mvn clean install on command promt.when i did debug using -X i have seennthe dependency directing the right path toward the jar though it is not recogniseing it

dagg 2009-10-19 15:59:24

are you sure the jar of project A is correctly generated? can you find the class/method if you look into it manually (or manually add it as a dependency to a new empty project?did you try emptying your local repo?

florent 2009-10-19 17:50:42

yes i can see the class \methods in jar

dagg 2009-10-19 18:08:11

then i don't know, maybe something is cached...

florent 2009-10-19 19:03:36

thanks for your time, i need a confirmation does the class file name and the class mentioned in java file should be same including case sensitive

dagg 2009-10-19 19:20:20

is it an inner class? in this case no, in the other case I don't know, i never did it otherwise (usually goood practice and i think it should)

florent 2009-10-19 19:58:23

Answer 3

A:

The error is pretty clear: "cannot find symbol". Some dependencies can't be resolved (you even have the line and column in the trace of the reference that can't be resolved):

V:/dhs_tss_build_view/dhs_tssproject/tss/tsscommon-server/src/main/java/us/mn/state/dhs/tss/common/oblix/da/wsdl/OblixLoginAc
cess.java:[51,60] cannot find symbol
symbol  : class BusinessException
location: class us.mn.state.dhs.tss.common.oblix.da.wsdl.OblixLoginAccess

V:/dhs_tss_build_view/dhs_tssproject/tss/tsscommon-server/src/main/java/us/mn/state/dhs/tss/common/app/da/ldap/BaseLdapImpl.j
ava:[187,14] cannot find symbol
symbol  : class Phone
location: class us.mn.state.dhs.tss.common.app.da.ldap.BaseLdapImpl

V:/dhs_tss_build_view/dhs_tssproject/tss/tsscommon-server/src/main/java/us/mn/state/dhs/tss/common/app/da/ldap/BaseLdapImpl.j
ava:[204,14] cannot find symbol
symbol  : class Phone
location: class us.mn.state.dhs.tss.common.app.da.ldap.BaseLdapImpl

Below a couple of things to verify:

Check or recheck that these classes are in the jar A (same version as in the pom)
Check or recheck the import statement in B sources (should match the package of classes in A)
Check or recheck B's pom.xml and especially the declaration of the dependency on A (it's version)
Check that the dependency on A is not excluded transitively somewhere in B's pom
Is A a SNAPSHOT dependency? If no, delete A from your local repository and rebuild

Maven is working fine, you have a mistake somewhere.

Pascal Thivent 2009-10-19 20:09:51

ansaurus

tags:

views:

answers:

maven compilation failure

related questions