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

Rename packages from net.sf.jabref to org.jabref #1179

Closed
koppor opened this issue Apr 12, 2016 · 2 comments
Closed

Rename packages from net.sf.jabref to org.jabref #1179

koppor opened this issue Apr 12, 2016 · 2 comments
Assignees
Labels
type: code-quality Issues related to code or architecture decisions
Milestone

Comments

@koppor
Copy link
Member

koppor commented Apr 12, 2016

We move away from SourceForge. Thus, the packages should also be renamed, too.

This could make #152 harder, but strengthens that we are independent of sourceforge.

Refs #111

Possibly also reorganize the imports in this change.

@koppor koppor added the type: code-quality Issues related to code or architecture decisions label Apr 12, 2016
@simonharrer
Copy link
Contributor

Downsides

  • as the package of the preferences would change, all old preferences would be lost (maybe something for a major break, e.g., 4.0?)
  • grammar (search, bst) must be changed and regenerated
  • files could go missing as changing the package requires to change the folder structure

@stefan-kolb stefan-kolb added this to the 4.0 milestone May 19, 2016
@lenhard lenhard changed the title [code] Rename packages from net.sf.jabref to org.jabref Rename packages from net.sf.jabref to org.jabref Dec 6, 2016
@koppor koppor self-assigned this Dec 9, 2016
@lenhard lenhard added the jabcon label Feb 10, 2017
@koppor
Copy link
Member Author

koppor commented Feb 16, 2017

Implemented in #2558

@koppor koppor closed this as completed Feb 16, 2017
@koppor koppor removed the jabcon label Feb 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: code-quality Issues related to code or architecture decisions
Projects
None yet
Development

No branches or pull requests

4 participants