-
Notifications
You must be signed in to change notification settings - Fork 100
consider commandlet dependencies #166
Copy link
Copy link
Closed
Labels
commandletrelated to commandlets (scripts/command/*)related to commandlets (scripts/command/*)enhancementNew feature or requestNew feature or requestscriptsrelated to shell scripts (bash and CMD)related to shell scripts (bash and CMD)softwaresoftware-package with 3rd party productssoftware-package with 3rd party products
Milestone
Metadata
Metadata
Assignees
Labels
commandletrelated to commandlets (scripts/command/*)related to commandlets (scripts/command/*)enhancementNew feature or requestNew feature or requestscriptsrelated to shell scripts (bash and CMD)related to shell scripts (bash and CMD)softwaresoftware-package with 3rd party productssoftware-package with 3rd party products
Currently when a commandlet is invoked manually to setup (e.g. not included in
DEVON_TOOLS) and it may have dependencies then the installation fails.Examples for dependencies:
We should therefore carefully consider if a commandlet shall be aware of its dependency and invoke setup on the dependency before.
Then
devon mvn setupwould automatically also invokedevon java setup.Are there drawbacks of this approach that I am issing?