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

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

After looked closely, it seems that IvyDE wasn't designed to be used in a "run" 
context. The run context doesn't assume to be executed in a specific project, 
which IvyDE assumes.

First I would say that it is not a bug but a missing feature. But the Eclipse 
API doesn't seperate the two concepts. Implementing the by project 
configuration also mean implementing the project independant one. So it is 
actually a bug.

> IvyDE 1.0.3 "Run configuration" problem with Eclipse 3.x
> --------------------------------------------------------
>
>                 Key: IVYDE-32
>                 URL: https://issues.apache.org/jira/browse/IVYDE-32
>             Project: IvyDE
>          Issue Type: Bug
>          Components: classpath container
>    Affects Versions: 1.1.0, 1.2.0
>         Environment: Windows XP, Eclipse 3.2.0, IvyDE 1.0.3
>            Reporter: Emmanuel Cordente
>            Assignee: Nicolas Lalevée
>             Fix For: 1.3.0
>
>
> I'm having an UI problem using IvyDE with Eclipse 3.1 et 3.2.
> When I add the "IvyDE Managed Dependencies" in my Eclipse project everything 
> work fine, I have the little windows the indicate where is my ivy.xml file 
> and a list of configuration when I select my ivy file.
> But when a try to do the same thing inside the "Run Configuration" to 
> configure a runtime dependencies, I can see the same little windows but the 
> "BROWSE" button doesn't work and it's impossible to find the ivy.xml file.
> I Tryed to put the ivy.xml path explicitely but I can't see the configuration 
> list below the browse button.
> The solution I found for now is to open the .launch file and to choose my 
> configuration directly inside but it's a bit tricky to do.

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

Reply via email to