You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2011/04/25 12:51:07 UTC

[jira] [Resolved] (IVYDE-246) Spurious error handling

     [ https://issues.apache.org/jira/browse/IVYDE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalevée resolved IVYDE-246.
-----------------------------------

    Resolution: Incomplete

No news so I'm guessing this is OK now. Reopen the issue with more inputs if this not the case.

> Spurious error handling
> -----------------------
>
>                 Key: IVYDE-246
>                 URL: https://issues.apache.org/jira/browse/IVYDE-246
>             Project: IvyDE
>          Issue Type: Bug
>          Components: workspace resolver
>    Affects Versions: 2.0.0.final
>         Environment: eclipse.buildId=M20090917-0800
> java.version=1.6.0_20
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
> Command-line arguments:  -os win32 -ws win32 -arch x86 -data C:\Dev\ritchiebd\projects\Workspaces\backtest
>            Reporter: gamhead
>
> We get the following when we are referencing an Ivy properties file in our settings but it is not available
> java.lang.NullPointerException
> 	at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.doGetIvy(IvyClasspathContainerConfiguration.java:494)
> 	at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.getIvy(IvyClasspathContainerConfiguration.java:453)
> 	at org.apache.ivyde.eclipse.cpcontainer.IvyResolveJob.run(IvyResolveJob.java:200)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Although to be fair we are using the Eclipse special notation:
> project:///../build/ivyde-settings.xml
> to pull in our settings from our build eclipse project - and this happens when that project is closed.
> -------------
> Another issue we have is when we try to resolve dependancies but are in a debug/run session in Eclipse. 
> Because the files are locked Ivy cannot replace them , but the way IvyDE reports this is very strange. We get a popup - see attached.
> Impossible to resolve dependencies of com.rbsfm.hft#backtest-scripts;working@lonmw85560
>   unresolved dependency: com.rbsfm.hft#Filter;TRUNK: not found
>   unresolved dependency: com.rbsfm.hft#backtest-api;TRUNK: not found
>   unresolved dependency: com.rbsfm.hft#Filter;TRUNK: not found
>   unresolved dependency: com.rbsfm.hft#backtest-api;TRUNK: not found
>   unresolved dependency: com.rbsfm.hft#Filter;TRUNK: not found
>   unresolved dependency: com.rbsfm.hft#backtest-api;TRUNK: not found
> Looking in the Ivy Console we can see :
> :::: ERRORS
> 	Couldn't delete outdated artifact from cache: C:\ivyrepo\cache\com.rbsfm.hft\Filter\TRUNK\Filter-TRUNK.jar
> 	Couldn't delete outdated artifact from cache: C:\ivyrepo\cache\com.rbsfm.hft\backtest-api\TRUNK\backtest-api-TRUNK.jar
> .. but would be nice to get the error handling on this improved

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira