Skip to content
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

JAR in source tree #65

Open
ghost opened this issue Jun 13, 2017 · 2 comments
Open

JAR in source tree #65

ghost opened this issue Jun 13, 2017 · 2 comments
Labels

Comments

@ghost
Copy link

ghost commented Jun 13, 2017

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/

@ghost ghost changed the title Compiled JAR in source tree JAR in source tree Jun 13, 2017
@ghost ghost added the bug label Jun 13, 2017
@petermr
Copy link
Member

petermr commented Jun 15, 2017

closed as out out project scope

@petermr petermr closed this as completed Jun 15, 2017
@ghost
Copy link
Author

ghost commented Jun 15, 2017

@petermr wrote:

Closed as out of project scope

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.

@ghost ghost reopened this Jun 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant