Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-2584

Rebuild on pom change

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      After a succesful build, all classes are compiled.
      Following builds won't recompile the classes since the sources
      haven't changed.

      When a user changes a dependency in the pom and then mvn installs, the sources
      aren't checked with the modified dependency.

      I propose we save a timestamp (or the pom itself) in target/ for each build,
      and let plugins that do some sort intelligent checking take this into account.

      There are a few options:

      • define a default location for the pom and let plugins implement timestamp or content checking
        as they please
      • define some api to ask if the project has changed
      • bind the clean plugin to some startup phase and let it auto-clean if the pom (or possibly parent poms/dependent poms)
        have changed.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              kenney Kenney Westerhof
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: