You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "dongeforever (JIRA)" <ji...@apache.org> on 2017/05/25 08:56:04 UTC
[jira] [Closed] (ROCKETMQ-168) Duplicated calls of life cycle in
Maven.
[ https://issues.apache.org/jira/browse/ROCKETMQ-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dongeforever closed ROCKETMQ-168.
---------------------------------
Resolution: Fixed
This issue has been resolved in `develop` branch, the quick start[1] guide should be adjusted when develop branch merged to master.
[1]. http://rocketmq.apache.org/docs/quick-start/
> Duplicated calls of life cycle in Maven.
> ----------------------------------------
>
> Key: ROCKETMQ-168
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-168
> Project: Apache RocketMQ
> Issue Type: Improvement
> Affects Versions: 4.0.0-incubating
> Reporter: Karl Heinz Marbaise
> Assignee: yukon
> Priority: Minor
> Fix For: 4.1.0-incubating
>
>
> Current the [build documentation|http://rocketmq.incubator.apache.org/docs/quick-start/] states to build via:
> {code}
> mvn clean package install -Prelease-all assembly:assembly -U
> {code}
> Only the following is neccessary:
> {code}
> mvn clean install -Prelease-all assembly:assembly -U
> {code}
> otherwise several parts of the build life cycle are repeated...furthermore the questions is why you use a call to {{assembly:assembly}} which is deprecated and best it should be done simply by using:
> {code}
> mvn clean deploy -Prelease-all
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)