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 240244 - IllegalStateException: may not call Project.getLookup().lookup(...) inside org.netbeans.modules.maven.j2ee.web.ClientSideDevelopmentSupport registered under @ProjectServiceProvider
Summary: IllegalStateException: may not call Project.getLookup().lookup(...) inside or...
Status: RESOLVED INVALID
Alias: None
Product: javaee
Classification: Unclassified
Component: Maven (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Martin Janicek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-10 18:28 UTC by rodrigorsantos
Modified: 2014-01-14 12:49 UTC (History)
9 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 206459

Attachments
stacktrace (3.56 KB, text/plain)
2014-01-10 18:28 UTC, rodrigorsantos 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rodrigorsantos 2014-01-10 18:28:01 UTC 
This bug was originally marked as duplicate of bug 230054, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 20140109-e0428f98f79d)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.7-b01, Java(TM) SE Runtime Environment, 1.7.0_15-b03
OS: Windows 7

User Comments:
tnleeuw: During maven deploy to Tomcat

GUEST: Running a base maven jsp 'Hello world' webApp with jboss 7.1.1 Final

tnleeuw: Deploying to Tomcat through maven; also project scanning in background

jbsabmello: x

janario: Waiting to tomcat start

rodrigorsantos: <Please provide a description of the problem or the steps to reproduce>

tnleeuw: ... Maven deploy to Tomcat?

KhArtNJava: <Please provide a description of the problem or the steps to reproduce>?

tnleeuw: This happened during deploy to Tomcat

GUEST: just run the project "Maven Scrum Toys"

GUEST: Ran maven project

danfalos: building a maven application

GUEST: just trying to run a simple servlet

mago_ebon: Starting up a new Maven based Java web project

tnleeuw: Exception in deploy

abien: Happened during first deployment of a JavaEE7 application

jskrivanek: I run Maven Java EE 7 project.

mjanicek: Deploying Maven Web project.

KhArtNJava: <Please provide a description of the problem or the steps to reproduce>




Stacktrace: 
java.lang.IllegalStateException: may not call Project.getLookup().lookup(...) inside org.netbeans.modules.maven.j2ee.web.ClientSideDevelopmentSupport registered under @ProjectServiceProvider
   at org.netbeans.modules.projectapi.LazyLookupProviders$1$1.safeToLoad(LazyLookupProviders.java:135)
   at org.netbeans.modules.projectapi.LazyLookupProviders$1$1.beforeLookup(LazyLookupProviders.java:91)
   at org.openide.util.lookup.ProxyLookup.lookup(ProxyLookup.java:215)
   at org.openide.util.lookup.ProxyLookup.lookup(ProxyLookup.java:223)
   at org.openide.util.lookup.ExcludingLookup.lookup(ExcludingLookup.java:142)
   at org.openide.util.lookup.ProxyLookup.lookup(ProxyLookup.java:223)
Comment 1 rodrigorsantos 2014-01-10 18:28:04 UTC 
Created attachment 143814 [details]
stacktrace
Comment 2 Martin Janicek 2014-01-13 14:13:08 UTC 
Don't understand this issue. Class maven.j2ee.web.ClientSideDevelopmentSupport does not even exist anymore (it was refactored to a different module on Sep 2, 2013). Since then no report occurs until now, but even the newest one is referring to this obsolete class and some other code that doesn't exist in the repository (yet the last report is using daily build from 9.1.2014).

Closing as INVALID as I don't think there is anything we can do at the moment.

Rodrigorsantos what kind of build are you using? Daily build or some kind of custom one build from repository sources? Thanks in advanced
Comment 3 Martin Janicek 2014-01-14 12:49:53 UTC 
Rodrigorsantos I just found that you are using pretty old version of maven.j2ee module (version 1.34 - current is 1.53). It's probably the reason why you are still able to reproduce this obsolete issue. If you tell me what kind of build are you using, maybe I will be able to help you. Can't do anything else until then :(