eclipse-ee4j / eclipse-ee4j/soteria
POM Breaks WildFly 14 Feature Pack
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 73
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
https://issues.jboss.org/browse/WFLY-11265
[snip]
The org.glassfish.soteria:parent:1.0 pom has this unfortunate business:
--
...
01
1.1-b01-SNAPSHOT
${spec_impl_version}
...
release
01
1.0
So when they build their stuff using the 'release' profile they depend on the non-snapshot but anyone whose tooling is following their dependency tree but not declaring a 'release' profile is going to see a SNAPSHOT version. And of course people are quite likely not going to specify a 'release' profile if they are not doing a release of their own stuff.
[snip]
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 linked WFLY-11265 report and the org.glassfish.soteria:parent:1.0 POM. Compare the default properties with those in the release profile, then inspect how the dependency tree resolves without that profile. Done means consumers do not see an unintended SNAPSHOT dependency when they omit the release profile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100