| Summary: | java/intellij-ultimate: update to 2019.1 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Alex Dupre <ale> | ||||
| Component: | Individual Port(s) | Assignee: | Alex Dupre <ale> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | andoriyu | ||||
| Priority: | --- | Flags: | andoriyu:
maintainer-feedback+
|
||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Comment on attachment 203215 [details] Patch to update intellij-ultimate to 2091.1 > deaIU-${PORTVERSION}-no-jbr > jbr is that right? A commit references this bug: Author: ale Date: Fri Mar 29 09:07:23 UTC 2019 New revision: 497077 URL: https://svnweb.freebsd.org/changeset/ports/497077 Log: Update to 2019.1 release. PR: 236852 Submitted by: ale Approved by: maintainer Changes: head/java/intellij-ultimate/Makefile head/java/intellij-ultimate/distinfo head/java/intellij-ultimate/pkg-plist Yes, it's correct, there is a new trend of forking the jdk to apply a couple of patches that should have been submitted upstream. |
Created attachment 203215 [details] Patch to update intellij-ultimate to 2091.1