[Bug 243623] devel/maven: Requires openjdk8 even if a newer JDK is installed

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Jan 26 20:48:21 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243623

            Bug ID: 243623
           Summary: devel/maven: Requires openjdk8 even if a newer JDK is
                    installed
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: rleigh at codelibre.net

Now that the ports tree includes these additional JDKs:

java/openjdk11
java/openjdk12
java/openjdk13

it would be nice if maven would not have a hard dependency upon openjdk8.  It
wants to install it even though openjdk11 is already installed.  I think this
stems from Mk/bsd.java.mk, but I'm not sure why?  The ordering of
__JAVA_PORTS_ALL?

% sudo pkg info | grep jdk
openjdk11-11.0.6+10.1          Java Development Kit 11

% sudo pkg install maven
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 2 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        maven: 3.6.3
        openjdk8: 8.242.07.1

Number of packages to be installed: 2

The process will require 201 MiB more space.
9 MiB to be downloaded.

If this is not maven-specific and applies equally to other Java packages with a
JDK dependency, it could be reassigned to a more appropriate package.

Now that JDK11 is the current LTS release of Java, would it be time to make it
the default/preferred JDK?  Or are there any issues which preclude doing that?

Does pkg support a Debian-style Provides/virtual package type of dependency
which could permit any of these JDKs to "Provide: javac" and be substitutable
for one another?

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list