[
https://issues.apache.org/jira/browse/IVYDE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500159#comment-13500159
]
Carsten Pfeiffer commented on IVYDE-328:
----------------------------------------
Thanks for the explanation, I see the problem now. For future reference, here's
the stacktrace where this happens (only when the ivy container does *not* have
the project in the path):
{code}
JavaRuntime.newRuntimeContainerClasspathEntry(IPath, int, IJavaProject) line:
689
JavaRuntime.newRuntimeContainerClasspathEntry(IPath, int) line: 671
ClasspathContainerSourceContainer.createSourceContainers() line: 83
ClasspathContainerSourceContainer(CompositeSourceContainer).getSourceContainers()
line: 129
SourceContainerViewer$ContentProvider.getChildren(Object) line: 77
{code}
> 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
