Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322141 - NPE in VirtualComponent#create() for validation
Summary: NPE in VirtualComponent#create() for validation
Status: NEW
Alias: None
Product: WTP Common Tools
Classification: WebTools
Component: wst.common (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: Future   Edit
Assignee: Rosendo Martinez CLA
QA Contact: Carl Anderson CLA
URL:
Whiteboard: Maven
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-09 10:08 EDT by Sebastian Oerding CLA
Modified: 2012-05-01 15:50 EDT (History)
1 user (show)

See Also:


Attachments
my logfile with stacktrace (26.73 KB, text/plain)
2010-08-09 10:17 EDT, Sebastian Oerding CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Oerding CLA 2010-08-09 10:08:04 EDT
Build Identifier: 20100617-1415

Hello,

I encounter a really nasty problem and failed to solve it. Even investigation failed in some way, so you might to change the component:

I use Eclipse 3.6.0-JEE and 3.5.2-JEE enriched with Mylyn, Subclipse and m2eclipse. When getting a multi-module-project from the repository via the m2eclipse plugin some errors occur:

1. Each some dependencies are not resolved, the exact unresolved dependencies and the number of unresolved dependencies vary nearly each time a bit. Twice I successfully obtained all projects. If the the project creation fails in the described way, cleaning and rebuilding the projects and so on doesn't make anything better.

By using the JavaHL for Subclipse instead of SVNKit this bug lightens a bit but it still remains there. Most times some error messages about validation error(s) occur. I will attach a biger part of my log with various stacktraces, hopefully can get a better idea what to do next than me.

Maybe this is an inappropriate place but I get a lot of different errors in the .metdadata/.log and don't know where to start Even searching some forums / asking Google didn't reveal a single entry for a similar problem.

Also I noticed for one project, several errors of type validation message, but in the problems view the location is unknown and the description is empty (or null), only a single red error icon shows up.

This errors occur for both named version of Eclipse under Ubuntu 8.04 and also after a dist-upgrade to 10.04.



Reproducible: Sometimes

Steps to Reproduce:
1.Create a Maven multi-module project in SCM (Subversion) (Only once required)
2.Add some dependencies especially make some modules to be interdependent
3.Checkout projects from SCM
Comment 1 Sebastian Oerding CLA 2010-08-09 10:17:50 EDT
Created attachment 176156 [details]
my logfile with stacktrace

the log contains a lot of stacktraces especially the mentioned one. Even if the bug is due to an added plugin / external component,please give me a hint to track it down.
Comment 2 Frederic Fusier CLA 2010-08-09 11:45:54 EDT
It looks to be a problem with the WST validation plugin, moving to Web Tools for further investigation.
Comment 3 Sebastian Oerding CLA 2010-08-12 03:11:33 EDT
On one of my colleagues pc (Windows 7, Eclipse 3.4.2, JEE + Subclipse, Mylyn and m2eclipse) there is a message about conflicting libs.

Maybe this has been broken somewhere on the road to 3.6.0? At the moment I'm not completely sure but I think that the same error occurs when I open my workspace with 3.5.1 or 3.5.2. Should I further investigate?

- Sebastian
Comment 4 Sebastian Oerding CLA 2010-08-12 03:37:25 EDT
Hello,

further investigation lead to the following results:

The only real error is the validation. The other errors in the provided logfile cause by other plugins. Especially the bugs mentioned to occur with m2eclipse seem to be a problem of m2eclipse / the underlying Maven. The don't occur when I restart Eclipse and do a fresh checkout.


The validation error occurred on a dynamic web project having a folder WebContent/WEB-INF/lib/ containing some libs. These libs conflicted with libs from the Maven dependencies, after deleting the libs from the WEB-INF/lib folder everything is fine and the validation error vanishes.

So the bug seems to be cause when libs from Maven dependencies conflict with libs in place. So maybe useful when trying to reproduce the bug.

- Sebastian
Comment 5 David Williams CLA 2010-09-27 10:16:42 EDT
Assuming this is the relevant message for WTP. 


!ENTRY org.eclipse.core.jobs 4 2 2010-08-09 15:33:03.956
!MESSAGE An internal error occurred during: "Updating Maven Configuration".
!STACK 0
java.lang.NullPointerException
	at org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.create(VirtualComponent.java:363)
Comment 6 Carl Anderson CLA 2011-05-24 11:42:32 EDT
Assigning to Rosendo for initial investigation.