kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dhwani Katagade <dhwani_katag...@persistent.co.in>
Subject Re: Build problems in Eclipse dev environment setup
Date Sun, 08 Jan 2017 13:49:47 GMT
Hi Ismael,

Thanks for your response. I agree this is not a Kafka issue, its about 
gradle and its eclipse plugin. I was able to resolve the compile errors 
in Eclipse by manually setting the Default output folder for core 
project to core/build/classes/main.

I understand Eclipse is not the popular choice for an IDE but, for me 
and my other Eclipse brethren, I looked into the problems I faced and 
noticed that the output folders for gradle and those for eclipse get 
configured differently. The output folders in eclipse go under 
<project>/bin where as in gradle they are under <project>/build. Due to 
this the projects in Eclipse don't work fine unless the command line 
build is completed at least once. Will it be fine if we could align 
these so that inter project dependencies fall well in place in either 
build? *I was looking into the possibilities of fixing that and I have a 
change available that I am testing out.*

There is another discussion on the pros and cons of this here 
https://discuss.gradle.org/t/eclipse-generated-files-should-be-put-in-the-same-place-as-the-gradle-generated-files/6986

People, please let me know your opinion and I will provide a PR for this 
if I get this working for myself.

thanks
-dhwani

On 01/07/2017 07:02 PM, Ismael Juma wrote:
> Hi Dhwani,
>
> This is more about Gradle and Eclipse than Kafka and many of us use
> IntelliJ IDEA so won't be able to help you. I can confirm that IntelliJ is
> able to import the project fine out of the box.
>
> Ismael
>
> On 3 Jan 2017 6:45 pm, "Dhwani Katagade" <dhwani_katagade@persistent.co.in>
> wrote:
>
>> Hi,
>>
>> I am trying to setup the eclipse dev environment on trunk. I have followed
>> the instructions given here
>> https://github.com/apache/kafka/blob/trunk/README.md
>> https://cwiki.apache.org/confluence/display/KAFKA/Developer+
>> Setup#DeveloperSetup-Eclipsesetup
>>
>> After I run ./gradlew eclipse in the command line followed by "Import
>> existing projects into workspace" in Eclipse, I am able to see the
>> projects. But I see the following build errors in Eclipse.
>>
>> Description: The import kafka.utils.ShutdownableThread cannot be resolved
>> Resource: Consumer.java
>> Path: /kafka-examples/src/main/java/kafka/examples
>> Location: line 19
>> Type: Java Problem
>>
>> There are other errors as well but they are of a similar nature and others
>> dependent on them. I can see the class ShutdownableThread in core and core
>> is compiled properly. The examples project has core setup as  dependency
>> project which seems correct. Also the command line build works just fine.
>>
>> Also I don't see any .class files generated under core/bin. They are
>> present under core/build/classes/main/ though. Is this due to some kind of
>> mismatch between the command line build and Eclipse build?
>>
>> Could you please suggest what am I missing here.
>>
>> Environment:
>> - Eclipse Neon
>> - Java 1.7
>> - Scala 2.10.6
>> - CentOS 6.8
>>
>> thanks
>> -dhwani
>>
>>
>> DISCLAIMER
>> ==========
>> This e-mail may contain privileged and confidential information which is
>> the property of Persistent Systems Ltd. It is intended only for the use of
>> the individual or entity to which it is addressed. If you are not the
>> intended recipient, you are not authorized to read, retain, copy, print,
>> distribute or use this message. If you have received this communication in
>> error, please notify the sender and delete all copies of this message.
>> Persistent Systems Ltd. does not accept any liability for virus infected
>> mails.
>>
>>


DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property of Persistent
Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed.
If you are not the intended recipient, you are not authorized to read, retain, copy, print,
distribute or use this message. If you have received this communication in error, please notify
the sender and delete all copies of this message. Persistent Systems Ltd. does not accept
any liability for virus infected mails.


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message