Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I want to develop a multi-platform game using libGdx (for Desktop and Android).To share my work with some friends, I created a GitHub repository.
In ecplise, I have 3 different projects :
MyProject-core (most of the game)
MyProject-desktop (specific desktop code)
MyProject-android (specific android code)
I want to push them in my Github repository in 3 different folders.
Basicaly, I want my repository to look like this :
MyRepository
/core/
/desktop/
/android/
README.md
LICENCE.md
My question is, Should I use 3 different local git repositories, or should I just use 1 large repo?
It seems like you may want to use Git submodules.
You can have 1 main repo, with each of the other folders being a submodule, which is just a separate repo you pull down on checkout.
When pulling down your main repo you would do git submodule init which pulls down the other 3 repos/submodules.
The benefit of doing this instead of just having 1 repo with these 3 folders is that each repo with different codebases is essentially its own project, with its own language and set of issues.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
Recently I have been trying to figure out how to publish my ScaleNumberPicker Android library from GitHub.
I read articles about publishing to Jitpack, GitHub Packages and Maven Central, but I found it confusing.
What is the difference between these different package repositories, and which one is the best for Android Studio? And how do I publish? Do I need to create a release first on GitHub? And after publishing, can I modify the README.md file on my GitHub repository to add the usage instructions?
JitPack pulls the source from your GitHub repo and builds it (when the first user uses the lib).
For Maven Central and GitHub Packages, you build and upload your own artifacts.
I'd say, the simplest way is JitPack.
Follow the docs to publish the lib. (Follow the Guide to Android)
After adding a release, you still can edit the README, and you can continue to work on the lib.
If you want to publish a new version, just create a new release and update the README.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I am considering forking a long lived but seemingly abandoned OSS project. In my updated pom.xml, should I include the developers of original work to give them credit since they are responsible for the 99% of the code, or just new maintainers, as the Maven POM Reference would imply:
All projects consist of files that were created, at some time, by a
person. Like the other systems that surround a project, so to do the
people involved with a project have a stake in the project. Developers
are presumably members of the project's core development. Note that,
although an organization may have many developers (programmers) as
members, it is not good form to list them all as developers, but only
those who are immediately responsible for the code. A good rule of
thumb is, if the person should not be contacted about the project,
they do not need to be listed here.
It is just the pom.xml file. Do like it is written in the rule of thumb.
For a branch or a fork the history and dependencies or codebase should be clarified elsewhere, e.g. git, GitHub.com, GitLab.com, a project page, the docs...
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I just want to create several Spring-Boot applications. But I want to create them all in the same project in parallel. At the end, when I'm building all the stuff via maven just one jar-file should be created. One Jar file which is including all applications.
(Optional: not sure if that is even possible) Each project should have its own pom file and artifact id.
To start a particular application of this one jar file, I want to add some profiles (or something similar, special parameter) so that I can simply start a subproject by given parameter or profile.
I just started with the answer i already got. Made the subprojects, but here every subproject is created in an own jar file. That is exactly not what i want ;).
You have an idea?
Tanks a lot in advance.
ps: I'm using IntelliJ IDEA
Yes, you can do it.
For this you can build different individual spring-boot project and accumulate all project into one parent project. Then, you can use your every project individually also can use as a parent jar file.
For more details multi-module-maven spring-boot-multiple-modules
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I need to create remote Github repository using java (Using my credentials) and I need to push some code to that repo.
I saw some examples using JGit and some other references like
http://www.codeaffine.com/2015/11/30/jgit-clone-repository/ and https://github.com/kohsuke/github-api.
But I'm not able to understand fully.
// ------------ create the directory ---------
try (Git git = Git.init().setDirectory(localPath).call()) {
System.out.println("Having repository: " + git.getRepository().getDirectory());
}
I tried this one. I can only create repo in local.
So How can I push these changes to remote.
Thanks.
If you need to create a repository on GitHub, you need to use something that talks to the GitHub API like the lib of Kohsuke you linked to, or you need to talk to the API directly if you prefer.
If you also want to create a local Git repostory and push that to the remote, you additionally need to use e. g. JGit to either clone the repository you created or create a new repository, set the remote configuration to the repo created on GitHub and then push.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I wish to create an internal maven repository on my network. Can anyone show me how to have this done ?
Check out these open-source managers:
Nexus
Archiva
Artifactory
Reposilite
Full list (with also commercial versions):
Repository Management Software
Have a look at Maven Repository Managers such as Nexus: http://maven.apache.org/repository-management.html
Also have a look at how to configure your settings file:
http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html
You are thinking of a deploying a Nexus Repository.