search

eirslett / frontend-maven-plugin

"Maven-node-grunt-gulp-npm-node-plugin to end all maven-node-grunt-gulp-npm-plugins." A Maven plugin that downloads/installs Node and NPM locally, runs NPM install, Grunt, Gulp and/or Karma.
Apache License 2.0
4.2k stars 867 forks source link

The `build` path is located differently, under the `react` or under the `target` #1071

Closed AlexandrSokolov closed 1 year ago

AlexandrSokolov commented 1 year ago

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

I've desribed it pretty detailed in stackoverflow.com

Hope it is ok. If not, will describe it here additionally.

If the current behavior is a bug, please provide the steps to reproduce.

Configure the plugin as described in the issue, run the build process via maven.

What is the expected behavior?

The build folder is ALWAYS located under the ${workingDirectory}, but not under the target

Please mention your frontend-maven-plugin and operating system version.

frontend-maven-plugin - version 1.6

$ uname -a Linux alex-HP-ProBook-450-G7 5.15.0-56-generic #62~20.04.1-Ubuntu SMP Tue Nov 22 21:24:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux react_build.txt target_build.txt

The log files are not full, if needed, can attach both.

AlexandrSokolov commented 1 year ago

I've compared 2 projects. It turned out the react application itself somehow affect the frontend-maven-plugin I am attaching it without src files, but with exact configurations to reproduce it locally. react.app.zip

I assume it must never happen.

AlexandrSokolov commented 1 year ago

It does not relate to the plugin at all. Explit configuration used '../target/build' folder, as a result even with npm run build it was located in the target. Not a bug.