Yes you are right. I guess it was not deeply tested. We have deployed the channel_iface_impl_stub to the public repository. Also you will have to include the aduna repository. Here is the pom snippet that will help you:
<repositories> <repository> <id>aduna</id> <name>Aduna Main Repository</name> <url>http://repo.aduna-software.org/maven2/releases</url> </repository> <repository> <id>public</id> <name>Ontotext Public</name> <url>http://maven.ontotext.com/archiva/repository/public</url> </repository> </repositories> Please write if you still have problems. We tested it with a clean local repository and everything should be OK. All the best Philip On Nov 12, 2010, at 5:18 PM, heapifyman wrote: > > Ah, one more thing: > > I assume the org.openrdf.util.rmirouting.channel_iface_impl_stub > dependency cannot be excluded? > I can add this manually to my repo but for ease of use it would be good > to make this available in the public repo or also mention in the > documentation that one has to deploy it manually. > > Best regards, > Philip > > Am 12.11.2010 15:54, schrieb Philip Alexiev @ Ontotext: >> Hi Philip, >> >> This is the case. platform-api is needed by kim-api, only for a part that >> is still experimental (the jms part). This means that you can go without it. >> So you can exclude it from the dependency. In your pom you can add kim-api >> like this: >> >> <dependency> >> <groupId>com.ontotext.kim</groupId> >> <artifactId>kim-api</artifactId> >> <version>3.0-RC4</version> >> <exclusions> >> <exclusion> >> <groupId>com.ontotext</groupId> >> <artifactId>platform-api</artifactId> >> </exclusion> >> </exclusions> >> </dependency> >> >> This will get kim-api without platform-api. And you will have no problems >> compiling and running your client, as you don't actually use the JMS part. >> >> Apologies for the unclarity. We will update the documentation to reflect our >> conversation. Thank you for your patience. >> >> All the best, >> Philip >> >> >> On Nov 12, 2010, at 3:02 PM, heapifyman wrote: >> >>> Am 12.11.2010 11:59, schrieb Philip Alexiev @ Ontotext: >>>> Hi >>> >>> Hello, >>> >>>> >>>> You can add an option to the platform-api dependency in the pom: >>>> >>>> <scope>optional</scope> >>> >>> I'm not sure I understand. I only have kim-api version 3.0-RC4 as a >>> dependency in my pom and the public ontotext maven repository as repository: >>> >>> <dependency> >>> <groupId>com.ontotext.kim</groupId> >>> <artifactId>kim-api</artifactId> >>> <version>3.0-RC4</version> >>> </dependency> >>> >>> <repository> >>> <id>repo-ontotext</id> >>> <name>Ontotext Maven Repository</name> >>> <url>http://maven.ontotext.com/archiva/repository/public/</url> >>> <snapshots> >>> <enabled>false</enabled> >>> </snapshots> >>> </repository> >>> >>> So the kim-api jar and pom are automatically downloaded by maven from there. >>> >>> But the kim-api pom has a dependency for com.ontotext.platform-api >>> version 0.6 defined but platform-api is not in above listed public >>> repository. I can take the platform-api jar from the kim server >>> distribution zip and add it manually to my local maven repository. >>> But platform-api has as parent pom referenced: com.ontotext.platform >>> version 0.6 >>> >>> This is neither in the public maven repository nor in the distribution >>> zip file and cannot be resolved by maven. >>> >>> Long story short, I believe you have to declare the platform-api >>> dependency in kim-api as optional or provide both platform-api and its >>> parent platform in your public maven repo. >>> >>> Or maybe I misunderstood something. >>> >>> Best, >>> Philip >>> >>>> >>>> This will stop maven from trying to download it. >>>> >>>> We will see which is the best way to handle this in our repository. >>>> >>>> hth, >>>> Philip >>>> >>>> On Nov 11, 2010, at 7:24 PM, heapifyman wrote: >>>> >>>>> >>>>> Good evening everyone. >>>>> >>>>> I have a little problem trying to use the maven artefacts for the KIM >>>>> Java RMI API as is suggested to use here: >>>>> http://ontotext.com/kim/doc/KimDocs-3.0-EN/KIMJavaRMIAPI.html >>>>> >>>>> The first problem was, that the kim-api depends on >>>>> com.ontotext.platform-api, which is not available in the public maven >>>>> repo. I had to extract that from the downloaded KIM platform zip file >>>>> and install it manually in my maven repo (which is artifactory). >>>>> >>>>> Next problem is: >>>>> platform-api in turn includes "com.ontotext.platform" as its parent. >>>>> Unfortunately, I cannot find this artefact in any of the public maven >>>>> repositories nor in the KIM platform zip file. >>>>> >>>>> Thus my maven build fails because the parent pom cannot be resolved. >>>>> >>>>> I'd appreciate any tips about how to proceed? >>>>> >>>>> Best regards. >>>>> >>>>> P.S.: My recommendation would be that the kim-api's dependencies should >>>>> be available in the public maven repository. Otherwise it does not make >>>>> much sense to provide instructions like: >>>>> "maven users can just reference the kim-api artifact from our public >>>>> repository" >>>>> in the documentation. >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Kim-discussion mailing list >>>>> [email protected] >>>>> http://ontotext.com/mailman/listinfo/kim-discussion >>>> >>> >>> >> > >
_______________________________________________ Kim-discussion mailing list [email protected] http://ontotext.com/mailman/listinfo/kim-discussion
