Re: Update Center write permission check prevents users from updating

Life saver. Thanx a lot ! Yes, I see my Branding module had
nbm.is.global=true   never put that there but for sure that's the culprit
causing all the headaches. For now I will also allow to modify the app.conf
by adding -J-Dplugin.manager.install.global=false which also solves the
issue.

On Thu, May 4, 2017 at 7:36 AM, stephen cumminger <
[email protected]> wrote:

> You need to set:
>
> nbm.is.global=false
>
> in the Project Properties for each module you have. Without this, the
> updater is trying to install to the Program Files directory which is
> restricted. With this setting, the downloaded files will be saved in the
> User's AppData related folder for your app; which the app will find and
> apply on next startup.
>
>
> Stephen Cumminger
>
> -----Original Message-----
> From: bruehlicke [mailto:[email protected]]
> Sent: Thursday, May 4, 2017 9:13 AM
> To: [email protected]
> Subject: [platform-dev] Update Center write permission check prevents
> users from updating
>
> Nb 8.2 app installed by User. When User gets new updates via a private
> Update Center the Platform app returns with "Write Permission Problem",
> "You don't have permissions to install plugin xyz into the installation
> directory" - starting the app with "Run as administrator" does the trick.
> Some other installs work just fine.
>
> From http://bits.netbeans.org/8.0/javadoc/org-netbeans-modules-
> autoupdate-services/overview-summary.html and
> http://bits.netbeans.org/8.0/javadoc/org-netbeans-modules-
> autoupdate-services/apichanges.html#check-write-permission I see some
> write permissions were added to the API since my earlier 6.5 based version
> which did not have this check.
>
> Though I do understand the need to check for write permission, I am just
> confused why this is happening when it is the SAME user who installed the
> initial application locally and runs it locally and who is getting the
> updates locally to install - why the error - all the same user on same
> machine ?
>
>
> Does any have some suggestions/best practices how to avoid this ?
>
>
>
>
>