[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619384#comment-13619384
]
Enis Soztutar commented on HBASE-8224:
--------------------------------------
I did a bit more digging, but ran into a fundamental problem. Overriding the
artifactId from a property coming from the profile works, but when a project
depends on the installed artifact:
{code}
<dependency>
<groupId>org.apache.hbase</groupId>
<artifactId>hbase-server-hadoop2</artifactId>
<version>0.97-SNAPSHOT</version>
</dependency>
</dependencies>
{code}
then, there is no profile information, so it will just try to fetch the jars
from hadoop1 versions. I tried to circumvent this with putting a parent pom for
hadoop2 profile (pom-hadoop2.xml) which is a child of pom.xml, but also
declares child modules hbase-client, etc. This also fails to work because the
parent artifactId does not accept variables.
> Add '-hadoop1' or '-hadoop2' to our version string
> --------------------------------------------------
>
> Key: HBASE-8224
> URL: https://issues.apache.org/jira/browse/HBASE-8224
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Attachments: 8224-adding.classifiers.txt, hbase-8224-proto1.patch
>
>
> So we can publish both the hadoop1 and the hadoop2 jars to a maven
> repository, and so we can publish two packages, one for hadoop1 and one for
> hadoop2, given how maven works, our only alternative (to the best of my
> knowledge and after consulting others) is by amending the version string to
> include hadoop1 or hadoop2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
