I'm afraid I know nothing of Jenkins so I'm not able to advise on changing that.

I was suggesting you might check the source to see which of 
com.ABC.XXX.bo.BusinessObject and  com.ABC.bo.BusinessObject was being imported 
 and confirm which one SHOULD be being imported.  It might be that a difference 
in classpaths is allowing you to get away with a source error in Eclipse but 
not elsewhere, so the fact that it works in Eclipse doesn't guarantee it's 
right.  It's a mistake I have made in the past.

If you are sure that the source is correct then my observation will not apply!  
Good luck either way. 

Regards

D.E>


-----Original Message-----
From: pradeepkumar [mailto:[email protected]] 
Sent: 01 December 2015 15:27
To: [email protected]
Subject: RE: Compilation Error -Incompatible Types

Hi  David , 


This is the original post .

I am facing the compilation error in my Jenkins job. 

We are not getting compile time error in Eclipse for BusinessObject but we are 
getting incompatible types error in Jenkins. 
Is there any way to resolve this issue rather than changing the source code. 


Please find the below. 

  
[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] /C:/Jenkins/jobs/XXX
Commons/workspace/src/com/ABC/XXX/bo/BusinessObject.java:[4158,102]
incompatible types
  required: com.ABC.XXX.bo.BusinessObject 
  found:    com.ABC.bo.BusinessObject 
[INFO] 1 error
[INFO] ------------------------------------------------------------ 

Please help me out regarding this issue. 



--
View this message in context: 
http://maven.40175.n5.nabble.com/Compilation-Error-Incompatible-Types-tp5852871p5853516.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to