search

duckAsteroid / protobuf-dt

Automatically exported from code.google.com/p/protobuf-dt
0 stars 0 forks source link

"Compile .proto files on save" creates the directory but doesn't compile proto files (Java) #172

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a .proto file inside of a Java project.
2. Enter a simple correct Message.
3. Save the file.

What is the expected output? What do you see instead?

With "Compile .proto files on save" enabled for Java and pointing to src-gen, I 
expect to see the directory with the proto outputs. Instead, the directory is 
created (so I know the plugin is correctly hooked into the save process), but 
the compiled protocol buffer classes are never generated. This happens on new 
projects as well as existing ones.

What version of the product are you using? On what operating system?

Protocol compiler 2.4.1, protobuf-dt 1.1.1.201112160549, TMF XText 2.1.1 (due 
to the known issue with 2.2.1), Eclipse 3.7 (Indigo) 20110916-0149, Windows 7.

Please provide any additional information below.

No information appears in the error log. The proto compiler is referenced from 
my PATH, but the same problem occurs when it is referenced directly. "Build 
automatically is checked", the project has the XText Proect Builder, and the 
.proto compiles perfectly and is found by the project when I invoke the 
protocol compiler manually from the command line.

Let me know if there's any additional information which will help!

Original issue reported on code.google.com by mich...@barnathan.name on 27 Dec 2011 at 2:51

GoogleCodeExporter commented 9 years ago

Original comment by alr...@google.com on 11 Jan 2012 at 11:10

GoogleCodeExporter commented 9 years ago

Original comment by alr...@google.com on 13 Jan 2012 at 3:21

GoogleCodeExporter commented 9 years ago 
Unfortunately I couldn't reproduce this issue. I created Issue 190. protobuf-dt 
will now print protoc's output to the console. This way at least you can verify 
if integration with protoc was properly set up. I'm not closing this bug. 
Hopefully we can find the root of the issue you are experiencing.

Original comment by alr...@google.com on 23 Jan 2012 at 7:36

GoogleCodeExporter commented 9 years ago 
Thanks. With the new release, I now see a dialog box with the message 'Reveal 
End of Document' has encountered a problem: An internal error has occurred. 
Argument not valid". Of note, I upgraded to XText 2.2 with the new protocol 
buffer editor (that seems to be working smoothly now; thanks for the support).

Original comment by mich...@barnathan.name on 27 Jan 2012 at 2:45

GoogleCodeExporter commented 9 years ago 
Figured this out: protoc was compiled under Cygwin, and it is disagreeing with 
the Windows-formatted --proto_path, yielding "directory does not exist" errors 
on the console. This is something I can work around fairly easily now that I 
know the cause, probably isn't a particularly common use case, and is something 
that is quite clear to debug now that the console output is echoed, so feel 
free to close this out.

Original comment by mich...@barnathan.name on 15 Feb 2012 at 3:12

GoogleCodeExporter commented 9 years ago 
Great! thanks for the update.

Original comment by alr...@google.com on 15 Feb 2012 at 6:39