How to avoid adding dependencies into Bundle-Classpath in TOS 7.0.1 ?

Four Stars

How to avoid adding dependencies into Bundle-Classpath in TOS 7.0.1 ?

Hello! 

I'm building a route as a *.kar package and all dependencies, added by cConfig, are automatically packaged into *.kar file and added into Bundle-Classpath header of bundle manifest.

How can I avoid this or manage this by myself?

In 6.*.* releases of TOS dependencies, added by cConfig were NOT added into kar file.

Thanks!

 

p.s.: this setting not helps:

Снимок.JPG

 

Moderator

Re: How to avoid adding dependencies into Bundle-Classpath in TOS 7.0.1 ?

Hello,

Could you please have a look at this jira issue:https://jira.talendforge.org/browse/TESB-20563 to see if it is what you are looking for?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Four Stars

Re: How to avoid adding dependencies into Bundle-Classpath in TOS 7.0.1 ?

Hello!

Yes, it seems that the bug TESB-20563 was a useful feature at some degree because for now, in TOS 7.0.1, dependencies are ALWAYS added into Bundle-ClassPath and Private-Package despite of this settings:

01.JPG

Moderator

Re: How to avoid adding dependencies into Bundle-Classpath in TOS 7.0.1 ?

Hello,

Does this issue also repro on other talend open studio for ESB build version? V 6.5.1, V 6.4.1?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Four Stars

Re: How to avoid adding dependencies into Bundle-Classpath in TOS 7.0.1 ?

Hello!

In 6.5.1 this feature works as it should and as expected.

In 6.4.1 it works as it described in https://jira.talendforge.org/browse/TESB-20563.

In 7.0.1 it works as I said earlier.

 

Tutorial

Introduction to Talend Open Studio for Data Integration.

Definitive Guide to Data Integration

Practical steps to developing your data integration strategy.

Definitive Guide to Data Quality

Create systems and workflow to manage clean data ingestion and data transformation.