meta-java: rely on well known bootstrap-path

Instead of potential circular depending virtual/javac-native (even this
recipe provides such a useable java-native), rely on well known path
via cacao-native to build up to icedtea7-native in reliable manner.

virtual/javac-native should be used by parts not belonging to the bootstrap
phase.

Signed-off-by: Jens Rehsack <sno@netbsd.org>
Signed-off-by: Maxin B. John <maxin.john@intel.com>

2 files changed, 9 insertions, 1 deletions

diff --git a/classes/java-bootstrap-components.bbclass b/classes/java-bootstrap-components.bbclass
new file mode 100644
index 0000000..0c62b5b
--- /dev/null
+++ b/classes/java-bootstrap-components.bbclass
@@ -0,0 +1,7 @@
+# This is to be used by recipes which rely on java-library.bbclass
+# infrastructure and their a *-native recipe are parts of the bootstrap
+# process
+#
+
+DEPENDS_prepend_class-native = " ecj-bootstrap-native "
+DEPENDS_prepend_class-target = " virtual/javac-native "
diff --git a/classes/java-library.bbclass b/classes/java-library.bbclass
index 144cd2f..a192f14 100644
--- a/classes/java-library.bbclass
+++ b/classes/java-library.bbclass
@@ -35,7 +35,8 @@ def java_package_name(d):
 
 JPN ?= "${@java_package_name(d)}"
 
-DEPENDS_prepend = "virtual/javac-native fastjar-native "
+DEPENDS_prepend = " fastjar-native "
+DEPENDS_prepend_class-target = " virtual/javac-native "
 
 PACKAGES += "${JPN}"