-
Notifications
You must be signed in to change notification settings - Fork 1
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
improve SCM detection in Maven mode #43
Comments
I've implemented this and looked at what URLs were being acquired now -- from my understanding, the core matter here is that, as per #8 , we need to add support for non-GitHub repositories; most of the repositories do seem to at least point to an existing repo, but they aren't GitHub ones (e.g., gitbox, svn). I'm assuming that for this, we should compile a list of known/relevant source code repository websites |
Plus some URLs could be a link to the "project page" rather than source code repository so you will also need a way to differentiate between them. |
I'd argue that that's already the case though, no? Which is fair, of course, just trying to understand if it's a new issue arising |
I just thought I should mention in case you were not aware. The AROMA paper mentions that they find URLs but sometimes it is just project pages like documentation. |
in Maven, the source repo can be filled in:
Source: Section 3.2 of AROMA: Automatic Reproduction of Maven Artifacts
The text was updated successfully, but these errors were encountered: