You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Dale Richardson (Jira)" <ji...@apache.org> on 2019/08/27 01:24:00 UTC
[jira] [Updated] (METRON-2237) Metron RPM Build - Move npm installs
outside of RPM construction
[ https://issues.apache.org/jira/browse/METRON-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dale Richardson updated METRON-2237:
------------------------------------
Description:
An extract from: metron-deployment/packaging/docker/rpm-docker/SPECS/metron.spec
{{allows node dependencies to be packaged in the RPMs}}
{{ npm install --prefix="%\{buildroot}%{metron_home}/web/expressjs" --only=production}}
It probably makes sense to keep this sort of packaging detail external to the RPM build and as a responsibility of the respective Maven modules.
In certain circumstances the npm repos get left lying around as persistent state in the build tree. This cannot be tidied up be a mvn clean and causes subsequent build failures. (c.f. METRON-2234)
was:
metron-deployment/packaging/docker/rpm-docker/SPECS/metron.spec
# allows node dependencies to be packaged in the RPMs
npm install --prefix="%\\{buildroot}%\\{metron_home}/web/expressjs" --only=production
It probably makes sense to keep this sort of packaging detail external to the RPM build and as a responsibility of the respective Maven modules.
In certain circumstances the npm repos get left lying around as persistent state in the build tree. This cannot be tidied up be a mvn clean and causes subsequent build failures. (c.f. METRON-2234)
> Metron RPM Build - Move npm installs outside of RPM construction
> ----------------------------------------------------------------
>
> Key: METRON-2237
> URL: https://issues.apache.org/jira/browse/METRON-2237
> Project: Metron
> Issue Type: Bug
> Reporter: Dale Richardson
> Priority: Minor
>
> An extract from: metron-deployment/packaging/docker/rpm-docker/SPECS/metron.spec
> {{allows node dependencies to be packaged in the RPMs}}
> {{ npm install --prefix="%\{buildroot}%{metron_home}/web/expressjs" --only=production}}
> It probably makes sense to keep this sort of packaging detail external to the RPM build and as a responsibility of the respective Maven modules.
> In certain circumstances the npm repos get left lying around as persistent state in the build tree. This cannot be tidied up be a mvn clean and causes subsequent build failures. (c.f. METRON-2234)
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)