Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DCA11Y-1145] Node version manager support #4

Open
wants to merge 59 commits into
base: master
Choose a base branch
from

Conversation

flipatlas
Copy link
Collaborator

Changes:

  • add node version support for node and npm installers

Copy link
Collaborator

@atl-mk atl-mk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A lot of work, but looking pretty good so far

@atl-mk
Copy link
Collaborator

atl-mk commented Sep 17, 2024

I think I'd rather we get feature complete now so we can do one QA demo to rule them all.

I'm thinking in the QA demo we check;

  • version files not available and nothing specified in the POM (should give a good message instead of using the global version)

I can't think of anything else right now

@atl-mk
Copy link
Collaborator

atl-mk commented Sep 17, 2024

Perhaps a good development loop is to set yourself up some docker containers, one for each version manager? Maybe you already having something working for you

@atl-mk
Copy link
Collaborator

atl-mk commented Sep 17, 2024

One case I'm not sure about yet is no version file is specified and a version of Node is specified in the POM. I'm tempted to say we should do the vanilla behaviour and download it ourselves. We tell the users that the file is missing and they probably should create it.

This offers a simple way to drop-in this fork as a replacement in situations where they haven't previously created the files. That's because we'll have other features like incremental compilation which we want them to adopt.

flipatlas and others added 2 commits September 19, 2024 08:41
- fix fnm when multiple node versions installed
- use fnm dir to get installed node
- disable tests on windows
- fix paths in tests setup
@flipatlas
Copy link
Collaborator Author

I have skipped the new tests on windows, for now I'll assume we don't support windows. I'll revisit it later

@flipatlas
Copy link
Collaborator Author

QA Demo note: test on a project with split node installation in root and npm execution in modules

flipatlas and others added 30 commits October 11, 2024 11:57
* DCA11Y-1145: handle empty SHELL

* DCA11Y-1145: handle empty SHELL

* DCA11Y-1145: handle empty SHELL

* DCA11Y-1145: chore: prepare for releaes of 1.15.0-atlassian-1-bd74da96

* DCA11Y-1145: chore: clean up release

* DCA11Y-1145: fix: fall back on reading $SHELL from bin/sh
* DCA11Y-1145: fix: call fnm directly

* DCA11Y-1145: fix: get absolute path of execs

* DCA11Y-1145: chore: try with bashrc

* DCA11Y-1145: chore: try with env var for multishells

* DCA11Y-1145: chore: fnm dir needs to be basedir

* DCA11Y-1145: chore: fnm dir needs to be non existing dir

* DCA11Y-1145: clean up

* DCA11Y-1145: remove test that can't be set
…ger-support

# Conflicts:
#	frontend-maven-plugin/src/main/java/com/github/eirslett/maven/plugins/frontend/mojo/InstallNodeAndNpmMojo.java
#	frontend-maven-plugin/src/main/java/com/github/eirslett/maven/plugins/frontend/mojo/InstallNodeAndPnpmMojo.java
#	frontend-maven-plugin/src/main/java/com/github/eirslett/maven/plugins/frontend/mojo/InstallNodeAndYarnMojo.java
#	frontend-maven-plugin/src/main/java/com/github/eirslett/maven/plugins/frontend/mojo/WebpackMojo.java
#	frontend-plugin-core/src/main/java/com/github/eirslett/maven/plugins/frontend/lib/NPMInstaller.java
#	frontend-plugin-core/src/main/java/com/github/eirslett/maven/plugins/frontend/lib/NodeInstaller.java
#	frontend-plugin-core/src/main/java/com/github/eirslett/maven/plugins/frontend/lib/NodeVersionHelper.java
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants