[
https://issues.apache.org/jira/browse/METRON-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971517#comment-15971517
]
Michael Miklavcic edited comment on METRON-856 at 4/17/17 7:19 PM:
-------------------------------------------------------------------
This is due to how maven handles dependencies. By splitting these steps up and
only doing a package rather than an install, you don't get the artifacts in the
repo. So the 2nd run will look for a dependency in the build tree first - which
isn't there - and then in the internal repo, which also isn't there. More
insidiously, if you had run a "mvn clean install" at some point, you would get
old outdated artifacts bundled up with the rpms, which would be really
confusing. Can we simply change this to mvn clean install?
was (Author: msmiklavcic):
This is due to how maven handles dependencies. By splitting these steps up and
only doing a package rather than an install, you don't get the artifacts in the
reactor. So the 2nd run will look for a dependency in the build tree first -
which isn't there - and then in the internal repo, which also isn't there. More
insidiously, if you had run a "mvn clean install" at some point, you would get
old outdated artifacts bundled up with the rpms, which would be really
confusing. Can we simply change this to mvn clean install?
> Ansible rpm build wipes out prior binary build
> ----------------------------------------------
>
> Key: METRON-856
> URL: https://issues.apache.org/jira/browse/METRON-856
> Project: Metron
> Issue Type: Bug
> Reporter: David M. Lyle
> Priority: Blocker
> Labels: newbie
> Fix For: 0.4
>
>
> The Ansible build currently does a second clean which undoes the build that
> was performed with the HDP-2.5.0.0 profile. The 2nd build task in the
> metron-builder role should look more like:
> bq.{{local_action: shell cd {{ metron_build_dir }}/metron-deployment && mvn
> clean package -DskipTests -P build-rpms}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
