I’m trying to update a node by editing it on Eclipse and then exporting it to save it in KNIME’S dropins directory but the changes are not being reflected on KNIME.
I’ve tried multiples ways and I’ve also read and tried some of the community’s similar posts:
Tried exporting it as a feature and update site project to install in KNIME.
The steps that you tried look like they should lead to results, but I think there is some information missing that should tell us what is going on.
Can you tell us which node you want to modify, and maybe what is the missing functionality that you are trying to add?
Directly modifying a single node is unlikely to work as expected, you should instead create a distinct new node with a different ID to prevent confusion.
Did you enable debug logs in AP and looked for errors during the startup?
I see that you already created an update site project, does your extension install successfully?
I guess you already successfully tested the node in debug mode?
It’s a customized node that works well, it basically downloads data from SAP, but a small change such as changing the node’s description (the xml file) is not working because it does not show the changes.
If I add a new node to the extension, it is not recognizing this change either.
I’m not getting any errors during startup.
The extension is installing successfully, but the nodes are from the previous version I had. Let’s say If the first version had the description “Hello” and the new version I’m trying to test says “Hello Bye”, after installing the latest version it still says “Hello”.
Yes, weird thing is there are no errors showing up.
Just a couple of weeks ago it was working fine and I was able to update other customized nodes, I haven’t changed the configuration from any of the programs, so I don’t know what might have changed within Eclipse or KNIME so that no new changes are being recognized.
If the build works correctly, it should create a new version of your extension when you run the build.
I recommend you to setup your project to run with maven, take a look at this template project: GitHub - knime-community/community-repository-template
If you then build with mvn clean verify you should get a new version everytime there are changes.
I found the solution to my problem, I think that the project I was trying to export as a deployable plugin had some corrupt files or maybe there were some issues with the path where it was located.
I created a new project (same scr) on a totally different directory and now it is reflecting the changes when I open it in KNIME. I’m not sure why this was the solution, but this may be helpful as another option for anyone else that encounter this issue.