jira-importer commented on issue #540: URL: https://github.com/apache/maven-deploy-plugin/issues/540#issuecomment-2771550213
**[Ivica Mikic](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mindjoy)** commented From the Maven perspective, we normally build our Java code first with "mvn clean package" many times during the active code change/development. This is done either manually on the command line or within the IDE. But once testing has passed and the code is considered reasonably stable, we want to proceed with the "mvn install", then "mvn deploy", but keep the original archive files in sync since there are no code changes. Isn't that reasonable? What would be the alternative? I would still like to accomplish this somehow within the Maven life cycle, if possible. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
