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.
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.
After two years of hard daily work this bug is finally finished!
