ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <j...@apache.org>
Subject [jira] Commented: (IVYDE-246) Spurious error handling
Date Tue, 16 Nov 2010 13:11:14 GMT

    [ https://issues.apache.org/jira/browse/IVYDE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932453#action_12932453
] 

Nicolas Lalevée commented on IVYDE-246:
---------------------------------------

About the NPE, closing projects are better handled now in the trunk version.

About the file lock error message: I try to do some setup in my windows virtual machine, I
cannot reproduce. Could you be more specific about the settings you are using. It would be
great if you could attach here a sample project I could test on.


> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message