Ticket #5878 (new defect)
ClassPathExplorer path problem
| Reported by: | Dmitry Kubrikov | Owned by: | ticketmaster |
|---|---|---|---|
| Priority: | normal | Milestone: | Maintenance backlog |
| Component: | Core Framework | Version: | 6.4.6 |
| Keywords: | Cc: | matti.tahvonen@…, stefan.goldmann@… | |
| Hours estimate: | Hours done: | ||
| Depends on: | |||
| Workaround: | |||
| Pro Account: | Mark as Priority | ||
Description
Incorrect processing path containing a "." at the beginning of the directory.
Class: ClassPathExplorer
Method: include
Code:
if (file.isHidden() || file.getPath().contains(File.separator + ".")) {
return;
}
Example of path: D:\Sources\Vaadin\test-server\.idea\out\production\Test\
For this path, none of the recursive directory will not be included in locations.
Change History
comment:1 Changed 3 years ago by Artur Signell
- Cc matti.tahvonen@… added
- Component changed from undefined to Widgetset builder
- Milestone set to Vaadin 6.4.7
comment:2 Changed 3 years ago by fabdouglas
I had the same problem with Eclipse (.metadata) until I switch the server binary location outside this directory.
I don't think this can be fixed. Removing the ".xxxx" directories from the exclusion might cause duplicate or wrong results because of ".backup", ... Also it's not possible to exclude each separated well known system, temp, etc. folders.
Anyway, it's not a good practice to locate the server deployment's binaries in the default ".idea" or ".metadata" folders. In addition, this practice may cause to reach easily the 255 chars limitation of Windows's path.
comment:5 Changed 2 years ago by Artur Signell
- Milestone changed from Vaadin 6.6.1 to Maintenance backlog
comment:6 Changed 22 months ago by Artur Signell
- Component changed from Widgetset builder to Core Framework
comment:7 Changed 6 days ago by s.goldmann
I am putting my stuff under "~/.eclipse/workspace", which is a valid use case under Linux, in my opinion.
I can understand the possible trouble that the general inclusion of ".xxx" directories can cause, but nevertheless the user should at least have an option to manually overwrite this behaviour.
A possible solution could be a dedicated "-D" VM parameter, either to generally include all of ".xxxx", or to include a dedicated list as given in the parameters value.
