[
https://issues.apache.org/jira/browse/MDEPLOY-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795185#comment-16795185
]
Ivica Mikic commented on MDEPLOY-252:
-------------------------------------
Here is my usual sequence of Maven build commands. First I run "mvn clean
package" many times as I work on my code. Once my code is complete, I run "mvn
install" then "mvn deploy", however, I noticed that Maven creates a new JAR,
WAR or EAR files even though I don't have code changes and I don't specify
"clean". I expect that Maven would just use previously created archived files
(JAR, WAR, EAR) and "install" them to our local repository or "deploy" them to
our global repository.
In a nutshell, I don't want to have different timestamps of the JAR, WAR, EAR
files that I deployed on Java application servers after "mvn clean package" and
those saved in Maven repositories after "mvn install" or "mvn deploy".
> Deploy current archive without creating new archive (jar, war, ear)
> -------------------------------------------------------------------
>
> Key: MDEPLOY-252
> URL: https://issues.apache.org/jira/browse/MDEPLOY-252
> Project: Maven Deploy Plugin
> Issue Type: New Feature
> Components: deploy:deploy
> Affects Versions: 2.8.2
> Reporter: Ivica Mikic
> Priority: Major
> Labels: features, maven
> Fix For: waiting-for-feedback
>
>
> It would be great to be able to deploy current archive file (jar, war, ear)
> without creating a new one, to preserve timestamp from previous package or
> install run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
