Uploaded image for project: 'IvyDE'
  1. IvyDE
  2. IVYDE-328

Do not save the project name in the classpath container configuration

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Invalid
    • 2.2.0.beta1
    • None
    • classpath container

    Description

      The classpath container in the .classpath file currently references the name of the project that the container belongs to. E.g.

      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
      

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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            carsten.pfeiffer Carsten Pfeiffer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment