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

Mavenize Ontology as a zip file artifact #7

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

griffbbn
Copy link

I do not know if Mavenization is of general interest, but I have done a minimal set of changes to wrap the ontology files into a Maven artifact. If the changes are adopted, the merge should modify the groupId of the artifact and will have to modify the paths of the repositories in the distributionManagement section of the POM.

@griffbbn griffbbn closed this May 20, 2015
@griffbbn griffbbn reopened this May 20, 2015
@cwacekINV
Copy link

@griffbbn What does making the ontology a Maven artifact achieve? I'm not sure I've actually ever used Maven but my understanding is that it is some sort of build tool.

At first blush I'm not sure it makes sense to include project specific build configs in this repository.

@griffbbn
Copy link
Author

Maven, Gradle, and Ivy all use the same concept for specifying and publishing project dependencies. They allow a project to specify specific versions of external executables, libraries, and data and include and use them without having to install them locally on each developer host or load them into the project repository. You then publish snapshots or releases of your 'artifact' (in this case, the zip file) into the established repository infrastructure and anyone can incorporate it in turn into their project in less than a minute. As shops update their development processes one of these three systems generally seems to be involved. (end of commercial :->)

The ontology doesn't need to be 'built' (unless we want to publish it in several different formats) but we should want to make it easy for someone to use. Publishing it in the existing repository network supports this. I could have done this in Gradle, but I'm more familiar with Maven at the moment and the result is usable by all three systems in any case.

Feel free to incorporate it into the repo or not. It doesn't eliminate someone just cloning the repository and using it that way...

@griffbbn griffbbn closed this May 22, 2015
@griffbbn griffbbn reopened this May 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants