Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provided dependencies management #158

Closed
oscerd opened this issue Apr 28, 2020 · 1 comment
Closed

Provided dependencies management #158

oscerd opened this issue Apr 28, 2020 · 1 comment
Assignees
@valdar

Comments

@oscerd
Copy link
Contributor

oscerd commented Apr 28, 2020

There are cases in which a component declare a provided dependency, like for example camel-sjms2 for geronimo specs, those deps are needed if you unpack your connector in the plugin.path location, this sound similar for ActiveMQConnectionFactory, which we use in some examples but comes from Activemq jars.
@oscerd
Copy link
Contributor Author

oscerd commented Apr 28, 2020

Looking at it better with @valdar
We are declaring activemq-client as test dependency in the parent/pom, so in the connector using the activemq-client, we have the dep as test and it's not included (with all the transitive deps) in the packages generated during the build

valdar added a commit to valdar/camel-kafka-connector that referenced this issue Apr 28, 2020
@valdar
camel-kafka-connector-generator-maven-plugin: Implemented the possibi…
7c6f8cc 
…lity to specify a scope in addeditional depencendices fix apache#158
@valdar valdar closed this as completed in 6291090 Apr 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@valdar valdar

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@valdar @oscerd