[
https://issues.apache.org/jira/browse/OPENMEETINGS-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17387243#comment-17387243
]
Maxim Solodovnik commented on OPENMEETINGS-2641:
------------------------------------------------
BTW here is the log of latest build at CI server:
https://ci-builds.apache.org/job/OpenMeetings/job/openmeetings/7/consoleFull
it contains same output:
{code}
[INFO] > [email protected] build-dev
/home/jenkins/workspace/OpenMeetings/openmeetings/openmeetings-web/src/main/front/main
[INFO] > browserify src/index.js --transform-key=staging -o
${outDir}${npm_package_name}.js
[INFO]
{code}
but everything works as expected :)
> Node environment value is not injected to NPM builds
> ----------------------------------------------------
>
> Key: OPENMEETINGS-2641
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2641
> Project: Openmeetings
> Issue Type: Bug
> Components: Builds, UI
> Affects Versions: 6.1.0
> Environment: Windows, maven-jetty-plugin, Java 14
> Reporter: Panimozhi Jothi
> Assignee: Maxim Solodovnik
> Priority: Blocker
> Labels: build, development, js, npm, outdir
> Attachments: js_gen_err.png, js_gen_err_mvn.png, mvn_config.png
>
>
> When I run the application using maven-jetty plugin, the npm compilations are
> NOT placing the generated JS under the target directory. The nodeenv
> environment value is not getting injected.
> Happens for both DEVELOPMENT and DEPLOYMENT maven builds.
> I believe the GIT source code should be running fine, am I missing something
> here.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
