Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

According to last message in google group, I created poms in each artifact and allowed inclusion of non-maven dependencies #66

Merged
merged 1 commit into from Nov 18, 2011

Conversation

Projects
None yet
2 participants

In these poms, there are two or three details to notice
1 - There is a dependency to JDK tools in Empire-core due to
EmpireAnnotationProvider. This is mandatory, but unfortunate.
2 - As Empire uses some clarkparsia utilities classes (mainly in
Empire-core, but also in Empire-fourstore) that cannot be found in any
maven repository, I had to use local repository trick to put them in the
lib folder under a meaningful name, so don't be scared if they have
moved. Besides, if one want to change them version, the following
command line has to be used :
mvn install:install-file
-Dfile=lib\clark-parsia\cp-common-fourstore-0.3.1.jar
-DgroupId=com.clarkparsia
-DartifactId=cp-common-fourstore -Dversion=0.3.1 -Dpackaging=jar
-DlocalRepositoryPath=lib

Not really intuitive, but, well, it would be better creating a
github-stored repository (like said here :
http://cemerick.com/2010/08/24/hosting-maven-repos-on-github/)

3 - To maskerade those libs, I use the maven-shade-plugin to change the
official jars to include those dependencies. Besides, I also create a
"onejar" version including all dependencies.
4 - all that is untested (mainly because I didn't wanted to
change the test artifact -which would have better been replaced by test
folder in each artifact).
5 - openrdf dependencies were "optimized" - or stripped down to their
lowest common denominators.

Added all poms required by maven for compile.
In these poms, there are two or three details to notice 
1 - There is a dependency to JDK tools in Empire-core due to
EmpireAnnotationProvider. This is mandatory, but unfortunate.
2 - As Empire uses some clarkparsia utilities classes (mainly in
Empire-core, but also in Empire-fourstore) that cannot be found in any
maven repository, I had to use local repository trick to put them in the
lib folder under a meaningful name, so don't be scared if they have
moved. Besides, if one want to change them version, the following
command line has to be used :
mvn install:install-file
 -Dfile=lib\clark-parsia\cp-common-fourstore-0.3.1.jar
-DgroupId=com.clarkparsia
 -DartifactId=cp-common-fourstore -Dversion=0.3.1 -Dpackaging=jar
-DlocalRepositoryPath=lib

Not really intuitive, but, well, it would be better creating a
github-stored repository (like said here :
http://cemerick.com/2010/08/24/hosting-maven-repos-on-github/)

3 - To maskerade those libs, I use the maven-shade-plugin to change the
official jars to include those dependencies. Besides, I also create a
"onejar" version including all dependencies.
4 - all that is untested (mainly because I didn't wanted to
change the test artifact -which would have better been replaced by test
folder in each artifact).
5 - openrdf dependencies were "optimized" - or stripped down to their
lowest common denominators.

@mhgrove mhgrove merged commit 7507d34 into mhgrove:master Nov 18, 2011

Owner

mhgrove commented Nov 18, 2011

merged into the head revision, thanks for contributing this. I had to make a few tweaks because i had changes locally that changed the cp utils & openrdf jars that went into the final 0.7 commit. you might want to pull head and make sure i correctly maintained the maven bits. if not, send me the fix or post to the list and let me know and i'll resolve it.

thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment