That's not going to remove the project from your IDE. When I saw Jason's commit went through, I removed the project, updated maven modules metadata, and rebuilt after the next time I rebased. Then all was well.
On Mon, Apr 6, 2015 at 1:52 PM, Daniel Barclay <[email protected]> wrote: > You can safely delete the module from your working directory. >> > > Thanks. > > Why didn't my rebasing of my branch on master remove the module? > > Daniel > > > Jason Altekruse wrote: > >> The interpreter module was removed in a recent commit to make the >> interpreter usable at planning time. >> >> The interpreter code was committed a few months ago, but only had unit >> tests written against it in its own module. To make the interpreter work >> with the other modules and hook it up to planning rules it needed to be >> refactored, the way we chose to refactor it actually removed the need for >> the separate module and build step. You can safely delete the module from >> your working directory. >> >> https://github.com/apache/drill/commit/0aa8b19d624d173da51de36aa164f3 >> 435d3366a4 >> >> -Jason Altekruse >> >> On Mon, Apr 6, 2015 at 1:20 PM, Daniel Barclay <[email protected]> >> wrote: >> >> What's going on with the drill-interpreter module? >>> >>> For while now, in Eclipse it shows up as having errors (e.g., that >>> org.apache.drill.BaseTestQuery is unknown), even after I issue the Maven >>> -> Update >>> Project ... command on it. >>> >>> >>> Daniel >>> -- >>> Daniel Barclay >>> MapR Technologies >>> >>> > > -- > Daniel Barclay > MapR Technologies > >
