I am using Talend Platform for data services 5.2.2 with nexus repository manager.
I have a classpath issue which requires me to edit my route manifest file. In Studio, choosing Edit Route Manifest gives me blank box where the Manifest details should display. This means I can only publish the route to my repository with the classpath issues unresolved. I will prefer to use the ESB conductor as part of the process of deploying my route but looks like this wont work in this case.
I don't want to have to edit the Route manifest directly then drop the kar file into the deploy folder of runtime manually, as this is a very manual process.
Any ideas how to get round this?
The 'Edit Route Manifest' UI should allow you to add any unexpected packages once during design. Something definitely sounds strange if the Manifest details don't show up at all in your Studio.
Is there anything peculiar about the route? For instance, was it originally created in a different version of Talend and imported into your 5.2.2? Also, have you tried creating a basic test route to see if the Manifest details show up for that one?
OK, I think I see what the problem is. In order to include a jar in your Bundle-Classpath, first you need to right click your route and select 'Manage Route Resources'. Add your jar(s) there, and then they should show up as options in your Bundle-Classpath. Each jar will have a checkbox that you will have to check to include the jar.
I see. That jar is probably being included as a part of one or more components you're using in your route. So removing it would likely require creating a custom component by modifying the right one.
Either way, it shouldn't be causing a classpath issue when you deploy. Is there a sharable version of your route that you can export and attach here? Also, are there any modifications you've made to your Runtime?