OpenLiberty / OpenLiberty/liberty-tools-eclipse
Considerations for project migrations
Open
Nobody has claimed this yet.
design
enhancement
- Dominant language
- Java
- Stars
- 16
- Forks
- 20
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Description
Consider what we should do for classic projects that work in Eclipse IDE and with classic Liberty Developer Tools. e.g., do we need to help migrate them over to be Maven or Gradle-based projects to work with dev mode and tools?
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
Start by reviewing how classic projects using Eclipse IDE and classic Liberty Developer Tools differ from Maven- or Gradle-based projects. Assess what migration support would be needed for dev mode and tools; done should be a documented migration approach or decision covering these project types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100