[
https://issues.apache.org/jira/browse/IMPALA-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Zeyliger resolved IMPALA-5836.
-------------------------------------
Resolution: Fixed
{code}
commit b524a5ce69945fb2c7a7667bd2a66f371161bc2a
Author: Philip Zeyliger <[email protected]>
Date: Thu Aug 24 09:44:04 2017 -0700
IMPALA-5836: Improvements to Eclipse frontend configuration.
Having recently gone through setting up Eclipse for frontend debugging,
I'm amending the process a tad to make it smoother for new developers.
* Adds the JDK sources package to the developer bootstrap
process. These are useful if you need to point Eclipse to the source
of Java libraries and are harmless to everyone else.
* Defaults to "downloadSource" for the "mvn eclipse:eclipse" plugin.
This was being set explicitly in the Wiki instructions, but
there's no reason not to set it on by default for everyone.
* Adds a "launcher" file for debugging the FE. Instead of creating
a debug configuration manually, it's possible to share these across
developers by checking them in. I checked it in via a mechanism
that "mvn eclipse:eclipse" has to create additional files, to
avoid literring the directory for non-Eclipse users.
* Changes the output directory used by Eclipse's compiler to
a different one than Maven uses. Because we start Impala
from the commandline, it's easy to start Impala and then
change a line of Java, which forces Eclipse to kick in and
replace the .class files. When this happens, the existing Impala
starts complaining about class not found, because the underlying
files have been overwritten. It's preferable to separate the
directories and rely on Maven for the compiled Java.
Change-Id: Ia723fbf706cf409a8fb6b5ff0297c2b1ff7c9590
Reviewed-on: http://gerrit.cloudera.org:8080/7803
Reviewed-by: Dimitris Tsirogiannis <[email protected]>
Tested-by: Impala Public Jenkins
{code}
> Eclipse frontend debugging setup requires manual steps like creating a
> launcher
> -------------------------------------------------------------------------------
>
> Key: IMPALA-5836
> URL: https://issues.apache.org/jira/browse/IMPALA-5836
> Project: IMPALA
> Issue Type: Bug
> Reporter: Philip Zeyliger
> Assignee: Philip Zeyliger
> Priority: Minor
>
> When setting up Eclipse per
> https://cwiki.apache.org/confluence/display/IMPALA/Eclipse+Setup+for+Impala+Development,
> you have to do some manual steps like setting up a launcher for debugging.
> This can be simplified by having the build do more of it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
