You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/01/06 17:30:01 UTC

[GitHub] [camel-kafka-connector] orpiske commented on issue #62: Use artifactId instead of project.name to build colon-less distro paths

orpiske commented on issue #62: Use artifactId instead of project.name to build colon-less distro paths
URL: https://github.com/apache/camel-kafka-connector/pull/62#issuecomment-571231327
 
 
   > You're the first person reporting this. Building the project with mvn clean package and running with connect-standalone.sh always worked for everybody here.
   
   I was puzzled by this as well, but I took a look at the jars and it seems some recent change is indeed causing the build to generate jars with strange names. 
   
   ```$ find core/target/ -type f -name '*.jar'
   core/target/camel-kafka-connector-0.0.1-SNAPSHOT-package/share/java/Camel-Kafka-Connector :: Core/jackson-dataformat-cbor-2.10.1.jar
   core/target/camel-kafka-connector-0.0.1-SNAPSHOT-package/share/java/Camel-Kafka-Connector :: ...```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services