Re: [iam-dev] Re: Error on updating dependencis

[Abel Muiño Vizcaino <amuino@xxxxxxxxx>]

Yes, it is something in WTP support (I suppose the admintool.fe  
project is a web project?).

The exception is raised from the component supporting the war  
overlay... are you using that maven feature?

From your email, I am not sure if this started happening "without  
reason" or if you did some changes to the project pom (or reimported  
the project or any other action). Do you have any idea of what could  
have changed to start reporting this error?

El 07/04/2010, a las 9:37, Richard Hauswald escribió:

> Update:
> I uninstalled the Eclipse IAM Web tools support and now the
> dependencies are being resolved without errors. So I guess the error
> is located in the wtp support plugin.
>
> On Wed, Apr 7, 2010 at 9:33 AM, Richard Hauswald
> <richard.hauswald@xxxxxxxxxxxxxx> wrote:
> > Hello list,
> > please excuse my silence in the last post - I didn't get the chance  
> > to
> > try the hints. I'll respond as soon as I tried it. Today in ran into
> > another error. When refreshing my dependencies i get the following
> > error in my .log file:
> > !SESSION 2010-04-07 09:28:12.433  
> > -----------------------------------------------
> > eclipse.buildId=unknown
> > java.version=1.6.0_16
> > java.vendor=Sun Microsystems Inc.
> > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
> > Framework arguments:  -product org.eclipse.epp.package.jee.product
> > Command-line arguments:  -os win32 -ws win32 -arch x86 -product
> > org.eclipse.epp.package.jee.product
> >
> > !ENTRY org.eclipse.equinox.registry 2 0 2010-04-07 09:28:14.833
> > !MESSAGE The extensions and extension-points from the bundle
> > "org.aspectj.runtime" are ignored. The bundle is not marked as
> > singleton.
> >
> > !ENTRY org.eclipse.core.jobs 4 2 2010-04-07 09:29:01.849
> > !MESSAGE An internal error occurred during: "Updating classpath
> > container: admintool.fe".
> > !STACK 0
> > java.lang.NullPointerException
> >        at  
> > org 
> > .eclipse 
> > .wst 
> > .common 
> > .componentcore 
> > .internal.resources.VirtualResource.removeLink(VirtualResource.java: 
> > 300)
> >        at  
> > org 
> > .eclipse 
> > .iam 
> > .wtp 
> > .core 
> > .internal 
> > .war 
> > .MavenWarClasspathListener 
> > .addOverlayWarFolders(MavenWarClasspathListener.java:89)
> >        at  
> > org 
> > .eclipse 
> > .iam 
> > .wtp 
> > .core 
> > .internal 
> > .war 
> > .MavenWarClasspathListener.resolved(MavenWarClasspathListener.java: 
> > 57)
> >        at  
> > org 
> > .eclipse 
> > .iam 
> > .jdt 
> > .core 
> > .classpath 
> > .container 
> > .MavenClasspathContainer 
> > .resolveArtifacts(MavenClasspathContainer.java:272)
> >        at  
> > org 
> > .eclipse 
> > .iam 
> > .jdt 
> > .core 
> > .classpath 
> > .container 
> > .MavenClasspathContainer 
> > .refreshClasspath(MavenClasspathContainer.java:141)
> >        at  
> > org 
> > .eclipse 
> > .iam 
> > .jdt 
> > .core 
> > .classpath 
> > .container 
> > .MavenClasspathContainer.newClasspath(MavenClasspathContainer.java: 
> > 181)
> >        at  
> > org 
> > .eclipse 
> > .iam 
> > .jdt 
> > .core 
> > .classpath 
> > .container 
> > .UpdateClasspathJob.runInWorkspace(UpdateClasspathJob.java:80)
> >        at  
> > org 
> > .eclipse 
> > .core 
> > .internal 
> > .resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> >        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> >
> > Any hints on this?
> >
> > Thanks
> > Richard
> >
> > --
> > Richard Hauswald
> > Blog: http://tnfstacc.blogspot.com/
> > LinkedIn: http://www.linkedin.com/in/richardhauswald
> > Xing: http://www.xing.com/profile/Richard_Hauswald
>
>
>
> --
> Richard Hauswald
> Blog: http://tnfstacc.blogspot.com/
> LinkedIn: http://www.linkedin.com/in/richardhauswald
> Xing: http://www.xing.com/profile/Richard_Hauswald
> _______________________________________________
> iam-dev mailing list
> iam-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/iam-dev

--
Abel Muiño - http://ramblingabout.wordpress.com/