[
https://issues.apache.org/jira/browse/AVRO-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766638#action_12766638
]
Doug Cutting commented on AVRO-146:
-----------------------------------
Philip, you told me a lot about Eclipse's awesomeness, and I'll trust you on
that. Viva Eclipse!
I think you may have answered one of my questions: the reason why you don't
want Eclipse to compile everything via Ant (my first choice) is that this would
somehow disable lots of Eclipse awesomeness. Is that right? Eclipse doesn't
just need to know where the sources and classes are, it needs to generate the
.class files itself in order to be most awesome?
I don't think you answered my other implicit question, so I'll make it
explicit: can Eclipse actually not handle multiple source trees that share a
classes directory? You seemed to motivate this change with the assertion that
Avro only needs to run paranamer on generated code, but that's not true. It
only needs to run it on Java interfaces used as protocols, a set that
intersects generated code, but is neither a proper superset nor subset. Your
statements make it clear that you dislike this sharing, but not whether this is
mandated by Eclipse. Is it actually?
We had Eclipse support built into Hadoop a long time ago. It compiled, but
wasn't maintained. Nice, innocent folks would try to use it in releases and it
would fail. I want to avoid that. Making this as simple as possible without
losing intense awesomeness is my goal here.
> configuration to work on Avro within Eclipse
> --------------------------------------------
>
> Key: AVRO-146
> URL: https://issues.apache.org/jira/browse/AVRO-146
> Project: Avro
> Issue Type: New Feature
> Reporter: Philip Zeyliger
> Assignee: Philip Zeyliger
> Attachments: AVRO-146.patch.txt, AVRO-146.patch.v2.txt,
> AVRO-146.patch.v3.txt
>
>
> The soon-to-be-attached patch lets you work on Avro from within Eclipse, if
> that's your style.
> I've added the following to the README:
> {quote}
> USING ECLIPSE
> To use Eclipse, use the "ant eclipse" target to trigger generating a
> .classpath
> file, and also trigger compilation (to pull in the maven dependencies, etc.)
> You must also make sure that your avro checkout directory is "avro". You
> should then be able to create an Eclipse project pointed to your checkout, and
> run the unit tests from Eclipse's runner.
> Note that the "Eclipse Builder" is configured to compile twice: once with
> Eclipse's built-in compiler, and another time with ant. Eclipse is happier
> this way, though the classpath is configured to ignore Eclipse's compilation.
> {quote}
> Everything here is incomprehensible XML boilerplate. There's a new ant
> target to create the .classpath file.
> I'm able to run all but the interop test that requires a server from within
> Eclipse. I welcome other Eclipse users trying this out to see if it works.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
