[MSOURCES-143] Can't create a source and test jar in Commons using commons-parent
A pull request for this has already been merged.
- #24 by @hboutemy — merged
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system
Research direction
Reproduce the failure using the listed commons-parent and commons-cli checkout commands, then inspect the Maven Source Plugin 3.3.0 source-jar execution and the linked merged pull request #24. Done means the Commons build no longer fails with the duplicated-artifacts error when source and test jars are configured through commons-parent.
Written by the indexing model from the issue text.
Description
Gary D. Gregory opened MSOURCES-143 and commented
Steps to reproduce:
- git clone https://gitbox.apache.org/repos/asf/commons-parent.git
- cd commons-parent
- git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
- mvn clean install
- cd ..
- git clone https://gitbox.apache.org/repos/asf/commons-cli.git
- cd commons-cli
- git checkout 08f8c5034a8492be6db65b2086341c292489ee53
- mvn clean package
[INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
[ERROR] We have duplicated artifacts attached.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.233 s
[INFO] Finished at: 2023-08-15T15:39:45-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork (create-source-jar) on project commons-cli: Presumably you have configured maven-source-plugn to execute twice times in your build. You have to configure a classifier for at least on of them. -> [Help 1]
Affects: 3.3.0
Issue Links:
- MSOURCES-121 Check for duplicated addition of the same file
("is caused by") - MSOURCES-140 Build fails when using install deploy
4 votes, 9 watchers
- Dominant language
- Java
- Stars
- 37
- Forks
- 38
- Avg merge
- 22h 35m
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from apache/maven-source-plugin
-
Fix Jenkins buildOpenbug priority:critical
Difficulty 3/5 1-2 days Newbie friendliness 48/100
apache/maven-source-plugin#311 · 1 comment ·
-
TestSourceJarMojo forks to generate-sources instead of generate-test-sourcesMay be free again @elharo claimed this 58 days ago, and no pull request is open. Openbug priority:major
apache/maven-source-plugin#304 · 3 comments · 1 assignee ·
-
bug priority:blocker
Difficulty 4/5 3-5 days Newbie friendliness 25/100
apache/maven-source-plugin#261 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
apache/maven-source-plugin#244 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apache/maven-source-plugin#239 ·
All issues in apache/maven-source-plugin
Similar issues
-
cbor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
FasterXML/jackson-dataformats-binary#844 ·
Maintainers usually reply within 1 day
-
improvement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/iceberg#18351 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
repowise-dev/repowise#2945 · 1 comment ·
Maintainers usually reply within 1 day
-
Interpolating settings.xml can lead to malformed XML when variable value contains double-hyphenOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/maven#13321 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
liquid-java/liquidjava#321 ·
Maintainers usually reply within 2 days