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] Updated: (IVYDE-70) The project ivy configuration is not taken into account on the first run
Date Tue, 05 Feb 2008 15:54:07 GMT

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

Nicolas Lalevée updated IVYDE-70:
---------------------------------

    Attachment: IVYDE-70-preferenceListenerTry.patch

I have got no response from the mailing list, so I started implementing the preference-listener
solution (see the attached patch). But then I run into too big issues.
First we have to mark an IvyDE default configuration as being default rather than not storing
a configuration. But the process of creating the classpath container is embedded into the
JDT process, IvyDE only implement IvydeContainerPage. So there is no obvious way to control
the preferences.
And then in my tests, the build is triggered twice. After the refresh, the resolve job is
triggered, but also the build one. The build job doesn't wait for the resolve job to be finished,
so it is triggered a second time after the resolve job actually updates the classpath.

Then rethinking about how the JDT works, it finally seems that having preferences to control
a class path container is wrong. And in fact IvyDE has two configuration panes: the one which
control the conf to resolve, and the one which control the ivysettings url, the jar, source,
javadocs types, etc...
Then I browsed the JDT classes and I have found the IClasspathAttribute, which should be used
to store extra configuration about the class path entry. So it seems that this Jira issue
will be resolved properly if we merge the two confiuration panes, and if we make the current
preferences stored as classpath extra attributes (which will finally get stored into the .classpath).

So unless there are objections about merging the two confiuration panes, I will do a patch
for this last solution.


> The project ivy configuration is not taken into account on the first run
> ------------------------------------------------------------------------
>
>                 Key: IVYDE-70
>                 URL: https://issues.apache.org/jira/browse/IVYDE-70
>             Project: IvyDE
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>         Environment: Eclipse 3.2
>            Reporter: Nicolas Lalevée
>         Attachments: IVYDE-70-preferenceListenerTry.patch
>
>
> Starting with an empty workspace, I import a project which already have its Ivy preferences
configured.
> After the import the classpath is made of some ibiblio jars, whereas I was expecting
the ones from my internal repository. After a resolve, the classpath has the proper jars,
from my internal repository.

-- 
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