docs: remove obsolete edit in domain.xml
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- java
- Domain
- documentation
Research direction
Open doc/sphinx-guides/source/installation/prerequisites.rst and inspect line 74, where the obsolete domain.xml edit is described. Remove that line and check the surrounding installation guidance for continuity; done means the documentation no longer recommends changing -client to -server.
Written by the indexing model from the issue text.
Description
In our documentation we recommend changing -client to -server in domain.xml, but the file now defaults to -server. I've verified this, but can't find a corresponding commit in the Payara repo.
In any case, we should be able to safely remove line 74.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 569
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 26
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IQSS/dataverse
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
IQSS/dataverse#12818 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Release Size: 30
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
docs: remove obsolete chown command and follow-up notePossibly taken @donsizemore claimed this 15 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
IQSS/dataverse#12764 · 1 reaction ·
Maintainers usually reply within 1 day
-
S3SubmitToArchiveCommand: temporary bag files not deleted after upload, causing disk space leakOpenType: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
IQSS/dataverse#12736 · 1 comment ·
Maintainers usually reply within 1 day
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
IQSS/dataverse#12735 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
netshot-net/Netshot#413 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
scylladb/scylla-cdc-source-connector#350 ·
Maintainers usually reply within 1 day
-
agent:working documentation enhancement go:build lane:needs-decision
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Sanne/incus-spawn#1435 · 3 comments ·
Maintainers usually reply within 1 day
-
area:shuffle bug priority:high requires-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/datafusion-comet#7062 ·
Maintainers usually reply within 1 day
-
help wanted testing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
antonyrag/ragleap-core#786 ·
Maintainers usually reply within 1 day