Description of problem: One of my packages (jinput) failed the Rawhide rebuild because: - https://fedorahosted.org/released/javapackages/doc/#_add_maven_depmap_macro says that projects built with ant that provides POMs should use the %add_maven_depmap macro, then own the files in %{_mavendepmapfragdir}. - the javapackages-tools package provides /usr/lib/rpm/macros.d/macros.jpackage, which defines %{_mavendepmapfragdir} to be %{_datadir}/maven-fragments - the javapackages-tools package also provides /usr/lib/rpm/macros.d/macros.fjava, which defines %add_maven_depmap as dumping files into %{_datadir}/maven-metadata May I suggest that macros.fjava should not be using an explicit path there, but should be using a macro that expands to the path (whether it be %{_mnavendepmapfragdir} or something else), and that macro should be the same one described in the fedorahosted docs? Version-Release number of selected component (if applicable): javapackages-tools-4.0.0-5.fc21.noarch How reproducible: Always Steps to Reproduce: 1. Try to build jinput in mock 2. 3. Actual results: The build fails because of the path mismatch noted above. Expected results: Successful build. Additional info:
The migration from depmaps to metadata was intentional. Documentation probably needs to be revised.
(In reply to Mikolaj Izdebski from comment #1) > The migration from depmaps to metadata was intentional. Documentation > probably needs to be revised. Since this change actually breaks packages, maybe an announcement to fedora-devel would not be out of place?
(In reply to David Tardon from comment #2) > (In reply to Mikolaj Izdebski from comment #1) > > The migration from depmaps to metadata was intentional. Documentation > > probably needs to be revised. > > Since this change actually breaks packages, maybe an announcement to > fedora-devel would not be out of place? Mikolaj formally announced this change in May, I believe: https://lists.fedoraproject.org/pipermail/java-devel/2014-May/005243.html https://lists.fedoraproject.org/pipermail/java-devel/2014-May/005248.html
(In reply to Mat Booth from comment #3) > Mikolaj formally announced this change in May, I believe: > > https://lists.fedoraproject.org/pipermail/java-devel/2014-May/005243.html > https://lists.fedoraproject.org/pipermail/java-devel/2014-May/005248.html I was talking about fedora-devel. Not all package maintainers read java-devel.
This was a problem with our release script which wasn't uploading the documentation due to a problem with group permissions at fedorahosted.org [1], which has just been fixed. I have uploaded the new documentation. It doesn't recommend using %{_mavendepmapfragdir} and it contains a section [2] describing migration from the legacy %{_mavendepmapfragdir} directory. Closing as NOTABUG as this wasn't a bug in the package, but a problem with website. [1] https://fedorahosted.org/fedora-infrastructure/ticket/4410 [2] https://fedorahosted.org/released/javapackages/doc/#_add_maven_depmap_macro_2