Maven knime-core with knime-cloud

biolekm · January 15, 2021, 12:52pm

Hi,

my main goal is to create own extension that is very similar to AWS Authentication node, because I dont want to login to AWS cloud but to my S3 storage (openIO). I setup the development ide and I have no problem to create my own extension without any inheritance. The problem occurs with inheritance. I have to download two projects knime-core and knime-cloude. In the knime-sdk setup repository on github I found this part

My errors in the Eclipse are

. Any proposed solution will be helpful.

gab1one · January 15, 2021, 12:55pm

Hi @biolekm

do you have git-lfs installed? The errors look like the library files could not be located, which usually indicates that git-lfs did not download them.

best,
Gabriel

biolekm · January 15, 2021, 1:16pm

Hi Gabriel, I installed git-lfs and remove the knime-cloud. I think the main problem is in pom.xml in knime-core.

This has to be solved first (in my opinion). pom.xml in kmine-cloud is related to knime-core pom.xml

gab1one · January 15, 2021, 3:53pm

The pom.xml error is
If you want to develop your own extension, then you don’t ever need to build knime-core itself with maven. Thus, you can just remove the knime-core parent project from your workspace, or remove the maven nature from that project.

The maven build of these projects depends on an internal parent pom, that we can’t share as it references non-public repositories. If you do want to build knime-core with maven you need to adapt the root pom (the one in knime-core) to be like the one in the public community project template:

github.com

knime-community/community-repository-template/blob/master/pom.xml

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

	<modelVersion>4.0.0</modelVersion>

	<groupId>org.knime</groupId>
	<artifactId>community-repository-template</artifactId>
	<version>${revision}${changelist}</version>
	<packaging>pom</packaging>

	<properties>
		<revision>1.0.0</revision>
		<changelist>-SNAPSHOT</changelist>
		<knime.version>4.3</knime.version>
		<tycho.version>1.5.1</tycho.version>
		<tycho.extras.version>${tycho.version}</tycho.extras.version>
	</properties>

	<!-- List the modules of your project here -->

This file has been truncated. show original

Just copy that pom into your clone of knime core and adapt the modules section. That should get you started. If you got any more questions, please reach out to us.

best,
Gabriel

biolekm · January 19, 2021, 10:07am

thank you, that helped me with knime-core then I registered API Baselines and import knime-cloud which includes aws authentication (this node I want to recreate to have own url not only to aws cloud). The pom.xml in kmine-cloude has no error related with API Baselines but there is and error with pom.xml

Project build error: Non-resolvable parent POM for org.knime:knime-cloud:${revision}${changelist}: Failure to transfer org.knime.maven:ap.parent:pom:4.4.0 from ${knime.core.p2} was cached in the local repository, resolution will not be reattempted until the update interval of p2-knime-
core has elapsed or updates are forced. Original error: Could not transfer artifact org.knime.maven:ap.parent:pom:4.4.0 from/to p2-knime-core (${knime.core.p2}): Cannot access ${knime.core.p2} with type p2 using the available connector factories: AetherRepositoryConnectorFactory,
BasicRepositoryConnectorFactory and ‘parent.relativePath’ points at wrong local POM

Because of this error mainly aws.fiulehandling can not use any library for ex an error:

Project ‘org.knime.cloud.aws.filehandling’ is missing required library: ‘libs/protocol-core-2.15.14.jar’

Is there any recommendation how to solve it? Thank you, Martin

gab1one · January 19, 2021, 3:00pm

That is a file that should exist in the repository, if it does not then something with the checkout went wrong.

To fix the pom errors you need to either set the parent pom to the one you created, or just remove the maven nature from the projects.

best,
Gabriel

system · September 22, 2021, 10:19am

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.