[
https://issues.apache.org/jira/browse/IVYDE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660050#action_12660050
]
Nicolas Lalevée commented on IVYDE-133:
---------------------------------------
The more I look into this, the more I see that kind of problem marker is a hack
to work around that the JDT API doesn't provide extended management of
classpath containers.
The IvyClasspathContainerDecorator is actually trying to redo what exist for
IResource (classpath containers are not IResource):
org.eclipse.jdt.ui.ProblemsLabelDecorator.
I think a more proper solution will be to use the already existing marker
management, and then more than trying to put an error marker on the classpath
container, the error marker will on the java project containing the problematic
classpath container.
If there is no objection, I will change it.
> The decorators can throw a NPE at startup
> -----------------------------------------
>
> Key: IVYDE-133
> URL: https://issues.apache.org/jira/browse/IVYDE-133
> Project: IvyDE
> Issue Type: Bug
> Affects Versions: 2.0.0.beta1
> Reporter: Nicolas Lalevée
> Assignee: Nicolas Lalevée
> Priority: Minor
> Fix For: 2.0.0.final
>
>
> When launching Eclipse, and if there are some failing resolve job, a NPE can
> be raised:
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.setConfStatus(IvyClasspathContainerConfiguration.java:329)
> at
> org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.getModuleDescriptor(IvyClasspathContainerConfiguration.java:634)
> at
> org.apache.ivyde.eclipse.cpcontainer.IvyResolveJob.run(IvyResolveJob.java:200)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> This may be due to the way the decorator listeners are accessed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
