Demetra on OS X Silliness - Required Administrator Rights

I created a bug report for this one but that was quickly dismissed. Unfortunately it is not possible to re-open closed JIRA issues, so I'll try again here :)

It looks like Demetra on OS X uses an undocumented and unsupported API on OS X, /dev/fsevents and because of that it requires the Demetra user to be an Administrator. Because of that Demetra requires me to enter an administrator passord during startup. Completely silly if you ask me.

This code is used for getting notifications about files that were changed outside of IDEA.

I don't understand why an undocumented API that requires admin privileges is part of an end-user application like IDEA. Also the previous versions of IDEA have always done it the 100% Java way without any problems.

So my request is to get rid of this or at least give an option to people to disable that code. It is annoying and completely unnecessary.

S.

1 comment

Hello Stefan,

SA> I created a bug report for this one but that was quickly dismissed.
SA> Unfortunately it is not possible to re-open closed JIRA issues, so
SA> I'll try again here :)
SA>
SA> It looks like Demetra on OS X uses an undocumented and unsupported
SA> API on OS X, /dev/fsevents and because of that it requires the
SA> Demetra user to be an Administrator. Because of that Demetra
SA> requires me to enter an administrator passord during startup.
SA> Completely silly if you ask me.
SA>
SA> This code is used for getting notifications about files that were
SA> changed outside of IDEA.
SA>
SA> I don't understand why an undocumented API that requires admin
SA> privileges is part of an end-user application like IDEA. Also the
SA> previous versions of IDEA have always done it the 100% Java way
SA> without any problems.

As already explained, there is one small but important difference between
the 100% Java way and the Demetra way: performance. If you know of any way
to achieve the same performance benefits without using undocumented APIs
that require amdin privileges, we will be very happy to implement it.

SA> So my request is to get rid of this or at least give an option to
SA> people to disable that code.

The option is right there: press Cancel in the password prompt dialog. The
old 100% Java way will be used in this case.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Please sign in to leave a comment.