Bug 9318 - hawtjni requires xbean, but should not
Summary: hawtjni requires xbean, but should not
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: High normal
Target Milestone: Mageia 3
Assignee: D Morgan
QA Contact:
URL:
Whiteboard:
Keywords: Junior_job, PATCH
Depends on:
Blocks:
 
Reported: 2013-03-10 09:14 CET by Hartmut Goebel
Modified: 2013-08-26 18:33 CEST (History)
1 user (show)

See Also:
Source RPM: hawtjni-1.6-1.mga3.noarch.prm
CVE:
Status comment:

Attachments
removing xbean in runtime dependency. (334 bytes, patch)
2013-07-23 20:43 CEST, benoît tuduri 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Hartmut Goebel 2013-03-10 09:14:54 CET 
The `hawtjni` package requires `xbean`, but does not use it. This dependency should be removed.

xbean in only mentioned in `JPP-hawtjni-generator.pom`, which is a development file. So `xbean` is a *build* dependence, not a run-time rependency. But since this dependency is set, every application using hawtjni is installing xban, too. (And many packages xbeans is requiring).

Please remove the dependency.
Hartmut Goebel 2013-03-10 09:15:37 CET

Source RPM: hawtjni-1.6-1.mga3 => hawtjni-1.6-1.mga3.noarch.prm

Manuel Hiebel 2013-03-13 22:48:32 CET

Assignee: bugsquad => dmorganec

Hartmut Goebel 2013-07-19 20:16:38 CEST

Keywords: (none) => Junior_job

Comment 1 benoît tuduri 2013-07-23 20:43:39 CEST 
Created attachment 4219 [details]
removing xbean in runtime dependency.

Thank you Hartmut Goebel,
Like you said I put a patch to fix it. It should be applied on the spec file.

Sincerly

CC: (none) => benoit.tuduri

Hartmut Goebel 2013-07-24 08:38:30 CEST

Keywords: (none) => PATCH

Comment 2 Samuel Verschelde 2013-08-26 18:33:34 CEST 
I committed it to SVN and submitted an new cauldron build. Closing. Hartmut, please reopen if an update to Mageia 3 is needed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.