Andrea Cosentino

I think it's really hard to say something without looking at the connector structure. By the way, it makes sense to create a completely new connector instead of extending a...

Not sure about this particular usecase. Probably it's something in the core.

> Core is added in common package. Yes, I meant something in the core checking for a specific package like org.apache.camel...

> So. if I dont change the package and add my custom code it works. Is there anything special needs to be pulled from the build plan? No.

> Does those autogenerated properties and resources (in generated packages) make any difference? No, they are related to the underline camel component. I don't know what is in your extended...

Ok, so you're still using the basic feature of the connector, this means you're still using the component. My suggestion for the moment is to maintain the package name and...

> @oscerd : Thanks you!! It was an indeed the issue with the package name. Once I moved back all common code to connector package (org.apche.camel) it worked. If you...

So we may have a persisted solution.

We have the same problem as before, we cannot include the lib and we cannot build in this way. We should remove even the other example, because we cannot have...

We need to find a way to fully build, so we need to update the modules list and check.