[jira] (MINSTALL-77) Checksum / timestamp check to allow install to assume previous successful completion

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MINSTALL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MINSTALL-77.
----------------------------------

    Resolution: Duplicate
      Assignee: Robert Scholte

I consider this as a duplicate of MINSTALL-39, which means that the artifact is considered unchanged, it won't be installed. The rules to decide if the artifact is the same can be found at [MNG-4368|https://jira.codehaus.org/browse/MNG-4368?focusedCommentId=204235&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-204235]
                
> Checksum / timestamp check to allow install to assume previous successful completion
> ------------------------------------------------------------------------------------
>
>                 Key: MINSTALL-77
>                 URL: https://jira.codehaus.org/browse/MINSTALL-77
>             Project: Maven 2.x Install Plugin
>          Issue Type: Improvement
>          Components: install:install
>         Environment: Windows
>            Reporter: Brien Wheeler
>            Assignee: Robert Scholte
>
> We have a large structured project with lots of components and artifacts (takes about 10 minutes to run mvn install from top of project).  When doing refactoring and rebuilding from clean working pool, we will occasionally get through 7 or 8 minutes of building and have something at the end of the dependency tree fail.
> After fixing the affected artifact, we have two options -- try to suss out what was not yet built and manually do those in appropriate order, or re-run mvn install from the project root.
> Obviously manually trying to complete the mvn install is error prone.
> Rerunning mvn install from the root takes a long time because even though it can skip compilation on all the previously built artifacts, it still re-runs the tests and re-packages and re-installs to the local repository.
> It would be great if mvn install checked the target directory, determined that its target existed in the working pool, checked that no dependencies (source files, resource files, test files, dependency artifacts) had newer timestamps and assumed that the target artifact was up to date.  Then it could skip all compilation, test, packaging steps.  It could check MD5 checksum against the local repository to determine whether the local file copy was needed (although it would be very odd that the test and packaging was all up to date but the actual file copy wasn't performed).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira