This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 201015 - SharabilityQuery.getSharability(.../.settings) -> NOT_SHARABLE
Summary: SharabilityQuery.getSharability(.../.settings) -> NOT_SHARABLE
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 7.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks: 67900
  Show dependency tree
 
Reported: 2011-08-16 19:11 UTC by Jesse Glick
Modified: 2012-06-20 16:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2011-08-16 19:11:19 UTC
GlobalVisibilityQueryImpl by default considers a dir named ".settings" (i.e. Eclipse settings) invisible, which is fine - I probably do not need to see this in Files etc. But then GlobalSharabilityQueryImpl also treats this file as unsharable, which is not OK: if I have a dir of this kind, even hidden, it can be expected to be in version control.

While there are some patterns such as ~$ for which NOT_SHARABLE is sensible, ^\\.(?!htaccess$).*$ definitely does not fall into this category.

I would recommend just removing GlobalSharabilityQueryImpl; if providers can only guess, UNKNOWN is the preferred result. A proper SCM setup would already be ignoring things like *~ anyway; the purpose of SQ is to let the IDE's SCM integration know about IDE-specific files or folders such as nbproject/private/ which you would not necessarily expect the user's repository to already be configured for, and the patterns in GlobalVisibilityQueryImpl are not relevant for that. My evaluation in bug #67900 comment #12 seems to have been wrong.
Comment 1 Jaroslav Tulach 2011-08-27 13:47:53 UTC
I have to say I have never understood the visibility/sharability queries stuff. Neither I got why these queries need to be part of masterfs. If you want to remove GlobalSharabilityQueryImpl and you believe you understand the consequences, go on.
Comment 2 Jaroslav Tulach 2012-06-20 16:26:41 UTC
Few months without any action by submitter. Probably not that urgent.