Re: [tycho-user] Unexplained compilation error

["Rizzo, Eric" <Eric.Rizzo@xxxxxxx>]

On 11/22/12 2:38 AM, "Krzysztof Daniel" <kdaniel@xxxxxxxxxx> wrote:

>Eric,
>
>You may want to visit
>http://wiki.eclipse.org/Tycho/Target_Platform#Dependency_resolution_troubl
>eshooting
>and call your build with Run mvn with
>"-Dtycho.debug.resolver=yourbundleid -X"
>
>This should print exactly what is being resolved.
>
>On the other hand, you may want to look at emf git log to check when
>this method was added - at least you will know which emf versions may
>play a role here.
>
>Yet another thing to check is searching for EMF bundles in the maven
>repo - maybe there are multiple versions of EMF loaded.

Daniel,
Thanks for the link and the debug property; I'll save those for future
troubleshooting. It turns out this specific problem was due to someone
having added a JAR to the plugin that included some (old) EMF classes in
it. Unfortunately, this isn't the first time I've encountered that
particular bad habit on this project :-(

Eric


>
>On Wed, 2012-11-21 at 15:46 -0500, Rizzo, Eric wrote:
>> I'm converting a large RCP product from PDE Build to Tycho, and using
>> a .target file to set the same target platform for both development in
>> Eclipse IDE and Tycho build.
>> One of our plugin projects is failing compilation in Tycho because it
>> complains a certain method is missing from EMF's EObject class. The
>> method is certainly part of the version of EObject that is visible in
>> our IDE (and to our existing PDE Build), it
>> is org.eclipse.emf.ecore.EObject.eIsProxy(). It's a little confusing
>> because it doesn't complain that EObject itself isn't found, just the
>> method eIsProxy().
>> 
>> 
>> 1. ERROR in F:\<our\plugin\source\path\CallProcessPage.java (at line
>> 74)
>> if (obj != null && obj instanceof EObject &&
>> ((EObject)obj).eIsProxy()) {
>>                                                            ^^^^^^^^
>> The method eIsProxy() is undefined for the type EObject
>> 
>> 
>> 
>> 
>> Other plugins in our product use EObject, even that specific method,
>> but I haven't encountered any compilation errors on them (yet, but my
>> overall build fails part-way through because of this error). I tried
>> building just this one plugin with the ­X argument, but it's hard to
>> get useful information from the verbose logging that comes out of
>> that. From what I could tell, it didn't look like there was any old
>> version of org.eclipse.emf.ecore on the build classpath, but I don't
>> feel 100% certain.
>> Are there any ideas or techniques for troubleshooting this kind of
>> compile classpath problem?
>> 
>> 
>> Thanks,
>> Eric
>> 
>> 
>> _______________________________________________
>> tycho-user mailing list
>> tycho-user@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>
>-- 
>Krzysztof Daniel <kdaniel@xxxxxxxxxx>
>Red Hat
>
>_______________________________________________
>tycho-user mailing list
>tycho-user@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/tycho-user