[
https://issues.apache.org/jira/browse/CAMEL-19108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19108:
--------------------------------
Description:
More work from CAMEL-19093
If you have a local .jar in the folder (no maven dependency). For example a
JDBC driver etc or custom JAR. Then we should during export
- create a lib folder *DONE*
- copy JARs to lib folder *DONE*
- add <dependency> in pom.xml that refer to local file *DONE*
- scan the JAR in case its a maven built as then it contains GAV we can use as
placeholder in <dependency> *DONE*
- gradle build ??? *DONE*
was:
More work from CAMEL-19093
If you have a local .jar in the folder (no maven dependency). For example a
JDBC driver etc or custom JAR. Then we should during export
- create a lib folder *DONE*
- copy JARs to lib folder *DONE*
- add <dependency> in pom.xml that refer to local file *DONE*
- scan the JAR in case its a maven built as then it contains GAV we can use as
placeholder in <dependency> *DONE*
- gradle build ???
> camel-jbang - Export with local JAR should include the JAR in lib folder and
> add as dependency
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-19108
> URL: https://issues.apache.org/jira/browse/CAMEL-19108
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 3.20.4, 3.21.0, 4.0-M3, 4.0
>
>
> More work from CAMEL-19093
> If you have a local .jar in the folder (no maven dependency). For example a
> JDBC driver etc or custom JAR. Then we should during export
> - create a lib folder *DONE*
> - copy JARs to lib folder *DONE*
> - add <dependency> in pom.xml that refer to local file *DONE*
> - scan the JAR in case its a maven built as then it contains GAV we can use
> as placeholder in <dependency> *DONE*
> - gradle build ??? *DONE*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
