Bug 237372 - [NEW PORT] textproc/elasticsearch7: Full-text search engine for Java
Summary: [NEW PORT] textproc/elasticsearch7: Full-text search engine for Java
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs mailing list
URL:
Keywords: feature, needs-qa
Depends on:
Blocks:
 
Reported: 2019-04-18 23:01 UTC by rlwestlund
Modified: 2019-09-17 11:42 UTC (History)
3 users (show)

See Also:


Attachments
Shar archive for the new port (11.88 KB, text/plain)
2019-04-18 23:01 UTC, rlwestlund
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description rlwestlund 2019-04-18 23:01:48 UTC
Created attachment 203777 [details]
Shar archive for the new port

Elasticsearch6 has a port, but Elasticsearch7 is out now. I mostly copied from textproc/elasticsearch6 and made the obvious changes, so I might have missed something; although I did test it and it seems to work.
Comment 1 rlwestlund 2019-04-21 15:02:40 UTC
Is the maintainer-feedback flag never supposed to be used for new port proposals, then? I thought it would be reasonable to set it since feld@freebsd.org was listed as the maintainer for elasticsearch6.

Also, I noticed that when you chaged the title you took out the [patch] thing. According to https://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/pr-writing.html I'm supposed to put that in the title if I have a patch. Is my patch bad? Did I submit it wrong?
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2019-04-21 15:12:21 UTC
(In reply to rlwestlund from comment #1)

Since new ports don't exist in the tree yet, they don't have a maintainer.

Also, feld@ was CC'd, so using the flag wasn't necessary, but it was an appropriate person to CC.

On [tags] in summaries, you're fine, the docs are out of date, our/my fault :)

You seem really interested in how things work and doing the right thing. I'm more than happy to go over a few cheetsheats with you to level up your contributions and provide clarity on the best way to submit issues. Either hit me up preferably on IRC (freenode: #freebsd-ports), or email me :)