Bug 711350

Version 6 was released - I'll update this spec file to reflect this soon.

Created attachment 513487 [details]
jboss-parent.spec

now it work

the problem was here

install -d -m 755 $RPM_BUILD_ROOT%{_mavenpomdir}
install -pm 644 pom.xml $RPM_BUILD_ROOT%{_mavenpomdir}/JPP.jboss-%{name}.pom
%add_to_maven_depmap org.jboss %{name} %{version} JPP jboss/%{name}

modified in this way (thanks to alt linux) works

install -d -m 755 $RPM_BUILD_ROOT%{_mavenpomdir}
install -pm 644 pom.xml $RPM_BUILD_ROOT%{_mavenpomdir}/JPP-%{name}.pom
%add_to_maven_depmap org.jboss %{name} %{version} JPP %{name}

(In reply to comment #4)
> the problem was here

Submitted spec file follows Fedora guidelines and is buildable. Specified change is not necessary for Fedora, although it may be necessary for other distros like Mageia as we discussed it on IRC.

Updated files to version 6, using new %add_maven_depmap macro.

Spec URL:
http://goldmann.fedorapeople.org/package_review/jboss-parent/2/jboss-parent.spec
SRPM URL:
http://goldmann.fedorapeople.org/package_review/jboss-parent/2/jboss-parent-6-1.fc16.src.rpm

And a scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=3222447

I would do this one.

Package Review
==============

Key:
- = N/A
x = Check
! = Problem
? = Not evaluated

=== REQUIRED ITEMS ===
[!]  Rpmlint output:
jboss-parent.noarch: W: invalid-url URL: http://www.jboss.org/ HTTP Error 403: Forbidden
False positive.
./jboss-parent.spec: W: no-%build-section
Please add a build section with mvn-rpmbuild install in it. This will help not missing newly added dependencies in future versions because the build will fail this way.
./jboss-parent.spec: W: invalid-url Source0: jboss-parent-6.tar.xz
Generated one so it's fine.

[x]  Package is named according to the Package Naming Guidelines[1].
[x]  Spec file name must match the base package name, in the format %{name}.spec.
[x]  Package meets the Packaging Guidelines[2].
[x]  Package successfully compiles and builds into binary rpms.
[x]  Buildroot definition is not present
[x]  Package is licensed with an open-source compatible license and meets other legal requirements as defined in the legal section of Packaging Guidelines[3,4].
[x]  License field in the package spec file matches the actual license.
License type: LGPLv2+
[-]  If (and only if) the source package includes the text of the license(s) in its own file, then that file, containing the text of the license(s) for the package is included in %doc.
[-]  All independent sub-packages have license of their own
[x]  Spec file is legible and written in American English.
[-]  Sources used to build the package matches the upstream source, as provided in the spec URL.
[!]  All build dependencies are listed in BuildRequires, except for any that are listed in the exceptions section of Packaging Guidelines[5].
A lot of pacakges will need ot be added to Buildrequires but there was a shortcut for saying that all BuildRequries are requires or smth like this
[x]  Package must own all directories that it creates.
[x]  Package requires other packages for directories it uses.
[x]  Package does not contain duplicates in %files.
[x]  File sections do not contain %defattr(-,root,root,-) unless changed with good reason
[x]  Permissions on files are set properly.
[x]  Package does NOT have a %clean section which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT). (not needed anymore)
[x]  Package consistently uses macros (no %{buildroot} and $RPM_BUILD_ROOT mixing)
[x]  Package contains code, or permissable content.
[x]  Fully versioned dependency in subpackages, if present.
[-]  Package contains a properly installed %{name}.desktop file if it is a GUI application.
[x]  Package does not own files or directories owned by other packages.
[-]  Javadoc documentation files are generated and included in -javadoc subpackage
[-]  Javadocs are placed in %{_javadocdir}/%{name} (no -%{version} symlinks)
[x]  Packages have proper BuildRequires/Requires on jpackage-utils
[-]  Javadoc subpackages have Require: jpackage-utils
[-]  Package uses %global not %define
[x]  If package uses tarball from VCS include comment how to re-create that tarball (svn export URL, git clone URL, ...)
[x]  If source tarball includes bundled jar/class files these need to be removed prior to building
[x]  All filenames in rpm packages must be valid UTF-8.
[-]  Jar files are installed to %{_javadir}/%{name}.jar (see [6] for details)
[x]  If package contains pom.xml files install it (including depmaps) even when building with ant
[x]  pom files has correct add_maven_depmap

=== Maven ===
[x]  Use %{_mavenpomdir} macro for placing pom files instead of %{_datadir}/maven2/poms
[-]  If package uses "-Dmaven.test.skip=true" explain why it was needed in a comment
[-]  If package uses custom depmap "-Dmaven.local.depmap.file=*" explain why it's needed in a comment
[!]  Package DOES NOT use %update_maven_depmap in %post/%postun
[!]  Packages DOES NOT have Requires(post) and Requires(postun) on jpackage-utils for %update_maven_depmap macro

=== Other suggestions ===
[x]  If possible use upstream build method (maven/ant/javac)
[x]  Avoid having BuildRequires on exact NVR unless necessary
[x]  Package has BuildArch: noarch (if possible)
[x]  Latest version is packaged.

=== Issues ===
1. Add a build section to let mvn check the dependencies.
2. Drop update_maven_depmap
3. Drop Requires(post|postun) on jpackage-utils
4. -n %{name}-%{version} can be omitted this is the default

Fixed!

Spec URL:
http://goldmann.fedorapeople.org/package_review/jboss-parent/3/jboss-parent.spec
SRPM URL:
http://goldmann.fedorapeople.org/package_review/jboss-parent/3/jboss-parent-6-2.fc15.src.rpm

Scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=3235374

Looks good.
APPROVED

Thank you for review!

New Package SCM Request
=======================
Package Name:      jboss-parent
Short Description: JBoss Parent POM
Owners:            goldmann
Branches:          f16

Git done (by process-git-requests).

Thank you, closing.