As part of productization, aggregate javadocs are installed into a naming scheme similar to <literal>"_javadocdir"/%"name"-%"namedversion"</literal>, where <literal>%"name"</literal> is the package name and <literal>%"namedversion"</literal> is the full productized version (this is not the same as the RPM <literal>%"version"</literal>). Subsequently, an unversioned symbolic link is added. The hibernate4 javadoc currently uses an unversioned directory, which does not match packages. As a result, wildcards used in the file exacerbate this problem.
The current productization policy is to install aggregate javadocs into %{_javadocdir}/%{name}-%{namedversion}, where %{name} is usually the package name and %{namedversion} is the full productized version (usually this is NOT equal to the RPM %{version}). Then, an unversioned symlink to this directory is added. It's currently using an unversioned directory, which doesn't match other packages.
Also, the use of wildcards in the file list may exacerbate this problem. When you do something like
%files
%_javadocdir/*
it is not immediately apparent what directories are going to be included, so spotting a bug in the files is more difficult.
Version-Release number of selected component: hibernate4-4.2.0-4.Final_redhat_1.ep6.el6.
The affected component is hibernate, but as we currently do not have a hibernate component, we've put it under unspecified for now, I have asked John to create that for us and will move this to the appropriate component when it is created.
Assigning to Dave.
Checked in EWS 2.1.0-ER3 and its not correct i think.
We have these directory structure in hibernate-dist.zip:
hibernate-release-4.2.13.Final-redhat-1/documentation/javadocs/...
(In reply to Libor Fuka from comment #6)
> Checked in EWS 2.1.0-ER3 and its not correct i think.
> We have these directory structure in hibernate-dist.zip:
> hibernate-release-4.2.13.Final-redhat-1/documentation/javadocs/...
I was under the impression that this bug was referring to the javadoc directory installed by the RPM rather than what is contained in the zip.
ie. /usr/share/javadoc/hibernate4 -> hibernate-4.2.13.Final-redhat-1
(In reply to Dave Stahl from comment #7)
> I was under the impression that this bug was referring to the javadoc
> directory installed by the RPM rather than what is contained in the zip.
> ie. /usr/share/javadoc/hibernate4 -> hibernate-4.2.13.Final-redhat-1
Correct. This bug is RPM-only.
The current productization policy is to install aggregate javadocs into %{_javadocdir}/%{name}-%{namedversion}, where %{name} is usually the package name and %{namedversion} is the full productized version (usually this is NOT equal to the RPM %{version}). Then, an unversioned symlink to this directory is added. It's currently using an unversioned directory, which doesn't match other packages. Also, the use of wildcards in the file list may exacerbate this problem. When you do something like %files %_javadocdir/* it is not immediately apparent what directories are going to be included, so spotting a bug in the files is more difficult. Version-Release number of selected component: hibernate4-4.2.0-4.Final_redhat_1.ep6.el6.