Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <17957879.50151291224913033.JavaMail.jira@thor>
Date: Wed, 1 Dec 2010 12:35:13 -0500 (EST)
From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Commented: (IVYDE-268) Resolve errors should be build
 errors, not eclipse errors
In-Reply-To: <9463045.327631290802453204.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/IVYDE-268?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12965=
755#action_12965755 ]=20

Nicolas Lalev=C3=A9e commented on IVYDE-268:
---------------------------------------

Actually I was wrong, IvyDE is already pushing errors in the problems view =
just like Maven does (I should better know the software I maintain ! :)).

I think I still let the errors popup because sometime the error message can=
 be quite long and to manage readability, the carriage return are inserted.

See for instance:
{noformat}
Error while resolving the ivy instance for ivy.xml[runtime, test, compile] =
in 'cas':
  The ivy settings file 'file:/Users/hibou/dev/svn/tools/build/ivysettings.=
xml' could not be parsed: failed to load settings from file:/Users/hibou/de=
v/svn/tools/build/ivysettings.xml: The element type "ivysettinssgs" must be=
 terminated by the matching end-tag "</ivysettinssgs>".
{noformat}

And this is not readable in the problems view... It would be not much bette=
r if everything was on one line. Maybe we can hook something on the double =
click on the Ivy problem ?

And another case which should be taken care: in the launch configuration we=
 can reference ivy files on the file system which is not part of the worksp=
ace, so the problem view cannot be used for reporting that kind of errors. =
Here a popup should still be mandatory, but a dedicated one would probably =
be better than the default error one, for sure.


> Resolve errors should be build errors, not eclipse errors
> ---------------------------------------------------------
>
>                 Key: IVYDE-268
>                 URL: https://issues.apache.org/jira/browse/IVYDE-268
>             Project: IvyDE
>          Issue Type: Bug
>          Components: workspace resolver
>    Affects Versions: 2.1.0
>            Reporter: Adam Lehenbauer
>
> when maven can't find dependencies for a build, the errors appear under t=
he _Problems_ view. When ivy can't resolve or download a dependency, it app=
ears under the _Error Log_ and notifies with a pop-up dialog.

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