[
https://issues.apache.org/jira/browse/MDEPLOY-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795203#comment-16795203
]
Karl Heinz Marbaise commented on MDEPLOY-252:
---------------------------------------------
The first thing is to deploy servers only from a CI solution like Jenkins which
means deploy the created artifacts into your repository manager and deploy your
servers from there. Apart from that if you do {{mvn install}} and then {{mvn
deploy}} you run several parts duplicate..cause the life cycle contains
{{install}} . which means you only need to do {{mvn clean deploy}}. Furthermore
if code has been changed can be identified by using your version control
system...
The last sentence I don't understand. If you do {{mvn clean deploy}} all your
artifacts have the same version etc. ?
> 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)
