Skip to content
This repository has been archived by the owner on Dec 20, 2022. It is now read-only.

Evaluate usage of the oomph library on org.aposin.gem.oomph #41

Open
d-gs opened this issue Nov 3, 2021 · 0 comments
Open

Evaluate usage of the oomph library on org.aposin.gem.oomph #41

d-gs opened this issue Nov 3, 2021 · 0 comments
Labels
Prio: Medium Medium Priority Status: Pending Issue or PR awaits response Type: Feature Issue or PR is a new feature

Comments

@d-gs
Copy link
Member

d-gs commented Nov 3, 2021

Feature request

Currently the EclipseLauncher works as following:

  1. XML files are manually created and saved forr oomph, so the workspace startup works as expected.
  2. The Eclipse installation is fixed and not configured via Oomph.

We should evaluate if it is possible to use the oomph libraries directly. For 2, each setup should provide its own Eclipse installation and workspace and use a bundle-pool to populate the required plug-ins.

If this is possible, the plug-ín should be completely refactored providing an unique Eclipse launcher (which creates the Eclipse installation and starts the workspace).
@d-gs d-gs added Prio: Medium Medium Priority Status: Pending Issue or PR awaits response Type: Feature Issue or PR is a new feature labels Nov 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Prio: Medium Medium Priority Status: Pending Issue or PR awaits response Type: Feature Issue or PR is a new feature
Milestone
No milestone
Development

No branches or pull requests
1 participant
@d-gs