[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487947#comment-16487947
]
tony kerz edited comment on PHOENIX-1567 at 5/23/18 7:58 PM:
-------------------------------------------------------------
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 and groovy 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.
was (Author: tony-kerz):
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)
