[Bug 614836] Review Request: maven-checkstyle-plugin - Maven Checkstyle Plugin

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=614836

Stanislav Ochotnicky <sochotni at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |sochotni at redhat.com
         AssignedTo|nobody at fedoraproject.org    |sochotni at redhat.com
               Flag|                            |fedora-review?

--- Comment #2 from Stanislav Ochotnicky <sochotni at redhat.com> 2010-07-15 09:39:27 EDT ---
OK: rpmlint must be run on every package. The output should be posted in the
review.

maven-checkstyle-plugin.noarch: W: non-conffile-in-etc
/etc/maven/fragments/maven-checkstyle-plugin
3 packages and 0 specfiles checked; 0 errors, 1 warnings.

OK: The package must be named according to the Package Naming Guidelines .
OK: The spec file name must match the base package %{name}, in the format
%{name}.spec unless your package has an exemption.  .
OK: The package must meet the Packaging Guidelines .
OK: The package must be licensed with a Fedora approved license and meet the
Licensing Guidelines .
OK: The License field in the package spec file must match the actual license. 
OK: 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 must be included in %doc.
OK: The spec file must be written in American English. 
OK: The spec file for the package MUST be legible. 
OK: The sources used to build the package must match the upstream source, as
provided in the spec URL. Reviewers should use md5sum for this task. If no
upstream URL can be specified for this package, please see the Source URL
Guidelines for how to deal with this.
OK: The package MUST successfully compile and build into binary rpms on at
least one primary architecture. 
NEEDSWORK: All build dependencies must be listed in BuildRequires, except for
any that are listed in the exceptions section of the Packaging Guidelines ;
inclusion of those as BuildRequires is optional. Apply common sense.

Your BRs are basically good, but it's better to be specific in these
cases (just like you specified maven2 >= 2.2.1):

checkstyle >= 5.1-1
objectweb-asm > 3.2-1

Without these the build can fail (it did on my F-13 mixed with rawhide packages
:-) ). After I updated those two everything went fine.

OK: Packages must NOT bundle copies of system libraries.
OK: A package must own all directories that it creates. If it does not create a
directory that it uses, then it should require a package which does create that
directory. 
OK: A Fedora package must not list a file more than once in the spec file's
%files listings. 
OK: Permissions on files must be set properly. Executables should be set with
executable permissions, for example. Every %files section must include a
%defattr(...) line. 
OK: Each package must consistently use macros. 
OK: The package must contain code, or permissable content. 
OK: Large documentation files must go in a -doc subpackage. (The definition of
large is left up to the packager's best judgement, but is not restricted to
size. Large can refer to either size or quantity). 
OK: If a package includes something as %doc, it must not affect the runtime of
the application. To summarize: If it is in %doc, the program must run properly
if it is not present. 
OK: Packages must not own files or directories already owned by other packages.
The rule of thumb here is that the first package to be installed should own the
files or directories that other packages may rely upon. This means, for
example, that no package in Fedora should ever share ownership with any of the
files or directories owned by the filesystem or man package. If you feel that
you have a good reason to own a file or directory that another package owns,
then please present that at package review time. 
OK: All filenames in rpm packages must be valid UTF-8. 

Other notes:
 * You are skipping tests. If they compile fine (and to me it seems
 they do, it's usually better to just
 -Dmaven.test.failure.ignore=true. This way tests are run, you can see
 the output and build doesn't fail when tests fail.
 * Might be a good idea and try those tests with upstream maven. They
 usually succeed, but if they fail with upstream -> file bugs
 * IMPORTANT:
   You are missing provides/obsoletes for
   maven2-plugin-checkstyle. See other maven-X-plugin packages spec files.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.