[
https://issues.apache.org/jira/browse/MDEPLOY-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800663#comment-16800663
]
Karl Heinz Marbaise commented on MDEPLOY-252:
---------------------------------------------
The problem here is implied by the life cycle. If you call first {{mvn clean
package}} and after that {{mvn deploy}} the life cycle starts from the
beginning which includes {{package}} and other parts as well. This is related
to incremental build which is currently not really working. So this means at
the moment the files will be recreated. The question is: Are you doing your
released locally ?
> 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)
