[
https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Steinbach updated HIVE-1095:
-
Status: Open (was: Patch Available)
> Hive in Maven
> -
>
>
410: Unable to initialize POM
hive-${hive.project}-0.6.0.pom:
Could not find the model file
'/Users/carl/Projects/hive/build/maven/poms/hive-${hive.project}-0.6.0.pom'.
for project unknown
Total time: 5 seconds
{code}
It looks like the make-pom target needs to depend on ivy
[
https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Sichi updated HIVE-1095:
-
Fix Version/s: (was: 0.6.0)
> Hive in Maven
> -
>
> Ke
[
https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerrit Jansen van Vuuren updated HIVE-1095:
---
Status: Patch Available (was: Open)
> Hive in Ma
st be applied for, the
https://issues.apache.org/jira/browse/INFRA-1896 tasks contains the information
on how to go about this, with some reference documentation links.
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https://is
prepare-maven-publish
The maven directory structure will be in build/maven/ containing
poms,jars,licences folders.
I'll write a comment on the different deployment strategies.
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https
[
https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerrit Jansen van Vuuren updated HIVE-1095:
---
Attachment: (was: HIVE-1095-trunk.patch)
> Hive in Ma
[username]:[passwo...@people.apache.org:/www/people.apache.org/repo/m1-ibiblio-rsync-repository/org/apache/hadoop/hive/
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https://issues.apache.org/jira/browse/HIVE-1095
> Project: Had
[
https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerrit Jansen van Vuuren updated HIVE-1095:
---
Attachment: (was: HIVE-1095-0.4.1.patch)
> Hive in Ma
[
https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerrit Jansen van Vuuren updated HIVE-1095:
---
Attachment: (was: HIVE-1095-Sample.patch)
> Hive in Ma
[
https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerrit Jansen van Vuuren updated HIVE-1095:
---
Status: Open (was: Patch Available)
Making new patch release
> Hive
So then we have:
-> Patch for trunk as Hive-1095-trunk.patch
-> I'll generate the ant script to do the hive for verions 0.4.1 and 0.5
How does that sound?
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https://issues.ap
for 0.3.0 and 0.4.0 could be skipped.
Generally we have been applying most changes to trunk and sometimes the latest
branch.
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https://issues.apache.org/jira/browse/HIVE-1095
>
l include a little ant build.xml to do this).
Then we only have to worry about commit on the trunk. using
Hive-1095-trunk.patch.
Any thoughts?
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https://issues.apache.org/jira/browse/HIVE-10
the patches for
the builds on the other versions of hive also, should I do this and attach to
this task?
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https://issues.apache.org/jira/browse/HIVE-1095
> Project: H
atch after review (not commit)
Does this mean the patch need to regenerated after any conflicting changes?
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https://issues.apache.org/jira/browse/HIVE-1095
> Project: Hadoop Hive
Affects Version/s: 0.6.0
Status: Patch Available (was: Open)
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https://issues.apache.org/jira/browse/HIVE-1095
> Project: Hadoop Hive
> Issue Type: Task
others expect that its for the current
hive trunk.
It also used ${version} inside the ivy.xml files to be more generic.
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https://issues.apache.org/jira/browse/HIVE-1095
> Pr
[
https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerrit Jansen van Vuuren updated HIVE-1095:
---
Attachment: HIVE-1095-0.4.1.patch
> Hive in Ma
?
-> Would somebody be able to apply this patch after review (not commit) but
just to generate the jars,poms for the hive-4x release to deploy this to maven
and then for the hive-5x release?
> Hive in Maven
> -
>
> Key: HIVE-1095
> U
alone:
-> Download the artifactory zip at
http://sourceforge.net/projects/artifactory/
-> run bin/artifactory.sh
As a WAR:
-> Download the zip file
-> copy to webapps/artifactory.war to tomcat or jetty.
Setup is done via the artifactory admin window:
defaults are: username: admin pa
)
> Hive in Maven
> -
>
> Key: HIVE-1095
> URL: https://issues.apache.org/jira/browse/HIVE-1095
> Project: Hadoop Hive
> Issue Type: Task
> Components: Build Infrastructure
>Reporte
Hive in Maven
-
Key: HIVE-1095
URL: https://issues.apache.org/jira/browse/HIVE-1095
Project: Hadoop Hive
Issue Type: Task
Components: Build Infrastructure
Affects Versions: 0.4.1
Reporter: Gerrit Jansen
Yes you should open a JIRA for this.
Ashish
-Original Message-
From: Gerrit [mailto:gvanvuu...@specificmedia.com]
Sent: Friday, January 22, 2010 7:33 AM
To: hive-dev@hadoop.apache.org
Subject: Re: Hive in maven
Hi,
Yes I'll start on creating the pom.xml
The fastest and recomm
Hi,
Yes I'll start on creating the pom.xml
The fastest and recommended way of doing this is by having a maven repo
and sync it with the official maven repos (one way ). Also future hive
releases would be just a matter of loading to this repo and its
automatically synced with the official maven re
Hi Gerrit,
Can you help uploading to maven?
Thanks
Yongqiang
On 1/20/10 2:21 AM, "Gerrit" wrote:
> Yep:
>
> The main maven page is:
> http://maven.apache.org/guides/mini/guide-central-repository-upload.html
> (see section
> Sync'ing your own repository to the central repository automatically)
Yep:
The main maven page is:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
(see section
Sync'ing your own repository to the central repository automatically)
For groupId and artifactId conventions see:
http://maven.apache.org/guides/mini/guide-naming-conventions.html)
This is a good idea. Can you point us to some references on how to upload it
to maven?
Zheng
On Mon, Jan 18, 2010 at 1:20 PM, Gerrit wrote:
> Hi guys,
>
> Would it be possible to add the hive jars to the main maven repo? If
> there is not objections I can make the request to the main repo if you
Hi guys,
Would it be possible to add the hive jars to the main maven repo? If
there is not objections I can make the request to the main repo if you
agree.
The reason for this need is that I've created a Loader for the pig
project to read HiveRCTables
(https://issues.apache.org/jira/browse/PIG-1
29 matches
Mail list logo
