[
https://issues.apache.org/jira/browse/IVYDE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494859#comment-13494859
]
Nicolas Lalevée commented on IVYDE-328:
---------------------------------------
This doesn't work better.
To test it there are two projects 'jetty' and 'jetty-webapp' to checkout from
there: http://svn.apache.org/repos/asf/ant/ivy/ivyde/trunk/test/
You will find there a launch configuration called HelloWorldServlet. The
classpath of this configuration is the default classpath of the project jetty.
But the source lookup if the default one + the project jetty-webapp. The JDT
show then in the source tab the two projects and the IvyDE classpath container
of jetty-webapp.
I have just retested, if the project name is not in the container path, then
trying to expand the container make the resolve fail due to a missing ivy.xml
(because not resolved relatively to the project but to the current working
directory of the jvm).
> Do not save the project name in the classpath container configuration
> ---------------------------------------------------------------------
>
> Key: IVYDE-328
> URL: https://issues.apache.org/jira/browse/IVYDE-328
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
> Affects Versions: 2.2.0.beta1
> Reporter: Carsten Pfeiffer
> Priority: Minor
> Labels: patch
> Attachments: dontSaveProjectName.patch
>
>
> The classpath container in the {{.classpath}} file currently references the
> name of the project that the container belongs to. E.g.
> {code}
> org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?project=someProject&ivyXmlPath=ivy.xml&confs=*&acceptedTypes=jar%2Cbundle%2Cejb%2Cmaven-plugin&alphaOrder=false&resolveInWorkspace=false&readOSGiMetadata=false&retrievedClasspath=true&retrievedClasspathPattern=lib%2F%5Bartifact%5D-%5Brevision%5D.%5Bext%5D&retrievedClasspathSync=false&retrievedClasspathTypes=jar
> {code}
> (see the reference to "someProject").
> This is unnecessary, because the classpath container is always attached to
> the project it is defined for, the there is no need to explicitly remember
> the project.
> Furthermore, it causes problems when a project is renamed, because the
> classpath container will not be updated and then reference the wrong (old)
> project.
> And last, not saving the project eases copy&pasting of the classpath
> container entry from one .classpath file to another (no need to click in all
> those dialogs then).
> I'll attach a patch that removes the saving of the project. The loading is
> kept at it is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
