reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Douglas Service <>
Subject Re: REEFJava build fails on Windows?
Date Tue, 04 Oct 2016 00:44:22 GMT
I just synced to Apache reef master and it builds. Your problem is probably
from the commit below. I put a warning in the commit message since I had a
very similar problem where I was getting test errors. To fix the problem, I
ended up pushing all of my branches to github deleting my enlistment and
then cloning my copy of REEF on github. You could probably also do a clean,
roll back to the commit just before this one, do a clean, and then pull the
latestest. I verified the problem only occurs if you do not do a clean in
Visual Studio and Maven before syncing to the commit. There was some
discussion on the dev list, but we probably need a better way to let every
know about these kinds of issues.


[REEF-1611] Move Java .proto files to common directory

This change moves the Java .proto files to lang/common/proto so
the C# side can use the same proto files.

WARNING: Before pulling this change you should clean both the
Java and C# builds; otherwise, you will have artifacts this
version cannot remove that cause test failures on the C# side.


Pull Request:
  This closes #1142 <>

On Mon, Oct 3, 2016 at 5:22 PM, Sergiy Matusevych <> wrote:

> Hi REEF devs,
> Can someone try to build current master from scratch? I am getting the
> following error:
>     [exec]
> C:\Users\sergiym.REDMOND\devel\reef\lang\java\reef-
> wake\wake/../../../../lang/common/proto/RemoteProtocol.proto:
> File does not reside within any path specified using --proto_path (or -I).
> You must specify a --proto_path which encompasses this file.  Note that the
> proto_path must be an exact prefix of the .proto file names -- protoc is
> too dumb to figure out when two paths (e.g. absolute and relative) are
> equivalent (it's harder than you think).
> and eventually it complains that java files that should be generated from
> proto are not there. :(
> I've removed ~/.m2 and cloned the whole repo anew but I am still getting
> this error. Am I the only one getting this error? Any ideas on how to fix
> it?
> Thanks,
> Sergiy.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message