You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2008/01/14 17:41:35 UTC
[jira] Created: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
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
Reporter: Nicolas Lalevée
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.
[jira] Updated: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée updated IVYDE-70:
---------------------------------
Environment: Eclipse 3.2
> 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
>
> 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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558664#action_12558664 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
After some IvyDE debugging, it appears that on the first run {{opt}} is {{null}} :
IvyPlugin line 376 :
{code}
String opt = IvyPlugin.getDefault().getProjectPreferences(project).get(
PreferenceConstants.IVYCONF_PATH, null);
{code}
On the resolve, {{opt}} has the URL I configured, the URL of the conf for my internal repository.
Not being an Eclipse expert, I cannot explain it yet.
> 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
> Reporter: Nicolas Lalevée
>
> 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.
[jira] Resolved: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée resolved IVYDE-70.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
I run Eclipse with the patch for sevral week, no special worries (execpt some Eclipse-3.3 issues which have their opened Jira entries).
So I committed the patch.
> 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
> Assignee: Nicolas Lalevée
> Fix For: 1.3.0
>
> Attachments: IVYDE-70-preferenceListenerTry.patch, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish-r629775.patch, IVYDE-70-urlish-r633421.patch, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567097#action_12567097 ]
Xavier Hanin commented on IVYDE-70:
-----------------------------------
Excellent! Sounds really great, and so much cleaner!
About the UI, I agree it will be much more user friendly, so I'm a big +1 for the change you suggest!
> 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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560951#action_12560951 ]
Xavier Hanin commented on IVYDE-70:
-----------------------------------
That sounds like good solutions to me, and yes it's better to never show an empty classpath container.
> 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
>
> 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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570290#action_12570290 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
Phew, finnaly I get it working with the IPath of the container, so the .classpath will be like :
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path=""/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="con" path="org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/ivy.xml/*/file%3A%2Fhome%2Fnicolasl%2Fdev%2Fivy%2Fivysettings.xml/jar/source,src/javadoc/-source,-sources,-src/-javadoc,-javadocs,-doc,-docs/false/lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5D/alpha"/>
<classpathentry kind="output" path=""/>
</classpath>
{noformat}
Cleaning up the code I wrote, I will provide a patch soon.
> 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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570339#action_12570339 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
About the container path. For Eclipse, it is a IPath. So as far as I understand, it is a path as in a URL. So it could be possible to implement what you suggest.
In fact here is the scheme I implemented :
org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/ivy.xml/conf/ivysetting.xml/acceptedTypes/sourceTypes/javadocTypes/sourceSuffixes/javadocSuffixes/doRetrieve/retreivePattern/order
knowing that the ivy.xml, ivysettings.xml and the retrieve pattern are URL encoded. Hum.. and in fact I just realized that it should be the case for every configuration entry, the user can broke its config in putting a / in its "javadocTypes" for instance. So it won't be that different from what you suggested. It will be quite easy to write the serializer, but the parser might be more complicated. I need to check the query string spec.
> 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, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560688#action_12560688 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
I have some colleagues which playing with Eclipse is their job. I have ask them, they never faced that issue, but they had some ideas: for instance we can try to use the scheduling rules so that the open operation and the refresh job will block the resolve job. It am still unsuccessful, but I have not gone deeply into that solution yet.
If that solution doesn't work, I thought of storing data even if the user didn't defined preferences. The data stored would simply be a no-configuration tag. So we should always try to load the preferences. And if the preferences are not there, then we wait for them to be loaded in being a preference listener.
I prefer this solution because there will be less input request from the user. And as the job is now asynchronously launched, the eclipse won't freeze.
But if that last solution doesn't work either, then your solution is the best yes.
> 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
>
> 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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574929#action_12574929 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
I think that containers disappearing on 3.2 was IvyDE breaking eclipse. What I seen there seems a lot more repeatable, like a kind of "feature", and I found some interesting pointers: IVYDE-82.
> 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, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish-r629775.patch, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Issue Comment Edited: (IVYDE-70) The project ivy
configuration is not taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570774#action_12570774 ]
hibou edited comment on IVYDE-70 at 2/20/08 9:47 AM:
---------------------------------------------------------------
So here is a path with some URLish container path.
I also made the plugin read properly IvyDE-1.3 configurations; well at least the ivy.xml and the confs as the other part of the configuration is contain is the preference which cannot be loaded due to the bug this patch is trying to fix.
By the way, the result in the .classpath is not exactly what we expected, there are some {{&}} :
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" output="src/main/webapp/WEB-INF/classes" path="src/main/java"/>
<classpathentry kind="src" output="src/main/webapp/WEB-INF/classes" path="src/main/resources"/>
<classpathentry kind="src" output="bin" path="src/test/java"/>
<classpathentry kind="src" output="bin" path="src/test/resources"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="con" path="org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?ivyXmlPath=ivy.xml&confs=*&ivySettingsPath=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fjoost%2Fsvn%2Fcode%2Fbistro%2Ftools%2F1.0%2Fivyconf-eclipse.xml&acceptedTypes=jar&sourceTypes=source%2Csrc&javadocTypes=javadoc&sourceSuffixes=-source%2C-sources%2C-src&javadocSuffixes=-javadoc%2C-javadocs%2C-doc%2C-docs&doRetrieve=false&retreivePattern=lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5D&alphaOrder=true"/>
<classpathentry kind="output" path="src/main/webapp/WEB-INF/classes"/>
</classpath>
{code}
was (Author: hibou):
So here is a path with some URLish container path.
I also made the plugin read properly IvyDE-1.3 configurations; well at least the ivy.xml and the confs as the other part of the configuration is contain is the preference which cannot be loaded due to the bug this patch is trying to fix.
By the way, the result in the .classpath is not exactly what we expected, there are some {{&}} :
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" output="src/main/webapp/WEB-INF/classes" path="src/main/java"/>
<classpathentry kind="src" output="src/main/webapp/WEB-INF/classes" path="src/main/resources"/>
<classpathentry kind="src" output="bin" path="src/test/java"/>
<classpathentry kind="src" output="bin" path="src/test/resources"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="con" path="org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?ivyXmlPath=ivy.xml&confs=*&ivySettingsPath=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fjoost%2Fsvn%2Fcode%2Fbistro%2Ftools%2F1.0%2Fivyconf-eclipse.xml&acceptedTypes=jar&sourceTypes=source%2Csrc&javadocTypes=javadoc&sourceSuffixes=-source%2C-sources%2C-src&javadocSuffixes=-javadoc%2C-javadocs%2C-doc%2C-docs&doRetrieve=false&retreivePattern=lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5D&alphaOrder=true"/>
<classpathentry kind="output" path="src/main/webapp/WEB-INF/classes"/>
</classpath>
{code:xml}
> 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, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Updated: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ 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-urlish-r629775.patch
héhé :)
So here is a patch with corrected spell mistake. One will still exist, the one in the global preference properties file, but I think it is better to keep compatibility than correcting an internal spell mistake.
I also fixed the link in the ivy container configuration page to the global Ivy configuration one.
> 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, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish-r629775.patch, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570350#action_12570350 ]
Xavier Hanin commented on IVYDE-70:
-----------------------------------
parsing should be very simple if all values are URLEncoded, you can be sure you won't ever have a & for something else than a parameter separator. So you can simply use a split or a StringTokenizer with & as delimiter (starting after the ?). Then for each part you split with the equal separator, and URL decode the value...
> 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, IVYDE-70.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.
[jira] Updated: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ 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-urlish-r629733.patch
Updated path which fix some introduced bugs:
* if there were no the project specific conf, the global one was not taken into account
* in the container page, if there is no the project specific conf, the grayed values are now the global configuration ones
* add some panaoïd check at the .classpath loading. Raising some Exception during to load of the .classpath is making Eclipse completely lost.
* container resolve job was not triggered on global configuration change
* add a configuration entry for the alphabetical order in the global Ivy config
> 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, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570318#action_12570318 ]
Xavier Hanin commented on IVYDE-70:
-----------------------------------
That sound nice, I guess you'll be able to commit it yourself :-)
About the information encoding, I know we shouldn't actually read the .classpath, but I think it's not easy to understand the encoding you choose. Maybe we could use something more standard, like the URI query part with parameters encoded with application/x-www-form-urlencoded MIME format, for which we already have the URLEncoder and URLDecoder in the JRE (which seems to be what you already use. Then the path would look pretty much like an URI, except for the beginning (no protocol, ...). Something like:
{noformat}
org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER?md=ivy.xml&conf=*&settings=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fivy%2Fivysettings.xml&...
{noformat}
Unless this is not something possible with eclipse classpath parsing?
> 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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569836#action_12569836 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
Bad news.
Whereas the configuration of an existing class path container works well with classpath attributes, the creation doesn't. The JDT doesn't care about the classpath attributes given from the "ContainerPage".
Again I asked help (now at the right place) http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.tools.jdt/msg22184.html
But I got no good answer yet.
So finally I think that the configuration should be in the container path. I will try that.
> 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.
[jira] Updated: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ 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-urlish-r633421.patch
New patch that fix a bug introduced in the path: the ivy instance was attached to the container and was not changing even if the ivySetting path change. So reconfiguring the container to be project-specific or not-project-specific was not working properly.
> 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, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish-r629775.patch, IVYDE-70-urlish-r633421.patch, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574546#action_12574546 ]
Xavier Hanin commented on IVYDE-70:
-----------------------------------
I've already seen disappearing classpath container too, I think there's an open issue about it. I'm not sure it's related though, since it happened on 3.2. But I agree a separate issue will be better to isolate the problem.
> 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, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish-r629775.patch, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560003#action_12560003 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
After further investigation, it seems that the preferences are loaded when the refresh thread runs. But the ivy container load before it.
The plugin may be a preference listener so it would be triggered when the preferences change, but the first resolve have to be avoided, because no configuration means retreiving artifacts from ibiblio, which takes time and space and which probably will raise errors for probably nothing.
So we have to find a way to load it after the refresh.
> 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
>
> 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.
[jira] Issue Comment Edited: (IVYDE-70) The project ivy
configuration is not taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570774#action_12570774 ]
hibou edited comment on IVYDE-70 at 2/20/08 9:49 AM:
---------------------------------------------------------------
So here is a path with some URLish container path.
I also made the plugin read properly IvyDE-1.3 configurations; well at least the ivy.xml and the confs as the other part of the configuration is contain is the preference which cannot be loaded due to the bug this patch is trying to fix.
By the way, the result in the .classpath is not exactly what we expected, there are some & ; :
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" output="src/main/webapp/WEB-INF/classes" path="src/main/java"/>
<classpathentry kind="src" output="src/main/webapp/WEB-INF/classes" path="src/main/resources"/>
<classpathentry kind="src" output="bin" path="src/test/java"/>
<classpathentry kind="src" output="bin" path="src/test/resources"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="con" path="org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?ivyXmlPath=ivy.xml&confs=*&ivySettingsPath=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fjoost%2Fsvn%2Fcode%2Fbistro%2Ftools%2F1.0%2Fivyconf-eclipse.xml&acceptedTypes=jar&sourceTypes=source%2Csrc&javadocTypes=javadoc&sourceSuffixes=-source%2C-sources%2C-src&javadocSuffixes=-javadoc%2C-javadocs%2C-doc%2C-docs&doRetrieve=false&retreivePattern=lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5D&alphaOrder=true"/>
<classpathentry kind="output" path="src/main/webapp/WEB-INF/classes"/>
</classpath>
{code}
was (Author: hibou):
So here is a path with some URLish container path.
I also made the plugin read properly IvyDE-1.3 configurations; well at least the ivy.xml and the confs as the other part of the configuration is contain is the preference which cannot be loaded due to the bug this patch is trying to fix.
By the way, the result in the .classpath is not exactly what we expected, there are some {{&}} :
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" output="src/main/webapp/WEB-INF/classes" path="src/main/java"/>
<classpathentry kind="src" output="src/main/webapp/WEB-INF/classes" path="src/main/resources"/>
<classpathentry kind="src" output="bin" path="src/test/java"/>
<classpathentry kind="src" output="bin" path="src/test/resources"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="con" path="org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?ivyXmlPath=ivy.xml&confs=*&ivySettingsPath=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fjoost%2Fsvn%2Fcode%2Fbistro%2Ftools%2F1.0%2Fivyconf-eclipse.xml&acceptedTypes=jar&sourceTypes=source%2Csrc&javadocTypes=javadoc&sourceSuffixes=-source%2C-sources%2C-src&javadocSuffixes=-javadoc%2C-javadocs%2C-doc%2C-docs&doRetrieve=false&retreivePattern=lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5D&alphaOrder=true"/>
<classpathentry kind="output" path="src/main/webapp/WEB-INF/classes"/>
</classpath>
{code}
> 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, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560447#action_12560447 ]
Xavier Hanin commented on IVYDE-70:
-----------------------------------
Thanks for your investigation Nicolas, you've found the exact problem, but it seems it won't be easy to solve in IvyDE. According to the bug in eclipse marked as won't fix, we can't have the information when the project is opened that some project preferences are available. This comes only later... if some project preferences are available, but we can't be sure. So what can we do? Delay dependency resolution? Make the resolution on demand only? this will affect all startups, not only when you import... so we have to be careful with what we do. But maybe making the resolution on demand only is the best solution. Indeed, this can take a lot of time, and sometimes people complain when starting eclipse with IvyDE installed that it takes a very long time, or even hang. So on startup or project import we could fetch the classpath container only if a dependency resolution report is available in cache, and keep it empty if we have no inormation. Then users would have to launch a resolve manually in such case. Since this can be a long operation, I don't think it's that silly to do things like this.
WDYT?
> 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
>
> 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.
[jira] Updated: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ 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.patch
Here is a patch.
So:
* the two configuration panes merged
* the configuration pane has a global "project specific settings" check box
* now we can only finish the configuration panes if it is correctly configured (some disabled finish button)
A little about the implementation:
* the container configuration is defined in the container path. The paths (ivysettings, ivy.xml paths) are URL encoded
* the configuration that was managed in the IvyPlugin is now handled in two new beans: the global configuration and the container one. The code is now simpler.
I have tested with some tiny projects, it works fine. But due to the big change, the patch should be also tested with bigger project, and also with project having default ivysettings.
> 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, IVYDE-70.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.
[jira] Assigned: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée reassigned IVYDE-70:
------------------------------------
Assignee: Nicolas Lalevée
> 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
> Assignee: Nicolas Lalevée
> Attachments: IVYDE-70-preferenceListenerTry.patch, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish-r629775.patch, IVYDE-70-urlish-r633421.patch, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565783#action_12565783 ]
Xavier Hanin commented on IVYDE-70:
-----------------------------------
It makes sense to follow eclipse convention, and it seems that would be the cleanest way to resolve this issue. So I'm +1 to merge the configuration panes and put everything in the classpath as long as it's related to the classpath container.
> 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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562078#action_12562078 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
Still not sucessfull with the former solution. I asked help there :
http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.platform/msg71811.html
If I have no response I will go forward the second 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
>
> 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.
[jira] Updated: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ 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-urlish.patch
So here is a path with some URLish container path.
I also made the plugin read properly IvyDE-1.3 configurations; well at least the ivy.xml and the confs as the other part of the configuration is contain is the preference which cannot be loaded due to the bug this patch is trying to fix.
By the way, the result in the .classpath is not exactly what we expected, there are some {{&}} :
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" output="src/main/webapp/WEB-INF/classes" path="src/main/java"/>
<classpathentry kind="src" output="src/main/webapp/WEB-INF/classes" path="src/main/resources"/>
<classpathentry kind="src" output="bin" path="src/test/java"/>
<classpathentry kind="src" output="bin" path="src/test/resources"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="con" path="org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?ivyXmlPath=ivy.xml&confs=*&ivySettingsPath=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fjoost%2Fsvn%2Fcode%2Fbistro%2Ftools%2F1.0%2Fivyconf-eclipse.xml&acceptedTypes=jar&sourceTypes=source%2Csrc&javadocTypes=javadoc&sourceSuffixes=-source%2C-sources%2C-src&javadocSuffixes=-javadoc%2C-javadocs%2C-doc%2C-docs&doRetrieve=false&retreivePattern=lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5D&alphaOrder=true"/>
<classpathentry kind="output" path="src/main/webapp/WEB-INF/classes"/>
</classpath>
{code:xml}
> 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, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574535#action_12574535 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
I worked on Eclipse 3.2 while creating the patch. I did not see any major issues yet.
I tested on Eclipse 3.3 : one annoying bug : if the resolved classpath is empty, the classpath container disapear... I think it will deserve a seperate issue as soon as this one is committed.
I have colleague which works with Eclipse 3.4M4 : same as 3.3.
> 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, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish-r629775.patch, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571008#action_12571008 ]
Xavier Hanin commented on IVYDE-70:
-----------------------------------
Sounds like a very good progress! Good job!
About the classpath format, there's a small typo: retreivePattern instead of retrievePattern. I know some IvyDE code also suffers from the same typo, but I've checked an english dictionary and it seems we should better use retrieve everywhere. Unless we prefer "récupérer" :-)
> 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, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish.patch, IVYDE-70.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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560410#action_12560410 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
In fact we have to deal with it :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=139911
> 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
>
> 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.
[jira] Commented: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567091#action_12567091 ]
Nicolas Lalevée commented on IVYDE-70:
--------------------------------------
It works !!! :)
Effectively this is the solution, we will have something like extra entries in the .classpath :
{code:xml}
<classpathentry kind="con" path="org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/ivy.xml/*">
<attributes>
<attribute name="ivySettingsPath" value="file:/home/nicolasl/dev/......../tools/1.0/ivyconf-eclipse.xml"/>
</attributes>
</classpathentry>
{code}
The patch is not ready, as I have some trouble while trying to change the Ivy's configuration the project being opened. But I will make it work!
I have another request about the UI. The pages being merged, there will be in fact two tabs, the main one (ivy.xml + confs) and the advanced one (ivyseetings.xml + extensions). In the advanced one I would like to present it as the other Eclipse classic configurations, with a global "Enable project specific settings" and a link to the global conf (See the "Java code style" configuration page), more than having a per-config entry inheritance. We would loose a little bit of the fine-graininess of the configuration, but I think this will be a lot better user friendly.
WDYT ?
> 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.