I faced a problem that some KNIME extensions raised a Maven error. After some investigations, I found that the problem is related to the conda environment yml files. Namely, If there is any pip package in a yml file, it fails every time.
The env files are attached. There are indeed derived from the mock extension, provided by KNIME team, the only difference is that my_conda_env_ok.yml.txt (206 Bytes) my_conda_env_failed.yml.txt (227 Bytes)
that could be due to an older version of your bundling environment, if named as in the tutorial, that is knime-ext-bundling.
Could you… conda activate knime-ext-bundling conda list knime
and post the version of knime-extension-bundling?
# Name Version Build Channel
knime-extension-bundling 4.7.0 4 knime
If it differs from the posted example here, then please update it to the latest (confusing, yes: the environment for bundling must be the latest one to support pip dependencies and thus is of version 4.7)
Update it for example via conda update knime-extension-bundling -c knime -c conda-forge
Thanks for your advise! Unfortunately, upgrading to 4.7 does not help. The issue is the same
# packages in environment at /home/sergeyadmin/miniconda3/envs/knime-ext-bundling: │ File "/home/sergeyadmin/miniconda3/envs/knime-ext-bundling/bin/build_python_extension.py", line 363
# │, in _run_maven_build
# Name Version Build Channel │ raise RuntimeError("Maven build failed.")
knime-extension-bundling 4.7.0 4 knime
One is a library issue, which should be resolved in the nightly version of knime-extension-bundling, please try this nightly package for your bundling environment:
The other is that in your example numpy is already included in the conda dependencies (i.e. in knime-python-base). If you specify the pip version of numpy for example to numpy==1.10, it should be put down as an additional pip dependency. As this is in no way easy to see, I filed a ticket for that (AP-20308).
Could you these two things out and tell me whether that worked?
Thanks!