Isis
  1. Isis
  2. ISIS-227

Separate out Eclipse (m2e) target classes from Maven cli,so co-exist better.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: core-1.0.0
    • Component/s: Core
    • Labels:
      None

      Description

      Use the m2e.version property to activate a profile such that Eclipse/M2E builds into "target-ide/..." while the Maven command line continues to build into the regular "target/..."

        Activity

        Hide
        Dan Haywood added a comment -

        On 3 February 2013 10:38, Minto van der Sluis <minto@xup.nl> wrote (on the dev mailing list):
        Hi Dan,

        Can you explain why ISIS-227 was needed? I understand what it does, but
        not why it was needed.

        ~~~~
        Dan's reply:

        It's a fix for the way that I work, and perhaps others do too.

        I usually work in Eclipse and rely on m2e to configure the classpaths of the projects, but Eclipse's incremental compiler doing the actual compilation. However, every now and then I like to go over to the cmd line and do a build from there; Eclipse doesn't distinguish between the regular classpath (src/main/java) and the test classpath (src/test/java) and so a misconfiguration in a pom.xml may build in Eclipse but not in Maven.

        Anyway... by default both Maven and m2e configure the target directory as the destination for class files. Doing a build from the cmd line confuses Eclipse, requiring (for me at least) a refresh all projects followed by a clean followed by a build all.

        With ISIS-227, Eclipse compiles into target-ide whereas Maven compiles into target. Thus the two build environments don't confuse each other.

        Show
        Dan Haywood added a comment - On 3 February 2013 10:38, Minto van der Sluis <minto@xup.nl> wrote (on the dev mailing list): Hi Dan, Can you explain why ISIS-227 was needed? I understand what it does, but not why it was needed. ~~~~ Dan's reply: It's a fix for the way that I work, and perhaps others do too. I usually work in Eclipse and rely on m2e to configure the classpaths of the projects, but Eclipse's incremental compiler doing the actual compilation. However, every now and then I like to go over to the cmd line and do a build from there; Eclipse doesn't distinguish between the regular classpath (src/main/java) and the test classpath (src/test/java) and so a misconfiguration in a pom.xml may build in Eclipse but not in Maven. Anyway... by default both Maven and m2e configure the target directory as the destination for class files. Doing a build from the cmd line confuses Eclipse, requiring (for me at least) a refresh all projects followed by a clean followed by a build all. With ISIS-227 , Eclipse compiles into target-ide whereas Maven compiles into target. Thus the two build environments don't confuse each other.

          People

          • Assignee:
            Dan Haywood
            Reporter:
            Dan Haywood
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 2h
              2h
              Remaining:
              Remaining Estimate - 2h
              2h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development