phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pedro Boado (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
Date Mon, 11 Jun 2018 22:10:04 GMT

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

Mime
View raw message