apache / apache/maven-shade-plugin
[MSHADE-231] Multiple shade artifacts + reduced pom from the same artifact
- Dominant language
- Java
- Stars
- 188
- Forks
- 103
- Avg merge
- 16h 39m
- Merged PRs (30d)
- 4
Description
**[Romain Manni-Bucau](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=romain.manni-bucau)** opened **[MSHADE-231](https://issues.apache.org/jira/browse/MSHADE-231?redirect=false)** and commented
Hi guys,
in tomee we create several flavors of tomee-embedded from tomee-embedded module.
We basically deploy:
- tomee-embedded normal jar
- tomee-embedded "uber" shade
- tomee-embedded "jaxws" shade
- tomee-embedded "jaxrs" shade
We would add few more flavors if we can solve this issue: we can't get reduced pom and attach it to let our users depend on the reduced pom.
Best would be to:
1- have the reduced pom created in target/
2- attach it to deploy it with another artifact (to avoid pom conflicts)
is that something mvn-shade could do?
Here is the pom: https://github.com/apache/tomee/blob/master/tomee/tomee-embedded/pom.xml#L55
Side note: the obvious fix it to define 1 pom by shade but it would make the maintenance harder for us and create inconsistencies long term.
---
2 votes, 2 watchers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Maven configuration linked in the issue, especially the tomee-embedded shade executions, then trace how the plugin handles shaded artifacts and reduced POM generation. Determine whether a reduced POM can be written to target/ and attached under another artifact without POM conflicts; done means the behavior is implemented and covered by relevant plugin tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100