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

Use standardized project structure #110

Closed
HEdingfield opened this issue Aug 6, 2018 · 6 comments
Closed

Use standardized project structure #110

HEdingfield opened this issue Aug 6, 2018 · 6 comments

Comments

@HEdingfield
Copy link
Contributor

I've been having trouble getting the Help button I'm working on to call up the config documentation txt file. It would help out a lot if we moved to a more standard directory structure like that used by Apache's Maven project. Here's a simple example of the layout in action.

@tarheel @moldover sound reasonable?

@HEdingfield HEdingfield self-assigned this Aug 6, 2018
@HEdingfield
Copy link
Contributor Author

I was researching Maven more, and it seems like migrating to this structure will allow us to build out tests, manage dependencies, and deploy more efficiently. It also integrates well with IntelliJ. Check out the quick video here.

@CalebKleppner
Copy link
Collaborator

This is above my pay grade, but if the 3 of you think this makes sense, I am fully supportive.

@HEdingfield
Copy link
Contributor Author

If we convert to Maven, we can probably delete the libs directory.

@HEdingfield
Copy link
Contributor Author

#239 is related, since we discuss migrating everything to Gradle.

@tarheel
Copy link
Contributor

tarheel commented May 8, 2019

Converting to Maven/Gradle to own the libs.

@HEdingfield
Copy link
Contributor Author

Gradle migration complete with #272.

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

No branches or pull requests

4 participants