[
https://issues.apache.org/jira/browse/IVYDE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653233#action_12653233
]
Nicolas Lalevée commented on IVYDE-133:
---------------------------------------
Thanks for looking into it Matt. Effectivelly the code is badly assuming an
order of loading.
Althouth your solution will avoid the NPE, but we will loose the notifications.
IvyDE should probably buffer the non transmitted status when the decorator is
not yet there, and as soon as it has been loaded, fire the pending changes.
> 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.
