You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is still some Git- and Maven-related groundwork to be done (and I know it is not entirely Tilburg-specific and may have to wait), but in future, ContentMine should aim to use GitHub's "Releases" mechanism for publishing binaries, instead of polluting the source code repositories:
I'm guessing that by "project scope" you are referring to the Tilburg project?
This issue was created within the Tilburg project, because it was for that project that this JAR was (unfortunately) committed to that branch. However, this issue will affect anyone who uses that branch of norma's history in the future, i.e. beyond the life of the Tilburg project. Its scope is therefore not restricted to the Tilburg project.
If you would prefer not to address this within the Tilburg project, due to the project deadline, that is understandable; but the semantically correct manoeuvre in that case would be to remove the issue from the Tilburg project board, not to close the issue. I have now performed this manoeuvre.
https://github.com/petermr/norma/tree/master/target contains a compiled binary.
There is still some Git- and Maven-related groundwork to be done (and I know it is not entirely Tilburg-specific and may have to wait), but in future, ContentMine should aim to use GitHub's "Releases" mechanism for publishing binaries, instead of polluting the source code repositories:
https://help.github.com/articles/about-releases/
The text was updated successfully, but these errors were encountered: