Guessing from your error messages, I’d guess you are using Eclipse, correct? In eclipse you can press ctrl+shift+o, which tries to resolve the imports, and gives you an list of possibilities if there are multiple that match. Very handy tool.
Eclipse has a long standing bug in auto-import of nested interfaces or classes in specific cases (if I remember correctly, when there are multiple possibilities of certain kinds for the nested interface), and unfortunately this happens with a lot of Vaadin listeners written as anonymous classes. This is complicated by the fact that the error message you get is not very good. You are especially likely to see the issue if you have configured “organize imports” as a “save action” for Java files.
Explicit “Organize imports…” can often fix this as Jens suggested, as can manually adding imports for the correct classes (either Property in your example or Property.ValueChangeListener and then removing “Property.” when declaring the listener anonymous class).