[
https://issues.apache.org/jira/browse/AVRO-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767401#action_12767401
]
Doug Cutting commented on AVRO-146:
-----------------------------------
> If we can separate out the files that paranamer runs on [ ... ]
I agree that this is a potential problem. Currently it does not impact build
time significantly. This should be addressed as a separate issue. Ideally we
could change things like this in the build without breaking Eclipse projects,
e.g., if Eclipse used Ant for all compilation, but that doesn't seem acceptable
to you.
> If we're generating code, can't we just generate the parameter information
> and stuff it into a static field in the interface, and be done with it?
Yes, we could probably do this for generated code, but we still need Paranamer
for reflected code. For generated interfaces, in fact, we can simply include
the Avro protocol as a constant and be done with it, just as we include the
Avro schema in generated classes.
Is the current version of the patch something that you feel is ready to commit?
If so, can some other Eclipse user confirm that it also works for them?
> 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.
