Are you using Windows by any chance?
On Aug 4, 11:54 am, Tai maitai.tru...@gmail.com wrote:
I got a strange behaviour when compiling a protofile (e.g.
MyClass.proto). The generated java class is then called MyClassProto.
All other proto files works fine. As a workaround I have added the
Yes, I am using Windows XP and Eclipse 3.5
On 4 Aug., 19:49, Stefan sneg...@gmail.com wrote:
Are you using Windows by any chance?
On Aug 4, 11:54 am, Tai maitai.tru...@gmail.com wrote:
I got a strange behaviour when compiling a protofile (e.g.
MyClass.proto). The generated java class is
What it is also funny is that my file ADMObjectHandleMessage.proto
looks like this:
package com.qnamic.base.agent;
option java_outer_classname = ADMObjectHandleMessage;
message ADMObjectHandle {
optional string host = 1;
optional string agent = 2;
optional string path = 3;
Thanks. Your were pointing into the right direction. It wasn't the
filename but the compile argument when using ant:
project name=Create PB classes default=generate
basedir=../../../..
target name=generate
exec executable=D:/development/workspace/Platform/dev/jars/
protoc
Yes, that's correct. If the Win32 API strips trailing whitespace from file
names when opening them, that would explain why there was no error -- but
that's very strange behavior IMO.
On Tue, Aug 4, 2009 at 4:26 PM, Tai maitai.tru...@gmail.com wrote:
This could be a windows problem where white
That's not strange. That's a Windows feature :-)
On 5 Aug., 01:50, Kenton Varda ken...@google.com wrote:
Yes, that's correct. If the Win32 API strips trailing whitespace from file
names when opening them, that would explain why there was no error -- but
that's very strange behavior IMO.
On
