source jars not attached to deployments
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 54
- Forks
- 380
- Avg merge
- 6h 49m
- Merged PRs (30d)
- 3
Description
When attempting to write a carbon plugin piggybacking off of the org.wso2.carbon.identity.application.mgt backend, the source of transitive dependency org.wso2.orbit.org.owasp.encoder:encoder:1.2.0.wso2v1 is not available with the maven artifact. This prevents the use of IDE autocomplete and documentation features. From reading the pom, it does not look like this has been addressed in 1.2.0.wso2v2
I've opened a similar ticket in IS's repository, as that's how I'm currently using these orbit packages: https://github.com/wso2/product-is/issues/5349
Contributor guide
No contributing guide indexed for this repository
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 inspecting the pom for org.wso2.orbit.org.owasp.encoder:encoder:1.2.0.wso2v1 and comparing it with 1.2.0.wso2v2. Check how this repository packages deployment artifacts and source jars; done means the transitive encoder dependency's source jar is available with the Maven artifact and the packaging behavior is covered by the relevant build verification.
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
- 38/100