Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update casing of "JabRef" #10345

Closed
wants to merge 4 commits into from
Closed

Update casing of "JabRef" #10345

wants to merge 4 commits into from

Conversation

koppor
Copy link
Member

@koppor koppor commented Sep 7, 2023

Follow-up to #10338.

We either need this fix - or add an explanation in the documentation how to "properly" check out the code to have IntelliJ working (one commit in #10322 does this).

Since I more want to have the guideline "intuitive", I would like to have this change in.

The installer file names and the startup scripts will be all-lowercase now. Which I kind of like. (bin/jabref instead of bin/JabRef)

Update casing of "JabRef"

  • Lowercase "jabref" in scripts and binary names
  • Change vendor to JabRef e.V.
  • Case "mac-package-identifier" to "JabRef"
  • Group macos steps together

Mandatory checks

  • Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
  • Tests created for changes (if applicable)
  • Manually tested changed features in running JabRef (always required)
  • Screenshots added in PR description (for UI changes)
  • Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
  • Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

- Lowercase "jabref" in scripts and binary names
- Change vendor to JabRef e.V.
- Case "mac-package-identifier" to "JabRef"
- Group macos steps together
@koppor
Copy link
Member Author

koppor commented Sep 7, 2023

Maybe, this conflicts with #10340 (JabRef.app vs. jabref.app - to be checked)

@github-actions
Copy link
Contributor

github-actions bot commented Sep 7, 2023

The build of this PR is available at https://builds.jabref.org/pull/10345/merge.

--mac-package-identifier Jabref \
--mac-package-name JabRef \
--mac-package-identifier JabRef \
--mac-package-name "JabRef e.V." \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should go to vendor?

@@ -283,26 +283,26 @@ jobs:
if: steps.checksecrets.outputs.secretspresent == 'YES'
id: gitversion
uses: gittools/actions/gitversion/execute@v0.10.2
- name: Get macOS binaries
- name: Get macos binaries
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is wrong! The casing of macOS is correct official

@Siedlerchr
Copy link
Member

We should discuss implications first

calixtus
calixtus previously approved these changes Sep 7, 2023
@Siedlerchr
Copy link
Member

We should keep the casing as is, this how it looks like in mac:
grafik

@koppor
Copy link
Member Author

koppor commented Sep 8, 2023

We should distinguish

  • Linux: all lower case
  • Mac OS: mixed case
  • Windows: Don't know - mixed case?

#FutureWork

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants