apache / apache/maven-shade-plugin
[MSHADE-353] Any transformer should be "relocatable"
- 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-353](https://issues.apache.org/jira/browse/MSHADE-353?redirect=false)** and commented
Need is to ensure any transformer can relocate its resource contents, even if originally not designed as such.
---
**Remote Links:**
- [GitHub Pull Request #39
](https://github.com/apache/maven-shade-plugin/pull/39)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the MSHADE-353 Jira issue and GitHub pull request #39 linked in the issue body. Determine how transformer resource contents are currently handled and define what behavior is required for every transformer to support relocation. Done means any transformer can relocate its resource contents, including transformers not originally designed for it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100