Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » AccessControlException in eclipse-based product when using New Plugin Project wizard
AccessControlException in eclipse-based product when using New Plugin Project wizard [message #1834393] Mon, 09 November 2020 15:54
Missing name Mising name is currently offline Missing name Mising nameFriend
Messages: 1
Registered: July 2009
Junior Member
We develop our own product based on Eclipse. Since Eclipse 4.14 (2019-12) we experience a problem in our product when creating a new plugin project. It does not happen in a plain eclipse without our plugins installed, but in our product it is always reproducible with these steps (works on Windows and linux):

1. Start the product with a fresh workspace
2. Open New Plugin Project wizard
3. Enter some project name and press Next.
4. Press Finish

This causes an error like this (the listed plugin differs between different attempts): access denied ("" ".../plugins/" "read")
at java.lang.SecurityManager.checkPermission(
at java.lang.SecurityManager.checkRead(
at java.util.Spliterators$ArraySpliterator.forEachRemaining(
at java.util.concurrent.CountedCompleter.exec(
at java.util.concurrent.ForkJoinTask.doExec(
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(
at java.util.concurrent.ForkJoinPool.runWorker(

Sometimes the project is created, sometimes it isn't. But when I do the same again without restarting (or just press Finish again in case the wizard is still open), it does not happen again.

From what I know we have not limited permissions through policies, we even tried to get rid of this by explicitly granting all permissions. And if this was the issue, it should happen regardless of the Eclipse version, but it does not happen with Eclipse 4.12 (that was the base of the previous version of our product). I even built a new package of our current product version based on 4.12 to see if this is caused by some change on our side. But with that package (our current plugins installed in Eclipse 4.12), it still does not happen.

We sometimes see something similar when importing plugin projects into the workspace, then it happens during "Initializing plug-in models".

It feels like something is not properly initialized when starting up the product, but I don't know if we are doing something wrong or if we somehow trigger a rare Eclipse bug that was introduced after 4.12. I already checked the start levels in the product configuration using the Add Recommended button, everything looks fine there.

Does anyone have any idea what could cause this? And if not, can anyone give advise about how to get more information to narrow down the search?
Previous Topic:Product Export with JDK 11
Next Topic:PDE build failing with java 11.
Goto Forum:

Current Time: Sun Jan 29 20:25:24 GMT 2023

Powered by FUDForum. Page generated in 0.10132 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top