Bug 1231430 - Missing jinterface maven metadata
Summary: Missing jinterface maven metadata
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: erlang
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 1228503
TreeView+ depends on / blocked
Reported: 2015-06-13 09:32 UTC by gil cattaneo
Modified: 2018-11-20 14:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-12-12 10:07:03 UTC
Type: Bug

Attachments (Terms of Use)

Description gil cattaneo 2015-06-13 09:32:31 UTC
Description of problem:
erlang-jinterface do not provides maven metadata, which used by some projects
e.g. https://github.com/spring-projects/spring-amqp/ (spring-erlang sub module)

The pom file is available but is not installed
and the JAR file should be placed in %_javadir

The spec file "should be" modified in this way:

%if %{?fedora} >= 21
BuildRequires: javapackages-local
BuildRequires: maven-local

jinterface_lib_dir="$(ls -d1 $RPM_BUILD_ROOT%{_libdir}/erlang/lib/jinterface-*/ | sed "s,^$RPM_BUILD_ROOT,,")" test -d "$RPM_BUILD_ROOT$jinterface_lib_dir"

rm -rf "${jinterface_lib_dir}priv/OtpErlang.jar"

if the pom file is not processed
sed 's/%VSN%/%{version}/' <otp/lib/jinterface/java_src/pom.xml.src >pom.xml

generates maven metadata
%mvn_artifact [path of the processed pom file]/pom.xml [path of the built java library]/[name of the java library].jar

install JAR file in %_javadir and generate a its symlink

%mvn_file org.erlang.otp:jinterface erlang/OtpErlang ${jinterface_lib_dir}priv/OtpErlang 

Version-Release number of selected component (if applicable):

How reproducible:

Comment 1 Jan Kurik 2016-07-26 04:33:17 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 2 Fedora End Of Life 2017-11-16 19:52:02 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:07:03 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.