Bug 170485

Summary:	dev-java/log4j depens on openjms-bin and not openjms
Product:	Gentoo Linux	Reporter:	Nicolas Laplante <nicolas.laplante>
Component:	New packages	Assignee:	Java team <java>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Nicolas Laplante 2007-03-11 20:32:59 UTC

I have pulled openjms (the one built from source) on my system. But, when I do "emerge --uDpv world", it still wants to pull openjms-bin. I did an "equery -d openjms-bin" and it told me that dev-java/log4j wants openjms-bin when switching on the "jms" USE flag.

I think there should be a "virtual/openjms" or something like that to prevent having to pull both the -bin and source versions.

Reproducible: Always

Steps to Reproduce:
1. Emerge openjms (not -bin)
2. Emerge log4j with "jms" USE flag

Actual Results:  
It wants to pull openjms-bin


Expected Results:  
It should have detected that JMS is indeed installed

I have seen in the ebuild that the path to the jms jar is hardcoded in the ebuild. There should be a way to automatically detect this. I just re-emerged log4j after hardcoding "/opt/openjms/lib/openjms-0.7.6.1.jar", and it built fine.

Comment 1 Petteri Räty (RETIRED) gentoo-dev

2007-03-11 21:22:40 UTC

Yes virtuals for java are coming but need quite a lot of code in java-config first. The reason that log4j wants openjms-bin is that openjms depends on log4j and as such it would create a circular dependency.

Comment 2 Petteri Räty (RETIRED) gentoo-dev

2009-05-18 19:53:39 UTC

After two years of hard daily work this bug is finally finished!