Skip to content

Instantly share code, notes, and snippets.

Phillip Green II phillipgreenii

Block or report user

Report or block phillipgreenii

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
View keybase.md

Keybase proof

I hereby claim:

  • I am phillipgreenii on github.
  • I am phillipgreenii (https://keybase.io/phillipgreenii) on keybase.
  • I have a public key whose fingerprint is 8158 F7C2 2E7E B058 A05B 1AA2 FAEB 6674 D182 3AD4

To claim this, I am signing this object:

@phillipgreenii
phillipgreenii / README.md
Created Mar 19, 2016
Raspberry PI Wirless Configuration
View README.md
@phillipgreenii
phillipgreenii / README.md
Last active Apr 16, 2019
Running NPM Scripts through maven
View README.md

I am in the process of introducing single page applications to where I work. For development, using node based build tools is much easier for the single page applications. However, the build process for our organization is based upon maven. Our solution started with the maven plugin frontend-maven-plugin. It worked great at first, but then we ran into a situation that I couldn't make work with it.

As stated before, at our organization, we have the older ecosystem which is maven and the newer ecosystem which is node. Our goal was to keep the hacking to a minimum. We did this by putting all of the hacks into a single super node based build file. This is what maven calls and the reason frontend-maven-plugin wasn't sufficient. The super node based build script calls all of the other build scripts by spawning npm run. Try as I might, I could not figure out how to make the spawn work. front-end-maven-plugin downloads npm

You can’t perform that action at this time.