jira-importer commented on issue #276: URL: https://github.com/apache/maven-install-plugin/issues/276#issuecomment-2771863448
**[Philip Pearson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=prgp)** commented There is a similar change required in `maven-deploy-plugin` - I have created a fork which includes both sets as changes (as separate commits) - https://github.com/prgp/maven-plugins/tree/prgp-MINSTALL-115 \\ \\ * `maven-install-plugin` changes are in [commit 3574e045a2af1146a98ed51af119a2a045204519](https://github.com/prgp/maven-plugins/commit/3574e045a2af1146a98ed51af119a2a045204519) * `maven-deploy-plugin` changes are in [commit e5b4c279de2e8e0de0dd7638144f4f93cfcac66e](https://github.com/prgp/maven-plugins/commit/e5b4c279de2e8e0de0dd7638144f4f93cfcac66e) These commits should cope with the edge care where any of the modules (except the last) are not using `installAtEnd` (/`deployAtEnd`) set to true or older versions. However, it currently does not handle last modules that are using an older `maven-install-plugin` (/`maven-deploy-plugin`) versions - I suppose the `isLastProject()` method could be altered so that it scans backwards through the reactor projects to find the first version that can support `installAtEnd` (/`deployAtEnd`) correctly and use that as the 'last' project ... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
