[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
