]
Alexey Kazakov commented on JBIDE-12129:
----------------------------------------
.settings/org.eclipse.wst.common.component points to the missing folder WebContent:
{code}
...
<wb-resource deploy-path="/" source-path="/WebContent"
tag="defaultRootSource"/>
{code}
I guess it should be something like:
{code}
...
<wb-resource deploy-path="/" source-path="/resources"
tag="defaultRootSource"/>
<wb-resource deploy-path="/" source-path="/view"/>
...
{code}
It cause this exception.
Slava, we should check if web content exists.
org.jboss.tools.common.validation.JBTValidationException
--------------------------------------------------------
Key: JBIDE-12129
URL:
https://issues.jboss.org/browse/JBIDE-12129
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.CR1
Reporter: Daniel Hinojosa
Assignee: Viacheslav Kabanovich
Fix For: 3.3.1
Attachments: .classpath, .project, debug-glassfish-grapesofstash.launch,
debug-jboss-grapesofstash.launch, explode.launch, grapesofstash.launch, settings.zip
In reference to
https://issues.jboss.org/browse/JBSEAM-4960
In an attempt to reconfigure the older .project, .classpath, and .settings/* files for it
to be compatible with the latest JBIDE, I get an NPE in the process:
{noformat}
org.jboss.tools.common.validation.JBTValidationException
at
org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101)
at
org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.NullPointerException
at
org.jboss.tools.jsf.web.validation.FacesConfigValidator.validateAll(FacesConfigValidator.java:314)
at
org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:132)
at
org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84)
... 2 more
{noformat}
This could be me either my doing, or perhaps there is a bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: