Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Confusing build process #66

Open
drtechie opened this issue Oct 9, 2023 · 5 comments
Open

Confusing build process #66

drtechie opened this issue Oct 9, 2023 · 5 comments
Assignees

Comments

@drtechie
Copy link
Member

drtechie commented Oct 9, 2023

The war file generation is not documented properly or the packages added to the project are confusing.

  1. The package.json script has "war" script that generates the build and runs a grunt task.
    The grunt task however results in an error.
> [email protected] grunt /Users/drtechie/Dev/PSMRI/HWC-UI
> grunt

Running "war:target" (war) task
Warning: Unexpected token * Use --force to continue.

Aborted due to warnings.
npm ERR! code ELIFECYCLE
npm ERR! errno 3
npm ERR! [email protected] grunt: `grunt`
npm ERR! Exit status 3
npm ERR! 
npm ERR! Failed at the [email protected] grunt script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

  1. GitHub Actions have one workflow file that packages the war file with mvn.

Questions

  1. Is the packaging done with grunt or mvn package?
  2. The GitHub workflow and pom.xml has many references to TMUI for this repo (HWC-UI).
  3. The pom.xml file has several references to internal IPs.
  4. There are at least 2 additional workflows present under .github folder which do not have the right .yml extension. Are these really used? Can we clean it up?
@ravishanigarapu
Copy link
Member

ravishanigarapu commented Oct 10, 2023 via email

@ravishanigarapu
Copy link
Member

ravishanigarapu commented Oct 10, 2023 via email

@drtechie
Copy link
Member Author

  1. In that case let's remove references to grunt. It's not required and adds unnecessary complexity.

  2. I get that HWC-UI was made from TM-UI. But that doesn't mean the artifactId and all the references of build generation should still be TM-UI. It must be cleaned up.

  3. This isn't helping either. dev hostnames and ports must be configurable for any developer so that they can set it up in local machine.
    Since this is a UI repo and Maven is only used to war generation, let's clean this up for building.

  4. There are 4 files in the folder. 2 of them don't have .yml extension. Are they used?

@ravishanigarapu
Copy link
Member

ravishanigarapu commented Oct 10, 2023 via email

@drtechie
Copy link
Member Author

Actions:

I will:

  1. Remove grunt.
  2. Remove references to internal IPs.
  3. Clean up the build process with maven.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants