Allow for execution of Run Config from non-Liberty projects, not just the current Liberty project

Open
#493 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
developer-experience, devtools

Research direction

Start by reviewing how the LT Run Config currently depends on the selected Liberty project and compare the related behavior across the three IDEs mentioned. Identify how the aggregator module and starting module are selected, then define completion as running the configuration from a non-Liberty project without relying on the current project selection.

Written by the indexing model from the issue text.

Description

multi-module

Our LT Run Config is, at the moment, surprisingly tied to a current project being selected.

It seems a complete view of this epic across the three IDEs would allow for breaking this link and just selecting the aggregator module and the starting module from the Run Config regardless of what is selected.

If this is too hard we can likely continue doing more like we do already and postpone this until we are ready, but let's include it for now.

Dominant language
Java
Stars
16
Forks
20
Avg merge
2d 9h
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenLiberty/liberty-tools-eclipse

All issues in OpenLiberty/liberty-tools-eclipse

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.