Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <18909741.107681289913074034.JavaMail.jira@thor>
Date: Tue, 16 Nov 2010 08:11:14 -0500 (EST)
From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Commented: (IVYDE-246) Spurious error handling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/IVYDE-246?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12932=
453#action_12932453 ]=20

Nicolas Lalev=C3=A9e 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 vir=
tual machine, I cannot reproduce. Could you be more specific about the sett=
ings you are using. It would be great if you could attach here a sample pro=
ject 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=3DM20090917-0800
> java.version=3D1.6.0_20
> java.vendor=3DSun Microsystems Inc.
> BootLoader constants: OS=3Dwin32, ARCH=3Dx86, WS=3Dwin32, NL=3Den_GB
> Command-line arguments:  -os win32 -ws win32 -arch x86 -data C:\Dev\ritch=
iebd\projects\Workspaces\backtest
>            Reporter: gamhead
>
> We get the following when we are referencing an Ivy properties file in ou=
r settings but it is not available
> java.lang.NullPointerException
> =09at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfigura=
tion.doGetIvy(IvyClasspathContainerConfiguration.java:494)
> =09at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfigura=
tion.getIvy(IvyClasspathContainerConfiguration.java:453)
> =09at org.apache.ivyde.eclipse.cpcontainer.IvyResolveJob.run(IvyResolveJo=
b.java:200)
> =09at 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.=20
> 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;work=
ing@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
> =09Couldn't delete outdated artifact from cache: C:\ivyrepo\cache\com.rbs=
fm.hft\Filter\TRUNK\Filter-TRUNK.jar
> =09Couldn't delete outdated artifact from cache: C:\ivyrepo\cache\com.rbs=
fm.hft\backtest-api\TRUNK\backtest-api-TRUNK.jar
> .. but would be nice to get the error handling on this improved

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.