https://bugzilla.redhat.com/show_bug.cgi?id=1666493
Hirotaka Wakabayashi <hiwkby(a)yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hiwkby(a)yahoo.com
--- Comment #8 from Hirotaka Wakabayashi <hiwkby(a)yahoo.com> ---
Hello Michael,
I found openliberty-19.0.0.1.tar.gz, which should contains source code(java
files), contains jar files. The guideline says jar files from upstream
releases MUST NOT be used during build of Fedora packages.
https://docs.fedoraproject.org/en-US/packaging-guidelines/Java/#_pre_buil...
I understand the basic process to build source files is:
1) prepare in the %prep section
2) build source files in the %build section
3) install the compile files to the the buildroot
Therefor you should use the %prep section to uncompress
openliberty-19.0.0.1.tar.gz,
which contains java files, and extract the contents into the build directory.
You can use the %setup macro. For example,
```
%prep
%setup
```
See
http://ftp.rpm.org/max-rpm/s1-rpm-inside-macros.html for details.
Then you should use the %build section to compile java files in the build
directory. For example,
```
%build
make {?_smp_flags}
```
Finally you should use the %install section to install the jar files. For
example,
```
%install
install -p -m 644 foo.jar %{buildroot}%{_javadir}/foo.jar
```
Java Packaging HOWTO must help you very much. It shows many examples and
is very easy to understand for me.
https://fedora-java.github.io/howto/latest/
After you make your source rpm file, you can check it by using Koji.
See
https://fedoraproject.org/wiki/Using_the_Koji_build_system for details.
Here is the current Koji scratch build result:
https://koji.fedoraproject.org/koji/taskinfo?taskID=34779979
Error messages says:
```
error: Bad file:
/home/travis/build/was-lighthouse/openliberty-rpmdeb/rpmbuild/SOURCES/openliberty-19.0.0.1.tar.gz:
No such file or directory
```
The /home/travis/build/was-lighthouse/openliberty-rpmdeb/rpmbuild directory may
exist in your local development environment. However you should not assume the
directory is present anywhere.
Best Regards,
Hirotaka Wakabayashi
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component