Closed Bug 648593 Opened 9 years ago Closed 9 years ago

Remove JavaXPCOM from mozilla-central

Categories

(Core Graveyard :: Java to XPCOM Bridge, defect)

x86
macOS
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED
mozilla5

People

(Reporter: benjamin, Assigned: benjamin)

References

Details

Attachments

(1 file)

We are removing JavaXPCOM from mozilla-central. If owners show up, I will help them to get something running in a project repository apart from our main codebase.
Attachment #524685 - Flags: review?(ted.mielczarek)
Comment on attachment 524685 [details] [diff] [review]
Remove JavaXPCOM, rev. 1

> JAVA_BIN_PATH=
> MOZ_ARG_WITH_STRING(java-bin-path,
> [  --with-java-bin-path=dir
>                           Location of Java binaries (java, javac, jar)],
>     JAVA_BIN_PATH=$withval)

Are we still using this somewhere? (Android?)

> 
>-if test `echo "$MOZ_EXTENSIONS" | grep -c java` -ne 0; then
>-    AC_MSG_WARN([java is no longer an extension, use --enable-javaxpcom to enable.])
>-    MOZ_EXTENSIONS=`echo $MOZ_EXTENSIONS | sed -e 's|java||g'`
>-fi

philor already removed this in bug 647647.

> 
>-AC_SUBST(MOZ_JAVAXPCOM)
> AC_SUBST(JAVA_INCLUDE_PATH)

You removed the bits that set JAVA_INCLUDE_PATH up above, probably should remove this (+ the autoconf.mk.in bit as well).
Attachment #524685 - Flags: review?(ted.mielczarek) → review+
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.2
Depends on: 648695
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.