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

ability to configure central software installation directory #152

Closed
hohwille opened this issue Jul 29, 2019 · 2 comments
Closed

ability to configure central software installation directory #152

hohwille opened this issue Jul 29, 2019 · 2 comments
Labels
enhancement New feature or request scripts related to shell scripts (bash and CMD) software software-package with 3rd party products
Milestone

Comments

@hohwille
Copy link
Member

Currently every ide installation has its own isolated software folder. This is the way this IDE solution is designed to work. However, for power-users, that may have up to ~100 parallel installations this multiplies the required disc-space per software folder per number of installations even if all IDE installations would share the same versions.

This enhancement shoud allow to configure an optional environment variable DEVON_SOFTWARE_REPO (ideally in ~/devon.properties - see #151). In case that variable is set, it must point to an existing directory. Further, it would change the behaviour of doInstall such that the software is saved to ${DEVON_SOFTWARE_REPO}/${software}/${version} and then symlinked to ${DEVON_IDE_HOME}/software/${software}.
Hence each version of each software tool would physically be only present once on your disc saving lots of disc-space.

However, there are some drawbacks of this feature:

  • software that is manipulated (enhanced with plugins/extensions) will cause these manipulations to have side-effects to all projects sharing the same software tool version.
  • additional complexity
  • issues with symlinks and permissions on windows.

However, as this feature would be optional and not active by default it would still be cool for those that want to use it.

@hohwille hohwille added enhancement New feature or request scripts related to shell scripts (bash and CMD) software software-package with 3rd party products labels Jul 29, 2019
@hohwille
Copy link
Member Author

There is a high danger to confuse this feature with #98.
As #98 already introduced a variable DEVON_SOFTWARE_REPOSITORY we should come up with a different name here to avoid confusion.
IMHO compared to maven #98 is the remote repository while this feature is about introducing a "local repository as cache". Maybe this analogy can be used for documentation, etc.

hohwille added a commit that referenced this issue Jul 30, 2019
#151: fix for commandlet invocations so un-exported variables remain visible
#145: fix for doUpgradeMavenArtect invoking doInstall (was forgotten on refactoring)
@hohwille
Copy link
Member Author

Done with PR #155

@hohwille hohwille added this to the release:3.0.0 milestone Jul 30, 2019
hohwille added a commit that referenced this issue Aug 1, 2019
* #159: devon4j migration improved/fixed
* #160: switched from OpenJDK to AdoptOpenJDK
* #161: fixed mvn invocation and exit code
* #162: propagate exit code
* #152: fix if installed software is reused (proper exit code so post installation quirks/enhancements are only once)
* #157: reuse local maven repo for integration tests to avoid waste
* #159: #157: improved integration test, create archetype and also test migration
* #18: archetype catalog should come with most recent archetype, updated and verify via test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request scripts related to shell scripts (bash and CMD) software software-package with 3rd party products
Projects
None yet
Development

No branches or pull requests

1 participant