Skip to content

Align tool names in scripts #1085

@hohwille

Description

@hohwille

For epic #941 and as special addition for story #1084 we want to use the migration from mirrors to urls also as cleanup:
In general we follow the best practice and convention that if we have a tool «tool» then we use the same name in the following places:

  • commandlet: scripts/command/«tool»
  • software folder: software/[extra/|macos/]«tool»
  • ide-urls folder: ide-urls/«tool»/«edition»/«version»/
  • variables: «TOOL»_VERSION and «TOOL»_EDITION
  • When running devon «tool» «args» you should get the same effect as when running devon followed by «tool» «args» except that if the tool is not yet installed in the first case it will be downloaded and installed and in the second case it will fail as the tool is not installed.

However, there are currently the following excuses/exceptions to that rule:

  • mvn vs. maven - as the command to run is given as mvn we have to use that instead of maven consistently.
  • node vs. nodejs - as the command to run is given as node we have to use that instead of nodejs consistently.
  • sonar vs. sonarqube - here we do not have any matching given command except StartSonar.bat or the like that is not even in the PATH after set by devon command. For simplicity, I would propose to stay with the shorter name sonar and rename sonarqube occurances to sonar.
  • cobigen vs. cobigen-cli vs. cli. The command is actually cg and cobigen. We can discuss with @jan-vcapgemini but IMHO cobigen is more self explanatory than cg that could confuse new users that might never get what this is about and therefore miss the according features behind it.

The acceptance criteria of this story is that devonfw-ide strictly follows this rules.
Therefore according scripts (see details above) need to be adapted accordingly.
Further we also have to change our devon.properties:

export MAVEN_HOME=${DEVON_IDE_HOME}/software/maven

Please also do a cleanup of internal variables such as COBIGEN_CLI_HOME vs. COBIGEN_HOME, etc.

This story does NOT care about backward compatibility as this is addressed by #1087.

Blocked by dependencies:

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions