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.23k stars 867 forks source link

Going crazy. #907

Open sesker opened 4 years ago

sesker commented 4 years ago

OK -- i am rewriting this issue. I need a matrix o products and VERSIONS that are required to make this plug in work. No combination of an NPM/NODE whatever versions work. None. I am running OSX 10.15.4 (latest I think). I Convinced my boss and others this plugin was the huge timesaver that was was its intent. I cannot make it work, I have installed, uninstalled, searched the web, whatever. It fails with npm install, or further the more I debug it. Please, please, put a matrix of products/projects that are required to use this plugin. It is ingenious for someone to have realized this is a problem -- with Microservices, this is a game changer, instead of writing all these scripts we normally do. I am frustrated because I spend a week trying to make this thing work. It fails on npm install or any other install. JFrog is giving me 404 issues -- is Jfrog really an answer to deploying. plugin vs the world and github/maven?

I wished/wanted to use this so badly as we have from projects that have front and backend development partitions.

Can you please write a simple matrix of the versions of dependencies that are required to make a specific version actually run? I know I am being a bit of an ass here, but I have been at open source software companies, and I't like I am so frustrated. You have to create docs, as mimimal as they may be. Tell me 1) what are the preqs for a particular version. I spent hours search the internet of answers, took a example project make that attempt to work, nada. I am really sorry, this was not mean to be a bassh. I just have to spend the weekend writing scripts when I thoughtI I font an answer to simplify.

I greatly appreciate you haveing the foresight to see how/what this could mean for developers.

sesker commented 4 years ago

Node: v14.4.0 (latest) NPM: 6.14.4 What is out of alignment? I uninstalled both of them, and it still didn't work.

jjlharrison commented 4 years ago

I expect your problem is with NPM, not this plugin. You’ll need to post at least a log file and maybe the plugin snippet from your POM if you want someone to help.

eirslett commented 4 years ago

What I suggest is that you git clone the frontend-maven-plugin itself, because it contains a number of integration tests that actually run the plugin and verify the results. If you get a green build, you know that the plugin itself works (and the problem could be somewhere else). If it breaks, then there could be a problem with the plugin, and it could be fixed by tweaking versions. Does that help?