[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16514661#comment-16514661
]
Ankit Singhal commented on PHOENIX-1567:
[~pboado], probably you are affected by this
https://issues.apache.org/jira/browse/PHOENIX-4781.
I was not able to personally try mvn deploy as it is failing because of
Unauthorized access while transferring artifcats to remote.(though it's good I
have not accidentally pushed anything to remote) but looks like gpg:sign might
be looking for a jar as per the pom but the actual name of the jar is different.
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508868#comment-16508868
]
Josh Elser commented on PHOENIX-1567:
-
[~pboado], the error message doesn't make sense to me. You invoke deploy which
implies package which the gpg:sign mojo is claiming wasn't invoked.
Let me approach this differently: the intent is to publish the phoenix-client
and phoenix-server jars to Maven central. We do this by attaching them to the
build. We attach them to the build as the normal jar for their respective
modules (because the shaded classifier is of no consequence).
As such, by the time gpg:sign runs, the default artifact for this module should
have been assembled and would be ready to sign. I'll have to dig in, I'm just
not sure at face-value.
(not sure if this is a tangent or might help) you should just be able to enable
the {{apache-release}} profile (instead of manually invoking gpg:sign – e.g.
{{mvn deploy -Prelease,apache-release}})
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508836#comment-16508836
]
Pedro Boado commented on PHOENIX-1567:
--
[~elserj] it *does* replace the default artifact, but gpg:sign fails after
generating it. Just checkout v4.14.0-HBase-1.4 ( in fact, any of the tags
for this release ) and you'll see it.
{code:java}
$ mvn clean deploy gpg:sign -DperformRelease=true
-Dgpg.passphrase=MY_PASSPHRASE -Dgpg.keyname=MY_KEY] -DskipTests -P release -pl
phoenix-core,phoenix-pig,phoenix-tracing-webapp,phoenix-queryserver,phoenix-spark,phoenix-flume,phoenix-pherf,phoenix-queryserver-client,phoenix-hive,phoenix-client,phoenix-server
-am
{code}
fails with a
{code}
[INFO]
[INFO]
[INFO] Building Phoenix Client 4.14.0-HBase-1.4
[INFO]
(...)
[WARNING] maven-shade-plugin has detected that some class files are
[WARNING] present in two or more JARs. When this happens, only one
[WARNING] single version of the class is copied to the uber jar.
[WARNING] Usually this is not harmful and you can skip these warnings,
[WARNING] otherwise try to manually exclude artifacts based on
[WARNING] mvn dependency:tree -Ddetail=true and the above output.
[WARNING] See http://maven.apache.org/plugins/maven-shade-plugin/
[INFO] Replacing
/home/pedro/Development/workspace/phoenix-build/phoenix-client/target/phoenix-4.14.0-HBase-1.4-client.jar
with
/home/pedro/Development/workspace/phoenix-build/phoenix-client/target/phoenix-client-4.14.0-HBase-1.4-shaded.jar
[INFO]
[INFO] --- maven-gpg-plugin:1.6:sign (sign-artifacts) @ phoenix-client ---
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Phoenix . SUCCESS [ 16.155 s]
[INFO] Phoenix Core ... SUCCESS [01:20 min]
[INFO] Phoenix - Flume SUCCESS [ 16.794 s]
[INFO] Phoenix - Pig .. SUCCESS [01:04 min]
[INFO] Phoenix Query Server Client SUCCESS [ 26.776 s]
[INFO] Phoenix Query Server ... SUCCESS [ 16.489 s]
[INFO] Phoenix - Pherf SUCCESS [ 24.597 s]
[INFO] Phoenix - Spark SUCCESS [ 34.231 s]
[INFO] Phoenix - Hive . SUCCESS [01:21 min]
[INFO] Phoenix Client . FAILURE [ 45.696 s]
[INFO] Phoenix Server . SKIPPED
[INFO] Phoenix - Tracing Web Application .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 06:49 min
[INFO] Finished at: 2018-06-11T23:03:32+01:00
[INFO] Final Memory: 185M/3330M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-gpg-plugin:1.6:sign (sign-artifacts) on project
phoenix-client: The project artifact has not been assembled yet. Please do not
invoke this goal before the lifecycle phase "package". -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :phoenix-client
{code}
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
>
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508263#comment-16508263
]
Josh Elser commented on PHOENIX-1567:
-
What we want is for the maven-shade-plugin to replace the default artifact
(from maven-jar-plugin) for these modules. That _should_ be the default action.
Do you have a git-hash you can point me (us) at to inspect?
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506716#comment-16506716
]
Pedro Boado commented on PHOENIX-1567:
--
Just released 4.14.0 with the classifier. But I couldn't get it working without
it . This is the error that I am getting
{code}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 06:47 min
[INFO] Finished at: 2018-06-09T00:43:18+01:00
[INFO] Final Memory: 194M/3102M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-gpg-plugin:1.6:sign (default-cli) on project
phoenix-client: The project artifact has not been assembled yet. Please do not
invoke this goal before the lifecycle phase "package". -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
{code}
We might get it fixed for next release. Any sugegstion?
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506690#comment-16506690
]
Ankit Singhal commented on PHOENIX-1567:
bq. What is the idea, getting it published with or without the classifier?
As we don't publish the original jar, we can skip keeping any classifier for
shading jar as well.
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506685#comment-16506685
]
Pedro Boado commented on PHOENIX-1567:
--
[~an...@apache.org] by changing that value this coordinate gets pushed ( with
classifier shaded ) . No original artiffact is published - because it is
replaced -
{code}
org.apache.phoenix
phoenix-client
4.14.0-cdh5.11.2
shaded
{code}
What is the idea, getting it published with or without the classifier?
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506677#comment-16506677
]
Ankit Singhal commented on PHOENIX-1567:
{quote}true
{quote}
bq. Is there any reason for not having it attached in the current code?
[~pboado] , is this not needed only if we want to publish both the
artifacts(shaded/original) to the repository
[https://maven.apache.org/plugins/maven-shade-plugin/examples/attached-artifact.html]
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492493#comment-16492493
]
Hudson commented on PHOENIX-1567:
-
FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #1888 (See
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/1888/])
PHOENIX-1567 Publish Phoenix-Client & Phoenix-Server jars into Maven
(ankitsinghal59: rev 0c53d601a4851cceac284d500fa21ec9c2730ea6)
* (edit) phoenix-client/pom.xml
* (edit) phoenix-server/pom.xml
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16491413#comment-16491413
]
Hudson commented on PHOENIX-1567:
-
ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #145 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/145/])
PHOENIX-1567 Publish Phoenix-Client & Phoenix-Server jars into Maven
(ankitsinghal59: rev 7eaac1caa5c04801c39548403c758a68bfa278c7)
* (edit) phoenix-client/pom.xml
* (edit) phoenix-server/pom.xml
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16491289#comment-16491289
]
Hudson commented on PHOENIX-1567:
-
SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1906 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-0.98/1906/])
PHOENIX-1567 Publish Phoenix-Client & Phoenix-Server jars into Maven
(ankitsinghal59: rev 137ed5ee0545b92f5f67d95edbeb38662d98e914)
* (edit) phoenix-server/pom.xml
* (edit) phoenix-client/pom.xml
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490021#comment-16490021
]
Ankit Singhal commented on PHOENIX-1567:
Thanks [~elserj], committing the attached patch so that phoenix-client and
phoenix-server jar will starting going properly in respective maven directory.
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Priority: Major
> Attachments: PHOENIX-1567.patch
>
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489920#comment-16489920
]
Josh Elser commented on PHOENIX-1567:
-
{quote}should we start publishing phoenix-client artifact in maven from next
release
{quote}
+1
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Priority: Major
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489876#comment-16489876
]
Ankit Singhal commented on PHOENIX-1567:
bq. we should revisit and start publishing our shaded artifacts as well. Let me
know if it's fine
Guys , if we don't have any objection, should we start publishing
phoenix-client artifact in maven from next release? (Not sure if we need to
have phoenix-server in maven.)
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Priority: Major
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489361#comment-16489361
]
Josh Elser commented on PHOENIX-1567:
-
[~tony-kerz], phoenix-core was (unnecessarily) an uber-jar in all Phoenix
releases up until PHOENIX-4706. It is not, nor has been in any recent number of
years, as large as what the phoenix-client jar is.
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Priority: Major
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488339#comment-16488339
]
tony kerz commented on PHOENIX-1567:
ah, thanks for the feedback james and josh. a little further analysis clarifies:
{{org.apache.phoenix:phoenix-core:4.13.1-HBase-1.3}} in maven-central *is-not*
an uber-jar
{{phoenix-client }}*is* an uber-jar, but is obtained from distributions, and
*is-not* published to maven
i was having an issue connecting to an hdp install where i was told that some
hortonworks patches were required, so i grabbed the following from the hdp
maven-repo {{http://nexus-private.hortonworks.com/nexus/content/groups/public}}
{{org.apache.phoenix:phoenix-core:4.7.0.2.6.1.40-4}}
inexplicably, the above hdp version of {{phoenix-core}} *is* an uber-jar
similar to {{phoenix-client}} which gave me grief.
i apologize for the confusion on this thread, i will take up my specific issue
with hortonworks.
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Priority: Major
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487961#comment-16487961
]
James Taylor commented on PHOENIX-1567:
---
Is it possible for you to build phoenix yourself and then manage the
dependencies on your own? I'm not aware of us publishing uber jars to maven.
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Priority: Major
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487962#comment-16487962
]
Josh Elser commented on PHOENIX-1567:
-
{quote}i am presently experiencing some issues with a version of the fat client
jar (uber-jar) as published in maven because of the fact that it bundles in
dependencies instead of calling them out via standard maven practices.
{quote}
There are two sides of the coin and they are both valid.
phoenix-client is an all-in-one uber-jar (with relocated dependencies) as many
JDBC applications require a single jar. phoenix-core is a simple Maven artifact
that lists all dependencies via "standard maven practices".
We cannot possibly handle all situations, but we can handle most. For the
exceptional cases, users can build their own artifact that suits their needs.
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Priority: Major
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487947#comment-16487947
]
tony kerz commented on PHOENIX-1567:
i am presently experiencing some issues with a version of the fat client jar
(uber-jar) as published in maven because of the fact that it bundles in
dependencies instead of calling them out via standard maven practices.
this can lead to complicated issues such as conflicts between versions of
classes in the uber-jar and versions required by peer libraries
for instance, i just ran into an issue around gson classes bundled in the
uber-jar which clash with versions required by some spring framework packages.
uber-jars, while potentially useful for users who don't use package-management
tools like maven, gradle, sbt, are troublesome for users who do use these tools
because they thwart the tool's capabilities to manage things like version
reconciliation.
i would also suggest that most modern users do use package-management such that
uber-jars aren't addressing the needs of the broadest base.
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Priority: Major
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482624#comment-16482624
]
Josh Elser commented on PHOENIX-1567:
-
FYI [~an...@apache.org]
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>Priority: Major
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658153#comment-15658153
]
Randy Gelhausen commented on PHOENIX-1567:
--
+1 for revisiting this decision.
Apache NiFi and Apache Zeppelin allow users to supply arbitrary JDBC jars.
Without published artifacts for shaded jars, the end-user needs to:
1. Hit phoenix.apache.org -> Downloads -> Select a mirror -> Download and
uncompress a tarball
2. Determine whether they'll be using the queryserver
3. Pick the right jar from the litany of extremely similarly named jars
4. Manually copy that jar into NiFi or Zeppelin's local resource directories
It's a lot of work to ask a user to do instead of supplying:
org.apache.phoenix:phoenix-queryserver-client:4.8.0-HBase-1.1 (or phoenix-core).
> Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
>
>
> Key: PHOENIX-1567
> URL: https://issues.apache.org/jira/browse/PHOENIX-1567
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Jeffrey Zhong
>
> Phoenix doesn't publish Phoenix Client & Server jars into Maven repository.
> This make things quite hard for down steam projects/applications to use maven
> to resolve dependencies.
> I tried to modify the pom.xml under phoenix-assembly while it shows the
> following.
> {noformat}
> [INFO] Installing
> /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
>
> to
> /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
> {noformat}
> Basically the jar published to maven repo will become
> phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
> phoenix-assembly-4.3.0-SNAPSHOT-server.jar
> The artifact id "phoenix-assembly" has to be the prefix of the names of jars.
> Therefore, the possible solutions are:
> 1) rename current client & server jar to phoenix-assembly-clinet/server.jar
> to match the jars published to maven repo.
> 2) rename phoenix-assembly to something more meaningful and rename our client
> & server jars accordingly
> 3) split phoenix-assembly and move the corresponding artifacts into
> phoenix-client & phoenix-server folders. Phoenix-assembly will only create
> tar ball files.
> [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383949#comment-14383949
]
Carter Shanklin commented on PHOENIX-1567:
--
Not having a standalone phoenix-client in Maven is causing a good bit of
confusion among our users. Use cases include things like building a
JasperReports app that pulls data from Phoenix. When users install our RPM they
see a phoenix-client but when there's nothing for them in maven they assume
something is missing and file support cases we have to deal with. I'd rather
not answer this question another 10 times.
Publish Phoenix-Client Phoenix-Server jars into Maven Repo
Key: PHOENIX-1567
URL: https://issues.apache.org/jira/browse/PHOENIX-1567
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.2
Reporter: Jeffrey Zhong
Phoenix doesn't publish Phoenix Client Server jars into Maven repository.
This make things quite hard for down steam projects/applications to use maven
to resolve dependencies.
I tried to modify the pom.xml under phoenix-assembly while it shows the
following.
{noformat}
[INFO] Installing
/Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
to
/Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
{noformat}
Basically the jar published to maven repo will become
phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
phoenix-assembly-4.3.0-SNAPSHOT-server.jar
The artifact id phoenix-assembly has to be the prefix of the names of jars.
Therefore, the possible solutions are:
1) rename current client server jar to phoenix-assembly-clinet/server.jar
to match the jars published to maven repo.
2) rename phoenix-assembly to something more meaningful and rename our client
server jars accordingly
3) split phoenix-assembly and move the corresponding artifacts into
phoenix-client phoenix-server folders. Phoenix-assembly will only create
tar ball files.
[~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14297861#comment-14297861
]
Nick Dimiduk commented on PHOENIX-1567:
---
To be clear, I'm not advocating we push uberjars into maven central. I'm
suggesting a modular build for phoenix similar to what hbase has done, with a
phoenix-client module that produces a phoenix-client.jar artifact with a
minimal set of dependencies.
Publish Phoenix-Client Phoenix-Server jars into Maven Repo
Key: PHOENIX-1567
URL: https://issues.apache.org/jira/browse/PHOENIX-1567
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.2
Reporter: Jeffrey Zhong
Fix For: 5.0.0
Phoenix doesn't publish Phoenix Client Server jars into Maven repository.
This make things quite hard for down steam projects/applications to use maven
to resolve dependencies.
I tried to modify the pom.xml under phoenix-assembly while it shows the
following.
{noformat}
[INFO] Installing
/Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
to
/Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
{noformat}
Basically the jar published to maven repo will become
phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
phoenix-assembly-4.3.0-SNAPSHOT-server.jar
The artifact id phoenix-assembly has to be the prefix of the names of jars.
Therefore, the possible solutions are:
1) rename current client server jar to phoenix-assembly-clinet/server.jar
to match the jars published to maven repo.
2) rename phoenix-assembly to something more meaningful and rename our client
server jars accordingly
3) split phoenix-assembly and move the corresponding artifacts into
phoenix-client phoenix-server folders. Phoenix-assembly will only create
tar ball files.
[~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14261640#comment-14261640
]
James Taylor commented on PHOENIX-1567:
---
I'm no maven expert, but I know one ([~jesse_yates]).
Publish Phoenix-Client Phoenix-Server jars into Maven Repo
Key: PHOENIX-1567
URL: https://issues.apache.org/jira/browse/PHOENIX-1567
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.2
Reporter: Jeffrey Zhong
Phoenix doesn't publish Phoenix Client Server jars into Maven repository.
This make things quite hard for down steam projects/applications to use maven
to resolve dependencies.
I tried to modify the pom.xml under phoenix-assembly while it shows the
following.
{noformat}
[INFO] Installing
/Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
to
/Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
{noformat}
Basically the jar published to maven repo will become
phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
phoenix-assembly-4.3.0-SNAPSHOT-server.jar
The artifact id phoenix-assembly has to be the prefix of the names of jars.
Therefore, the possible solutions are:
1) rename current client server jar to phoenix-assembly-clinet/server.jar
to match the jars published to maven repo.
2) rename phoenix-assembly to something more meaningful and rename our client
server jars accordingly
3) split phoenix-assembly and move the corresponding artifacts into
phoenix-client phoenix-server folders. Phoenix-assembly will only create
tar ball files.
[~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14261670#comment-14261670
]
James Taylor commented on PHOENIX-1567:
---
I agree, [~mujtabachohan], that does seem better, but I suspect there's a
reason why Jeffrey doesn't want to do that. [~jeffreyz]?
Publish Phoenix-Client Phoenix-Server jars into Maven Repo
Key: PHOENIX-1567
URL: https://issues.apache.org/jira/browse/PHOENIX-1567
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.2
Reporter: Jeffrey Zhong
Phoenix doesn't publish Phoenix Client Server jars into Maven repository.
This make things quite hard for down steam projects/applications to use maven
to resolve dependencies.
I tried to modify the pom.xml under phoenix-assembly while it shows the
following.
{noformat}
[INFO] Installing
/Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
to
/Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
{noformat}
Basically the jar published to maven repo will become
phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
phoenix-assembly-4.3.0-SNAPSHOT-server.jar
The artifact id phoenix-assembly has to be the prefix of the names of jars.
Therefore, the possible solutions are:
1) rename current client server jar to phoenix-assembly-clinet/server.jar
to match the jars published to maven repo.
2) rename phoenix-assembly to something more meaningful and rename our client
server jars accordingly
3) split phoenix-assembly and move the corresponding artifacts into
phoenix-client phoenix-server folders. Phoenix-assembly will only create
tar ball files.
[~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14261671#comment-14261671
]
Jeffrey Zhong commented on PHOENIX-1567:
When we deploy Phoenix, phoenix-client server jars are used not phoenix-core.
The disparity causes confusion because when an application uses out of box
Phoenix, Phoenix-client/server jar will be used while down stream projects
phoenix-core jar with other jars are used. I'm not sure what's the best
practices since I've been asked on this several times.
Publish Phoenix-Client Phoenix-Server jars into Maven Repo
Key: PHOENIX-1567
URL: https://issues.apache.org/jira/browse/PHOENIX-1567
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.2
Reporter: Jeffrey Zhong
Phoenix doesn't publish Phoenix Client Server jars into Maven repository.
This make things quite hard for down steam projects/applications to use maven
to resolve dependencies.
I tried to modify the pom.xml under phoenix-assembly while it shows the
following.
{noformat}
[INFO] Installing
/Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
to
/Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
{noformat}
Basically the jar published to maven repo will become
phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
phoenix-assembly-4.3.0-SNAPSHOT-server.jar
The artifact id phoenix-assembly has to be the prefix of the names of jars.
Therefore, the possible solutions are:
1) rename current client server jar to phoenix-assembly-clinet/server.jar
to match the jars published to maven repo.
2) rename phoenix-assembly to something more meaningful and rename our client
server jars accordingly
3) split phoenix-assembly and move the corresponding artifacts into
phoenix-client phoenix-server folders. Phoenix-assembly will only create
tar ball files.
[~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client Phoenix-Server jars into Maven Repo
[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14261730#comment-14261730
]
Jesse Yates commented on PHOENIX-1567:
--
bq. Is it good practice to publish über jars to Maven? I thought it was not
good practice but could be mistaken.
This was my first thought as well.
bq. Perhaps a documentation improvement could help clarify the roles of the
client and server jar in the distribution?
And this was my second thought. Maybe a doc page on 'using phoenix' with
explicit sections on 'from code' and and 'from tarball'.
If you pull in phoenix-core (and possibly -flume, etc) then maven does all the
hard work of finding all the transitive dependencies and resolving them
properly. Including the -client and -server jars in maven would actually make
life very painful - maven would have no way of knowing about the uber-packaged
dependencies, almost assuredly leading to weird classpath issues for whomever
is using phoenix-server or -client.
Publish Phoenix-Client Phoenix-Server jars into Maven Repo
Key: PHOENIX-1567
URL: https://issues.apache.org/jira/browse/PHOENIX-1567
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.2
Reporter: Jeffrey Zhong
Phoenix doesn't publish Phoenix Client Server jars into Maven repository.
This make things quite hard for down steam projects/applications to use maven
to resolve dependencies.
I tried to modify the pom.xml under phoenix-assembly while it shows the
following.
{noformat}
[INFO] Installing
/Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar
to
/Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar
{noformat}
Basically the jar published to maven repo will become
phoenix-assembly-4.3.0-SNAPSHOT-client.jar or
phoenix-assembly-4.3.0-SNAPSHOT-server.jar
The artifact id phoenix-assembly has to be the prefix of the names of jars.
Therefore, the possible solutions are:
1) rename current client server jar to phoenix-assembly-clinet/server.jar
to match the jars published to maven repo.
2) rename phoenix-assembly to something more meaningful and rename our client
server jars accordingly
3) split phoenix-assembly and move the corresponding artifacts into
phoenix-client phoenix-server folders. Phoenix-assembly will only create
tar ball files.
[~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this?
Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
