Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34157 - [junit] PKGBUILD referring to deprecated source location
Attached to Project:
Arch Linux
Opened by Yanus Poluektovich (ypoluektovich) - Tuesday, 05 March 2013, 16:35 GMT
Last edited by Guillaume ALAUX (galaux) - Sunday, 10 March 2013, 19:52 GMT
Opened by Yanus Poluektovich (ypoluektovich) - Tuesday, 05 March 2013, 16:35 GMT
Last edited by Guillaume ALAUX (galaux) - Sunday, 10 March 2013, 19:52 GMT
|
DetailsDescription:
Currently (version 4.11-1) the PKGBUILD for JUnit gets the sources from the archives on Kent Beck's GitHub account. However, since it's last been updated, the repository has been moved to [1]. Kent Beck's repository has been either deleted or made private. This matters because: - there is no guarantee that Kent will keep the repository up-to-date, if at all; - as evidenced at [2], since version 4.11 JUnit is distributed as one jar (junit.jar), instead of two (junit-dep.jar is gone). However, current ArchLinux version of the junit package ships with a junit-dep jar. The reason for originally having two jars is that one of them (junit.jar) also packed a dependency (hamcrest), whereas junit-dep.jar was pure JUnit. Since JUnit version 4.11, they got rid of the junit+hamcrest package; one must now use proper dependency management tools to obtain hamcrest-core.jar (currently the dependency is on version 1.3). There is an AUR package named 'hamcrest', but at the time of my writing this, it's out of date. (1.3RC2, while the current version of Hamcrest is just 1.3. I've flagged it.) To fix everything, it might be necessary to promote that package to the official repository. However, there is a snag: aur/hamcrest does not pack a set of separate jars, but an all-inclusive hamcrest-all.jar. One could leave it as is, but it's not advisable due to possible Java classpath issues in applications with complex dependencies. [1] https://github.com/junit-team/junit [2] https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.md#maven-artifacts P.S.: it should also be noted that the 'url' field of the PKGBUILD is incorrect: www.junit.org does not exist, the correct link would be http://junit.org/. |
This task depends upon
Closed by Guillaume ALAUX (galaux)
Sunday, 10 March 2013, 19:52 GMT
Reason for closing: Implemented
Additional comments about closing: Implemented in 4.11-2
Sunday, 10 March 2013, 19:52 GMT
Reason for closing: Implemented
Additional comments about closing: Implemented in 4.11-2
- created package java-hamcrest with split jars
- junit 4.11-2 now only provides junit-dep, the light junit jar (renamed in Arch as 'junit')
- junit now depends on java-hamcrest
- fixed 'source' and 'url' in junit
I will inform AUR owner of 'hamcrest' about it.
Thank you for this report.