jira-importer commented on issue #1160: URL: https://github.com/apache/maven-scm/issues/1160#issuecomment-2964649293
**[Alex Harui](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aharui)** commented I am not a Maven expert, but I agree it isn't compliant with the standard conventions as I understand them. However, it looks like Maven does allow some variations: you can change the output and source directory names, for example. In this case, I think the patch allows for a similar variation: instead of requiring one released project per repo, it allows for some small projects to be collected in a repo. One of the projects in our code base contains only two .java files (the other has 8 .java files) so having each project in its own repo seems like too much overhead, and complicates the non-Maven legacy build process we want to continue to support. Also, I thought of this as a mere bug fix in JGit. On my local machine I added a similar test to gitexe's GitCheckInCommandTest and it worked there. It seems to only be a problem in JGit. I will try to get the patches into a PR by the weekend. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
