Uploaded image for project: 'Java Mission Control'
  1. Java Mission Control
  2. JMC-6517

Make maven the single source of truth when importing JMC into Eclipse

    Details

    • Type: Bug
    • Status: New
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 7.1.0
    • Fix Version/s: None
    • Component/s: Infrastructure
    • Labels:
      None

      Description

      When importing the JMC projects into Eclipse, maven generates a few properties files such as .classpath, .project or .settings/org.eclipse.jdt.core.prefs.

      Interesting to notice is that a different set of files is generated or modified depending on whether the projects are imported on Windows or MacOS. Maybe there's also differences by Eclipse versions.

      A few of these properties files are already checked in.

      It shall be investigated whether the Maven configuration (e.g. pom.xml files) can be improved to correctly define the Eclipse projects and the project layout is reproducible when importing into Eclipse, no matter what platform and Eclipse version is used.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              clanger Christoph Langer
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: