[jira] [Updated] (HBASE-8224) Add '-hadoop1' or '-hadoop2' to our version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8224: - Attachment: 8224.gen.script.txt This patch includes latest over on hbase-8488 so ignore the changes to do w/ dependency inclusion and purge of slf4j for now (I'll fix up the patch later). Patch adds a script into dev-support called generate-hadoopX-poms.sh Run the script to generate a hadoop1 or hadoop2 pom from the original pom. The new pom shows up to the side of the original. Next build telling mvn to use this new pom. This seems to generate artifacts that are w/o pollution: i.e. no need for downstreamer to add a -Dhadoop.profile=2.0, etc. I used this script to deploy new hbase-hadoop1 and hbase-hadoop2 snapshots up at https://repository.apache.org/content/repositories/snapshots/org/apache/hbase/hbase/ ([~brocknoland] -- you have a chance to take a look at them?). Here is roughly what you do to build artifacts to publish: $ bash -x ./dev-support/generate-hadoopX-poms.sh 0.95.2-SNAPSHOT 0.95.2-hadoop1-SNAPSHOT $ $ mvn clean install deploy -DskipTests -Pgpg -f pom.xml.hadoop1 The head of the script has more on how it works. I'll write it up better in the manual after I've played some more (need to look at assembly's and at maven release). > 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 >Assignee: stack >Priority: Blocker > Fix For: 0.95.2 > > Attachments: 8224-adding.classifiers.txt, 8224.gen.script.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
[jira] [Updated] (HBASE-8224) Add '-hadoop1' or '-hadoop2' to our version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-8224: - Priority: Blocker (was: Critical) > 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 >Assignee: stack >Priority: Blocker > Fix For: 0.95.2 > > 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
[jira] [Updated] (HBASE-8224) Add '-hadoop1' or '-hadoop2' to our version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8224: - Priority: Critical (was: Major) This issue I am using for figuring build against h1 and h2 and then publishing to mvn repo. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.2 > > 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
[jira] [Updated] (HBASE-8224) Add '-hadoop1' or '-hadoop2' to our version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8224: - Fix Version/s: 0.95.2 Assignee: stack > 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 >Assignee: stack > Fix For: 0.95.2 > > 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
[jira] [Updated] (HBASE-8224) Add '-hadoop1' or '-hadoop2' to our version string
[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-8224:
-
Attachment: hbase-8224-proto1.patch
[~stack] could you please take a quick look at the prototype patch.
{code}
mvn clean install -DskipTests
{code}
builds with hadoop1 suffix:
{code}
[INFO] Installing
/Users/enis/projects/svn-repos/hbase/hbase-server/target/hbase-server-hadoop1-0.97-SNAPSHOT.jar
to
/Users/enis/.m2/repository/org/apache/hbase/hbase-server-hadoop1/0.97-SNAPSHOT/hbase-server-hadoop1-0.97-SNAPSHOT.jar
[INFO] Installing /Users/enis/projects/svn-repos/hbase/hbase-server/pom.xml to
/Users/enis/.m2/repository/org/apache/hbase/hbase-server-hadoop1/0.97-SNAPSHOT/hbase-server-hadoop1-0.97-SNAPSHOT.pom
[INFO] Installing
/Users/enis/projects/svn-repos/hbase/hbase-server/target/hbase-server-hadoop1-0.97-SNAPSHOT-tests.jar
to
/Users/enis/.m2/repository/org/apache/hbase/hbase-server-hadoop1/0.97-SNAPSHOT/hbase-server-hadoop1-0.97-SNAPSHOT-tests.jar
[INFO] Installing
/Users/enis/projects/svn-repos/hbase/hbase-server/target/hbase-server-hadoop1-0.97-SNAPSHOT-sources.jar
to
/Users/enis/.m2/repository/org/apache/hbase/hbase-server-hadoop1/0.97-SNAPSHOT/hbase-server-hadoop1-0.97-SNAPSHOT-sources.jar
{code}
For hadoop2 profile:
{code}
mvn install -DskipTests -Dhadoop.profile=2.0
{code}
results in
{code}
[INFO] Installing
/Users/enis/projects/svn-repos/hbase/hbase-server/target/hbase-server-hadoop2-0.97-SNAPSHOT.jar
to
/Users/enis/.m2/repository/org/apache/hbase/hbase-server-hadoop2/0.97-SNAPSHOT/hbase-server-hadoop2-0.97-SNAPSHOT.jar
[INFO] Installing /Users/enis/projects/svn-repos/hbase/hbase-server/pom.xml to
/Users/enis/.m2/repository/org/apache/hbase/hbase-server-hadoop2/0.97-SNAPSHOT/hbase-server-hadoop2-0.97-SNAPSHOT.pom
[INFO] Installing
/Users/enis/projects/svn-repos/hbase/hbase-server/target/hbase-server-hadoop2-0.97-SNAPSHOT-tests.jar
to
/Users/enis/.m2/repository/org/apache/hbase/hbase-server-hadoop2/0.97-SNAPSHOT/hbase-server-hadoop2-0.97-SNAPSHOT-tests.jar
[INFO] Installing
/Users/enis/projects/svn-repos/hbase/hbase-server/target/hbase-server-hadoop2-0.97-SNAPSHOT-sources.jar
to
/Users/enis/.m2/repository/org/apache/hbase/hbase-server-hadoop2/0.97-SNAPSHOT/hbase-server-hadoop2-0.97-SNAPSHOT-sources.jar
{code}
Not sure whether this will work with the assembly or maven publish, but install
seems fine.
> 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
[jira] [Updated] (HBASE-8224) Add '-hadoop1' or '-hadoop2' to our version string
[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-8224:
-
Attachment: 8224-adding.classifiers.txt
I tried adding classifiers. Was fine till I got to the assembly step:
{code}
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Error adding file
'org.apache.hbase:hbase-common:jar:0.97.0-SNAPSHOT' to archive:
/Users/stack/checkouts/hbase/hbase-common/target/classes isn't a file. -> [Help
1]
{code}
I couldn't get over the above. There is no vocabulary around moduleSet and
dependencySet to deal w/ classifiers; they seem blind unless I try and call
out what to include individually (failed trying to do this too).
Giving up on this avenue. Going to add to our version.
> 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
>
>
> 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
