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
Refactor tag importers into a single class #143
Comments
We decided to integrate legacy tag importer into the existing tag importer to avoid this. |
kaklakariada
changed the title
Allow configuring importers
Refactor tag importers into a single class
Aug 2, 2018
kaklakariada
added a commit
that referenced
this issue
Aug 2, 2018
kaklakariada
added a commit
that referenced
this issue
Aug 2, 2018
kaklakariada
added a commit
that referenced
this issue
Aug 3, 2018
kaklakariada
added a commit
that referenced
this issue
Aug 3, 2018
kaklakariada
added a commit
that referenced
this issue
Aug 3, 2018
kaklakariada
added a commit
that referenced
this issue
Aug 3, 2018
kaklakariada
added a commit
that referenced
this issue
Aug 3, 2018
Implemented in #167 |
redcatbear
pushed a commit
that referenced
this issue
Sep 14, 2018
Story/#143 unify short & long tag importer
Merged
kaklakariada
added a commit
that referenced
this issue
Nov 11, 2018
kaklakariada
added a commit
that referenced
this issue
Nov 11, 2018
#143: Fetch git history to provide sonar blame information
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When importing code tags from
*.java
files using the legacy tag importer the import fails because the 'normal' tag importer also uses*.java
.Describe the solution you'd like
A solution would be to allow configuring each importer for which files it is responsible.
Describe alternatives you've considered
Another option would be to order the importers by priority (giving the legacy tag importer higher priority) and use the first one without checking the others.
The text was updated successfully, but these errors were encountered: