Specify version when deploying to nexus from maven
I've forked Confluent's Kafka Connect HDFS writer and now I'd like to deploy a version of this jar to my local Nexus.
mvn clean deploy
Works like a charm and deploys the jar.
https://[nexus]/repository/releases/io/confluent/kafka-connect-hdfs/5.0.0/kafka-connect-hdfs-5.0.0.jar
So far so good, but to make a distinction between the confluent versions and my own deployment I'd like to change the version of the build to something like 5.0.0-1
or so (preferably the tag name when pushed, but that's step 2)
The pom.xml is basically the same as the 5.0.0-post release, but here the most important parts:
<parent>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-common-parent</artifactId>
<version>5.0.0</version>
</parent>
<artifactId>kafka-connect-hdfs</artifactId>
<packaging>jar</packaging>
<name>kafka-connect-hdfs</name>
<organization>
<name>Confluent, Inc.</name>
<url>http://confluent.io</url>
</organization>
<url>http://confluent.io</url>
<description>
A Kafka Connect HDFS connector for copying data between Kafka and Hadoop HDFS.
</description>
...
<dependencies>
...
<dependency>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-common</artifactId>
<version>${confluent.version}</version>
</dependency>
<dependency>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-core</artifactId>
<version>${confluent.version}</version>
</dependency>
...
</dependencies>
<build>
<plugins>
<plugin>
<groupId>io.confluent</groupId>
<version>0.10.0</version>
<artifactId>kafka-connect-maven-plugin</artifactId>
...
So first I added <version>
tags to the pom.xml, but it started using that as the default for all confluent.version
and complained that it couldn't find for example: https://[nexus]/repository/releases/io/confluent/kafka-connect-storage-hive/5.0.0-1/kafka-connect-storage-hive-5.0.0-1.pom
Next I tried the versions plugin from maven
mvn versions:set -DnewVersion=5.0.0-1 clean deploy
But that complained about the parent:
[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.7:set (default-cli) on project kafka-connect-hdfs: Project version is inherited from parent. -> [Help 1]
I don't even care if the version is 5.0.0 in the code, I just wat to deploy to a different version in our artifactory.
I'm not a maven expert, so maybe I'm missing some very basic clue, but all help is welcome.
maven apache-kafka nexus apache-kafka-connect confluent
add a comment |
I've forked Confluent's Kafka Connect HDFS writer and now I'd like to deploy a version of this jar to my local Nexus.
mvn clean deploy
Works like a charm and deploys the jar.
https://[nexus]/repository/releases/io/confluent/kafka-connect-hdfs/5.0.0/kafka-connect-hdfs-5.0.0.jar
So far so good, but to make a distinction between the confluent versions and my own deployment I'd like to change the version of the build to something like 5.0.0-1
or so (preferably the tag name when pushed, but that's step 2)
The pom.xml is basically the same as the 5.0.0-post release, but here the most important parts:
<parent>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-common-parent</artifactId>
<version>5.0.0</version>
</parent>
<artifactId>kafka-connect-hdfs</artifactId>
<packaging>jar</packaging>
<name>kafka-connect-hdfs</name>
<organization>
<name>Confluent, Inc.</name>
<url>http://confluent.io</url>
</organization>
<url>http://confluent.io</url>
<description>
A Kafka Connect HDFS connector for copying data between Kafka and Hadoop HDFS.
</description>
...
<dependencies>
...
<dependency>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-common</artifactId>
<version>${confluent.version}</version>
</dependency>
<dependency>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-core</artifactId>
<version>${confluent.version}</version>
</dependency>
...
</dependencies>
<build>
<plugins>
<plugin>
<groupId>io.confluent</groupId>
<version>0.10.0</version>
<artifactId>kafka-connect-maven-plugin</artifactId>
...
So first I added <version>
tags to the pom.xml, but it started using that as the default for all confluent.version
and complained that it couldn't find for example: https://[nexus]/repository/releases/io/confluent/kafka-connect-storage-hive/5.0.0-1/kafka-connect-storage-hive-5.0.0-1.pom
Next I tried the versions plugin from maven
mvn versions:set -DnewVersion=5.0.0-1 clean deploy
But that complained about the parent:
[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.7:set (default-cli) on project kafka-connect-hdfs: Project version is inherited from parent. -> [Help 1]
I don't even care if the version is 5.0.0 in the code, I just wat to deploy to a different version in our artifactory.
I'm not a maven expert, so maybe I'm missing some very basic clue, but all help is welcome.
maven apache-kafka nexus apache-kafka-connect confluent
Where is confluent.version defined? What is its definition?
– JF Meier
Nov 19 '18 at 13:13
I actually don't know. I'm assuming that thekafka-connect-maven-plugin
is doing some magic in this area, because I cannot find a reference in this project.
– Tom Lous
Nov 19 '18 at 13:15
When I used extensive debugging it all of a sudden has this line[DEBUG] properties used {docker.upstream-registry=placeholder/, ... confluent.version=5.0.0, avro.version=1.8.1, java.vm.info=mixed mode, ...
– Tom Lous
Nov 19 '18 at 13:17
1
Personally, I just use our existing Nexus repos, but have<artifactId>kafka-connect-hdfs</artifactId><scope>provided</scope><version>5.0.0</version>
, then just extend whatever code I need... Then, if you put that built JAR into thekafka-connect-storage-hdfs
folder, it should work
– cricket_007
Nov 19 '18 at 16:52
add a comment |
I've forked Confluent's Kafka Connect HDFS writer and now I'd like to deploy a version of this jar to my local Nexus.
mvn clean deploy
Works like a charm and deploys the jar.
https://[nexus]/repository/releases/io/confluent/kafka-connect-hdfs/5.0.0/kafka-connect-hdfs-5.0.0.jar
So far so good, but to make a distinction between the confluent versions and my own deployment I'd like to change the version of the build to something like 5.0.0-1
or so (preferably the tag name when pushed, but that's step 2)
The pom.xml is basically the same as the 5.0.0-post release, but here the most important parts:
<parent>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-common-parent</artifactId>
<version>5.0.0</version>
</parent>
<artifactId>kafka-connect-hdfs</artifactId>
<packaging>jar</packaging>
<name>kafka-connect-hdfs</name>
<organization>
<name>Confluent, Inc.</name>
<url>http://confluent.io</url>
</organization>
<url>http://confluent.io</url>
<description>
A Kafka Connect HDFS connector for copying data between Kafka and Hadoop HDFS.
</description>
...
<dependencies>
...
<dependency>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-common</artifactId>
<version>${confluent.version}</version>
</dependency>
<dependency>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-core</artifactId>
<version>${confluent.version}</version>
</dependency>
...
</dependencies>
<build>
<plugins>
<plugin>
<groupId>io.confluent</groupId>
<version>0.10.0</version>
<artifactId>kafka-connect-maven-plugin</artifactId>
...
So first I added <version>
tags to the pom.xml, but it started using that as the default for all confluent.version
and complained that it couldn't find for example: https://[nexus]/repository/releases/io/confluent/kafka-connect-storage-hive/5.0.0-1/kafka-connect-storage-hive-5.0.0-1.pom
Next I tried the versions plugin from maven
mvn versions:set -DnewVersion=5.0.0-1 clean deploy
But that complained about the parent:
[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.7:set (default-cli) on project kafka-connect-hdfs: Project version is inherited from parent. -> [Help 1]
I don't even care if the version is 5.0.0 in the code, I just wat to deploy to a different version in our artifactory.
I'm not a maven expert, so maybe I'm missing some very basic clue, but all help is welcome.
maven apache-kafka nexus apache-kafka-connect confluent
I've forked Confluent's Kafka Connect HDFS writer and now I'd like to deploy a version of this jar to my local Nexus.
mvn clean deploy
Works like a charm and deploys the jar.
https://[nexus]/repository/releases/io/confluent/kafka-connect-hdfs/5.0.0/kafka-connect-hdfs-5.0.0.jar
So far so good, but to make a distinction between the confluent versions and my own deployment I'd like to change the version of the build to something like 5.0.0-1
or so (preferably the tag name when pushed, but that's step 2)
The pom.xml is basically the same as the 5.0.0-post release, but here the most important parts:
<parent>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-common-parent</artifactId>
<version>5.0.0</version>
</parent>
<artifactId>kafka-connect-hdfs</artifactId>
<packaging>jar</packaging>
<name>kafka-connect-hdfs</name>
<organization>
<name>Confluent, Inc.</name>
<url>http://confluent.io</url>
</organization>
<url>http://confluent.io</url>
<description>
A Kafka Connect HDFS connector for copying data between Kafka and Hadoop HDFS.
</description>
...
<dependencies>
...
<dependency>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-common</artifactId>
<version>${confluent.version}</version>
</dependency>
<dependency>
<groupId>io.confluent</groupId>
<artifactId>kafka-connect-storage-core</artifactId>
<version>${confluent.version}</version>
</dependency>
...
</dependencies>
<build>
<plugins>
<plugin>
<groupId>io.confluent</groupId>
<version>0.10.0</version>
<artifactId>kafka-connect-maven-plugin</artifactId>
...
So first I added <version>
tags to the pom.xml, but it started using that as the default for all confluent.version
and complained that it couldn't find for example: https://[nexus]/repository/releases/io/confluent/kafka-connect-storage-hive/5.0.0-1/kafka-connect-storage-hive-5.0.0-1.pom
Next I tried the versions plugin from maven
mvn versions:set -DnewVersion=5.0.0-1 clean deploy
But that complained about the parent:
[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.7:set (default-cli) on project kafka-connect-hdfs: Project version is inherited from parent. -> [Help 1]
I don't even care if the version is 5.0.0 in the code, I just wat to deploy to a different version in our artifactory.
I'm not a maven expert, so maybe I'm missing some very basic clue, but all help is welcome.
maven apache-kafka nexus apache-kafka-connect confluent
maven apache-kafka nexus apache-kafka-connect confluent
edited Nov 19 '18 at 16:49
cricket_007
82.1k1143111
82.1k1143111
asked Nov 19 '18 at 12:43
Tom LousTom Lous
1,56911324
1,56911324
Where is confluent.version defined? What is its definition?
– JF Meier
Nov 19 '18 at 13:13
I actually don't know. I'm assuming that thekafka-connect-maven-plugin
is doing some magic in this area, because I cannot find a reference in this project.
– Tom Lous
Nov 19 '18 at 13:15
When I used extensive debugging it all of a sudden has this line[DEBUG] properties used {docker.upstream-registry=placeholder/, ... confluent.version=5.0.0, avro.version=1.8.1, java.vm.info=mixed mode, ...
– Tom Lous
Nov 19 '18 at 13:17
1
Personally, I just use our existing Nexus repos, but have<artifactId>kafka-connect-hdfs</artifactId><scope>provided</scope><version>5.0.0</version>
, then just extend whatever code I need... Then, if you put that built JAR into thekafka-connect-storage-hdfs
folder, it should work
– cricket_007
Nov 19 '18 at 16:52
add a comment |
Where is confluent.version defined? What is its definition?
– JF Meier
Nov 19 '18 at 13:13
I actually don't know. I'm assuming that thekafka-connect-maven-plugin
is doing some magic in this area, because I cannot find a reference in this project.
– Tom Lous
Nov 19 '18 at 13:15
When I used extensive debugging it all of a sudden has this line[DEBUG] properties used {docker.upstream-registry=placeholder/, ... confluent.version=5.0.0, avro.version=1.8.1, java.vm.info=mixed mode, ...
– Tom Lous
Nov 19 '18 at 13:17
1
Personally, I just use our existing Nexus repos, but have<artifactId>kafka-connect-hdfs</artifactId><scope>provided</scope><version>5.0.0</version>
, then just extend whatever code I need... Then, if you put that built JAR into thekafka-connect-storage-hdfs
folder, it should work
– cricket_007
Nov 19 '18 at 16:52
Where is confluent.version defined? What is its definition?
– JF Meier
Nov 19 '18 at 13:13
Where is confluent.version defined? What is its definition?
– JF Meier
Nov 19 '18 at 13:13
I actually don't know. I'm assuming that the
kafka-connect-maven-plugin
is doing some magic in this area, because I cannot find a reference in this project.– Tom Lous
Nov 19 '18 at 13:15
I actually don't know. I'm assuming that the
kafka-connect-maven-plugin
is doing some magic in this area, because I cannot find a reference in this project.– Tom Lous
Nov 19 '18 at 13:15
When I used extensive debugging it all of a sudden has this line
[DEBUG] properties used {docker.upstream-registry=placeholder/, ... confluent.version=5.0.0, avro.version=1.8.1, java.vm.info=mixed mode, ...
– Tom Lous
Nov 19 '18 at 13:17
When I used extensive debugging it all of a sudden has this line
[DEBUG] properties used {docker.upstream-registry=placeholder/, ... confluent.version=5.0.0, avro.version=1.8.1, java.vm.info=mixed mode, ...
– Tom Lous
Nov 19 '18 at 13:17
1
1
Personally, I just use our existing Nexus repos, but have
<artifactId>kafka-connect-hdfs</artifactId><scope>provided</scope><version>5.0.0</version>
, then just extend whatever code I need... Then, if you put that built JAR into the kafka-connect-storage-hdfs
folder, it should work– cricket_007
Nov 19 '18 at 16:52
Personally, I just use our existing Nexus repos, but have
<artifactId>kafka-connect-hdfs</artifactId><scope>provided</scope><version>5.0.0</version>
, then just extend whatever code I need... Then, if you put that built JAR into the kafka-connect-storage-hdfs
folder, it should work– cricket_007
Nov 19 '18 at 16:52
add a comment |
2 Answers
2
active
oldest
votes
You can specify the version with ${revision}
parameter.
To do this, you need to add <version>
tag with this variable in pom.xml:
<artifactId>kafka-connect-hdfs</artifactId>
<version>5.0.0-${revision}</version>
<packaging>jar</packaging>
And then provide it to the maven command. E.g.,
mvn clean package -Drevision=01
will generate kafka-connect-hdfs-5.0.0-01.jar
file.
Thanks biruk1230, I've actually tried this (sorry for not mentioning) but I ran into the same issues
– Tom Lous
Dec 6 '18 at 10:08
That's strange. Did you try to add this code to your pom.xml (under the <build> section)?<finalName>${project.artifactId}-${project.version}</finalName>
– biruk1230
Dec 6 '18 at 16:36
add a comment |
So there were some good suggestions, but in the end the one thing that worked best for me in our setup was to use the deploy:deploy-file
command for maven.
mvn deploy:deploy-file
-Dfile=target/kafka-connect-hdfs-5.0.0.jar
-DrepositoryId=[nexus id]
-Durl=[nexus url]
-Dversion=$TAG
-DgroupId=io.confluent
-DartifactId=kafka-connect-hdfs
The major downside was that I had to respecify parameters that were already present in the pom.xml (artifactId
, groupId
, ect), but it works, and that's what counts :-)
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374924%2fspecify-version-when-deploying-to-nexus-from-maven%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can specify the version with ${revision}
parameter.
To do this, you need to add <version>
tag with this variable in pom.xml:
<artifactId>kafka-connect-hdfs</artifactId>
<version>5.0.0-${revision}</version>
<packaging>jar</packaging>
And then provide it to the maven command. E.g.,
mvn clean package -Drevision=01
will generate kafka-connect-hdfs-5.0.0-01.jar
file.
Thanks biruk1230, I've actually tried this (sorry for not mentioning) but I ran into the same issues
– Tom Lous
Dec 6 '18 at 10:08
That's strange. Did you try to add this code to your pom.xml (under the <build> section)?<finalName>${project.artifactId}-${project.version}</finalName>
– biruk1230
Dec 6 '18 at 16:36
add a comment |
You can specify the version with ${revision}
parameter.
To do this, you need to add <version>
tag with this variable in pom.xml:
<artifactId>kafka-connect-hdfs</artifactId>
<version>5.0.0-${revision}</version>
<packaging>jar</packaging>
And then provide it to the maven command. E.g.,
mvn clean package -Drevision=01
will generate kafka-connect-hdfs-5.0.0-01.jar
file.
Thanks biruk1230, I've actually tried this (sorry for not mentioning) but I ran into the same issues
– Tom Lous
Dec 6 '18 at 10:08
That's strange. Did you try to add this code to your pom.xml (under the <build> section)?<finalName>${project.artifactId}-${project.version}</finalName>
– biruk1230
Dec 6 '18 at 16:36
add a comment |
You can specify the version with ${revision}
parameter.
To do this, you need to add <version>
tag with this variable in pom.xml:
<artifactId>kafka-connect-hdfs</artifactId>
<version>5.0.0-${revision}</version>
<packaging>jar</packaging>
And then provide it to the maven command. E.g.,
mvn clean package -Drevision=01
will generate kafka-connect-hdfs-5.0.0-01.jar
file.
You can specify the version with ${revision}
parameter.
To do this, you need to add <version>
tag with this variable in pom.xml:
<artifactId>kafka-connect-hdfs</artifactId>
<version>5.0.0-${revision}</version>
<packaging>jar</packaging>
And then provide it to the maven command. E.g.,
mvn clean package -Drevision=01
will generate kafka-connect-hdfs-5.0.0-01.jar
file.
edited Nov 29 '18 at 12:11
answered Nov 29 '18 at 12:02
biruk1230biruk1230
1,0111316
1,0111316
Thanks biruk1230, I've actually tried this (sorry for not mentioning) but I ran into the same issues
– Tom Lous
Dec 6 '18 at 10:08
That's strange. Did you try to add this code to your pom.xml (under the <build> section)?<finalName>${project.artifactId}-${project.version}</finalName>
– biruk1230
Dec 6 '18 at 16:36
add a comment |
Thanks biruk1230, I've actually tried this (sorry for not mentioning) but I ran into the same issues
– Tom Lous
Dec 6 '18 at 10:08
That's strange. Did you try to add this code to your pom.xml (under the <build> section)?<finalName>${project.artifactId}-${project.version}</finalName>
– biruk1230
Dec 6 '18 at 16:36
Thanks biruk1230, I've actually tried this (sorry for not mentioning) but I ran into the same issues
– Tom Lous
Dec 6 '18 at 10:08
Thanks biruk1230, I've actually tried this (sorry for not mentioning) but I ran into the same issues
– Tom Lous
Dec 6 '18 at 10:08
That's strange. Did you try to add this code to your pom.xml (under the <build> section)?
<finalName>${project.artifactId}-${project.version}</finalName>
– biruk1230
Dec 6 '18 at 16:36
That's strange. Did you try to add this code to your pom.xml (under the <build> section)?
<finalName>${project.artifactId}-${project.version}</finalName>
– biruk1230
Dec 6 '18 at 16:36
add a comment |
So there were some good suggestions, but in the end the one thing that worked best for me in our setup was to use the deploy:deploy-file
command for maven.
mvn deploy:deploy-file
-Dfile=target/kafka-connect-hdfs-5.0.0.jar
-DrepositoryId=[nexus id]
-Durl=[nexus url]
-Dversion=$TAG
-DgroupId=io.confluent
-DartifactId=kafka-connect-hdfs
The major downside was that I had to respecify parameters that were already present in the pom.xml (artifactId
, groupId
, ect), but it works, and that's what counts :-)
add a comment |
So there were some good suggestions, but in the end the one thing that worked best for me in our setup was to use the deploy:deploy-file
command for maven.
mvn deploy:deploy-file
-Dfile=target/kafka-connect-hdfs-5.0.0.jar
-DrepositoryId=[nexus id]
-Durl=[nexus url]
-Dversion=$TAG
-DgroupId=io.confluent
-DartifactId=kafka-connect-hdfs
The major downside was that I had to respecify parameters that were already present in the pom.xml (artifactId
, groupId
, ect), but it works, and that's what counts :-)
add a comment |
So there were some good suggestions, but in the end the one thing that worked best for me in our setup was to use the deploy:deploy-file
command for maven.
mvn deploy:deploy-file
-Dfile=target/kafka-connect-hdfs-5.0.0.jar
-DrepositoryId=[nexus id]
-Durl=[nexus url]
-Dversion=$TAG
-DgroupId=io.confluent
-DartifactId=kafka-connect-hdfs
The major downside was that I had to respecify parameters that were already present in the pom.xml (artifactId
, groupId
, ect), but it works, and that's what counts :-)
So there were some good suggestions, but in the end the one thing that worked best for me in our setup was to use the deploy:deploy-file
command for maven.
mvn deploy:deploy-file
-Dfile=target/kafka-connect-hdfs-5.0.0.jar
-DrepositoryId=[nexus id]
-Durl=[nexus url]
-Dversion=$TAG
-DgroupId=io.confluent
-DartifactId=kafka-connect-hdfs
The major downside was that I had to respecify parameters that were already present in the pom.xml (artifactId
, groupId
, ect), but it works, and that's what counts :-)
answered Dec 6 '18 at 10:14
Tom LousTom Lous
1,56911324
1,56911324
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374924%2fspecify-version-when-deploying-to-nexus-from-maven%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Where is confluent.version defined? What is its definition?
– JF Meier
Nov 19 '18 at 13:13
I actually don't know. I'm assuming that the
kafka-connect-maven-plugin
is doing some magic in this area, because I cannot find a reference in this project.– Tom Lous
Nov 19 '18 at 13:15
When I used extensive debugging it all of a sudden has this line
[DEBUG] properties used {docker.upstream-registry=placeholder/, ... confluent.version=5.0.0, avro.version=1.8.1, java.vm.info=mixed mode, ...
– Tom Lous
Nov 19 '18 at 13:17
1
Personally, I just use our existing Nexus repos, but have
<artifactId>kafka-connect-hdfs</artifactId><scope>provided</scope><version>5.0.0</version>
, then just extend whatever code I need... Then, if you put that built JAR into thekafka-connect-storage-hdfs
folder, it should work– cricket_007
Nov 19 '18 at 16:52