[
https://issues.apache.org/jira/browse/AVRO-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Zeyliger updated AVRO-146:
---------------------------------
Attachment: AVRO-146.patch.v2.txt
Patrick,
Thanks for the reference. I'm uploading a new patch, which:
# Works. (I dropped the .project file in the previous patch, so, had you tried
it, it wouldn't have worked :/)
# Uses ant-eclipse. For simple things, ant-eclipse seems to work well. The
bixo project (see
http://www.google.com/codesearch/p?hl=en&sa=N&cd=1&ct=rc#hMNiHrMJ4Bc/ivy.xml&q=ivy.xml%20ant-eclipse&l=44
) manages to pull in ant-eclipse via Ivy, but I haven't been able to figure
out how they do it. So, I followed zookeepers approach and pull it in
manually. Patrick --- any clever thoughts here?
# Changes build.xml to separate out build/test/classes and
build/test/generated/classes. The only things that Avro tests absolutely need
paranamer to run on are the classes generated from the schemas. By having two
distinct classpaths in there, it's easier to configure eclipse to compile the
tests themselves, but to rely on ant to build the generated code. That's a
mouthful: I think, in general, it's reasonable to have one "classes" directory
per "src" directory, and this makes this true.
# Seems to be snappier, because Eclipse no longer calls ant; you only need to
call it when you change code that needs to get generated.
If someone here uses Eclipse, would be great to have someone else try it.
-- Philip
> 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
>
>
> 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.
