Samir Batla
Do you have any plans for hosting a maven repo for all the stardog libraries? Right now, its very difficult to compile the java library stardog-spring. With Gradle, it does compile but fails to export the classes as a jar file. I think the lib folder in stardog has spring 2.x version, Gradle build file ignores these jar files, still the build fails. It will save lot of time for the developers if you create a maven repo.
Kendall Clark
Cheers,
Do you have any plans for hosting a maven repo for all the stardog libraries? Right now, its very difficult to compile the java library stardog-spring. With Gradle, it does compile but fails to export the classes as a jar file. I think the lib folder in stardog has spring 2.x version, Gradle build file ignores these jar files, still the build fails. It will save lot of time for the developers if you create a maven repo.
--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+u...@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en
Al Baker
You can drop the stardog-1.2.x/lib/org.springframework folder with the 2.5.6 jars. Despite all variants of exclude clauses, Gradle still appears to pick it up and cache it. I have a follow up with the Gradle team on this behavior of the fileTree API which finds/pulls in everything.
Per Kendall's note, this will be fixed in the 2.0 release where the Stardog client dependencies will be first class citizens and all build tools w/ dependency management (Ant+Ivy, Maven, Gradle, etc) will handle them appropriately.
Al