duckAsteroid / protobuf-dt

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

Import paths ineffective in protobuf-dt 1.2, on Windows #204

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

In a project I have a .proto file with

import "com/foo/bar/a.proto";

The project configuration specifies the import path 
"${workspace_loc:/{$project}/target/protobuf/dependencies/a}" where the file 
"com\foo\bar\a.proto" can indeed be found.

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

An error that reads 'The import "com/foo/bar/a.proto" was not found.' is 
displayed in the editor of the aforementioned .proto file. I believe the file 
should be imported correctly.

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

This used to work, and then it broke about a month ago when I updated 
protobuf-dt. I cannot be certain, but I'm pretty sure it was when going from 
1.1.1 to 1.2.1

I'm currently using Eclipse 3.7.1 with protobuf-dt 1.2.2 on Windows 7 with Java 
1.7.0_02 (all 64-bit versions where applicable)

Finally, I'm attaching a minimal failure case. It contains two eclipse projects 
with the error I've just described. These projects have a reference to the 
protobuf-java runtime jar (version 2.4.1) which I obviously didn't include in 
the zip and will have to be fixed before looking at the issue.

Thanks in advance for looking at this.

Original issue reported on code.google.com by chwthe...@gmail.com on 22 Feb 2012 at 9:37

Attachments:

GoogleCodeExporter commented 9 years ago
Thanks very much for providing a reproducible use case! I'll be taking a look 
at this issue today.

Original comment by alr...@google.com on 2 Mar 2012 at 5:59

GoogleCodeExporter commented 9 years ago
This seems to be a problem in Windows. On my mac, the provided projects don't 
show that error.

Original comment by alr...@google.com on 2 Mar 2012 at 6:30

GoogleCodeExporter commented 9 years ago
I was able to reproduce this issue on Windows.

Original comment by alr...@google.com on 3 Mar 2012 at 9:36

GoogleCodeExporter commented 9 years ago
Fixed the bug in Windows. Need to test fix in Linux and Mac.

Original comment by alr...@google.com on 4 Mar 2012 at 3:43

GoogleCodeExporter commented 9 years ago
Changes from previous comment: r8fe8805280df

Original comment by alr...@google.com on 4 Mar 2012 at 3:43

GoogleCodeExporter commented 9 years ago
Fixed!

Original comment by alr...@google.com on 4 Mar 2012 at 4:31

GoogleCodeExporter commented 9 years ago
Thanks for such a fast resolution!

Original comment by chwthe...@gmail.com on 6 Mar 2012 at 3:25