[
https://issues.apache.org/jira/browse/MDEPLOY-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803264#comment-16803264
]
Ivica Mikic commented on MDEPLOY-252:
-------------------------------------
>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.
> 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)
