Specify version when deploying to nexus from maven
up vote
1
down vote
favorite
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 |
up vote
1
down vote
favorite
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 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 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 at 13:17
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 at 16:52
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
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 at 16:49
cricket_007
76.9k1142106
76.9k1142106
asked Nov 19 at 12:43
Tom Lous
1,25611222
1,25611222
Where is confluent.version defined? What is its definition?
– JF Meier
Nov 19 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 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 at 13:17
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 at 16:52
add a comment |
Where is confluent.version defined? What is its definition?
– JF Meier
Nov 19 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 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 at 13:17
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 at 16:52
Where is confluent.version defined? What is its definition?
– JF Meier
Nov 19 at 13:13
Where is confluent.version defined? What is its definition?
– JF Meier
Nov 19 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 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 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 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 at 13:17
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 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 at 16:52
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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 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 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 at 13:17
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 at 16:52