Let VisualVM export and import nodes with their configuration for the 'Remote' node
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Mostly about a missing feature. When I do an upgrade for example from 2.0.x to 2.0.4, or a new clean installation in other machine, Within the Remote node I must re create all the nodes with their respective configuration
Describe the solution you'd like
Do right click in the Remote node and let me export and import through a specific selection.
Therefore once accomplished the export approach, then later through the import approach I can re use all of them in a new machine or in a new version of VisualVMt
Describe alternatives you've considered
None
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue targets the VisualVM Remote node and asks for context-menu actions to export and import all remote nodes with their configurations. Start by locating the Remote node implementation and its existing configuration persistence; define completion as successfully moving the configured Remote nodes between installations or VisualVM versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100