maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <>
Subject [jira] Created: (MNG-2584) Rebuild on pom change
Date Mon, 02 Oct 2006 14:26:27 GMT
Rebuild on pom change

                 Key: MNG-2584
             Project: Maven 2
          Issue Type: Improvement
            Reporter: Kenney Westerhof

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.


This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message