[
https://issues.apache.org/jira/browse/AVRO-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784572#action_12784572
]
Tom White commented on AVRO-184:
--------------------------------
Is this ready to be committed?
> Better eclipse configuration support
> ------------------------------------
>
> Key: AVRO-184
> URL: https://issues.apache.org/jira/browse/AVRO-184
> Project: Avro
> Issue Type: Bug
> Components: java
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Priority: Minor
> Attachments: AVRO-184.patch, AVRO-184.patch
>
>
> Jira AVRO-146 enabled easy eclipse setup for Avro. But it had a few minor
> issues:
> - It downloaded the ant-eclipse plug-in directly without using Ivy. This
> problem has been acknowledged in the JIRA itself. Thus if you clean up the
> project and rebuild, it'll go and fetch the plug-in again. That means one
> cannot do "ant clean" when offline.
> - Eclipse project used the external jar files from ivy cache locations
> rather than from the place where they have been retrieved into. It's not a
> big issue, the only concern is that ant and eclipse will use two different
> sets of jars though with identical contents.
> - Ant-eclipse plug-in was downloaded into build/lib, which will get
> included in ant builds, though the builds would never use it.
> The attached patch fixes all these issues. The ant-eclipse plug-in now gets
> retrieved by ivy into a separate directory build/lib/ant-eclipse.
> Unfortunately, the is patch adds a new file ivysettings-ant-eclipse.xml in
> the base directory. Alas, one cannot specify ivy settings inline in
> build.xml, you need an external settings file.
> There is still one more small problem. Eclipse projects traditionally use the
> built-in JUnit instead of external jars. The use of built-in JUnit within a
> project is specified by a classpathentry of kind "con" in the .classpath
> directory. The projects with JUnit will have two classpathentries of "con"
> kind - one for JRE and the other for JUnit. But Ant-eclipse does not support
> more than one classpathentry of "con" kind, which is already used by the JRE.
> Thus we cannot fix this problem until ant-eclipse removes this limitation.
> Eclipse users, please give this patch a try. Thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
