OpenLiberty / OpenLiberty/liberty-tools-eclipse
Though using multi-project Gradle the suggested run config uses Maven multi-mod
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 16
- Forks
- 20
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Description
I set up a Gradle multi-project build from: https://github.com/OpenLiberty/ci.gradle/tree/main/src/test/resources/loose-ear-test.
(Since it's an IT it needed some tweaking.. plus buildship likes to treat this as a single Eclipse project.
So I won't go into detail on how to set this up).
But like our multi-mod Maven examples, this has a server.xml at the EAR level.
When I did a Start from the ear-level project, the suggested run config was as if we were using multi-mod Maven:
-f ../pom.xml -am -pl ejb-ear
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 with the multi-project Gradle example at the linked ci.gradle test-resource path and reproduce a Start from the EAR-level project. Inspect how the suggested run configuration is selected when server.xml is at the EAR level, then verify that the generated configuration uses the Gradle project rather than the Maven-style arguments shown in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100