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