On Jul 16, 2009, at 3:54 AM, Giridharan Kesavan wrote:
2) Publishing artifacts to the people.apache.org
ssh resolver is configured which publishes common/hdfs/mapred
artifacts to my home folder /home/gkesavan/ivyrepo
I think that publishing to your home directory is a mistake. We need
[mailto:sc...@richrelevance.com]
Sent: Thursday, July 02, 2009 10:32 PM
To: common-dev@hadoop.apache.org
Subject: Re: Developing cross-component patches post-split
On 7/1/09 11:58 PM, Nigel Daley nda...@yahoo-inc.com wrote:
On Jul 1, 2009, at 10:16 PM, Todd Lipcon wrote:
On Wed
I have been using ivy for a multi-module project which have similar
independent modules built separately.
I think the way to got is like :
1. Let the projects be checked out independently and in arbitrary
directory structure
2. Define ivy repositories in the following order : local, maven
3.
For example,
ant test
does the same as it does now, but
ant -Dhadoop.common.jar=/home/dhruba/common/hadoop-common.jar test will
pick up the common jar from my home directory.
+1; we'll also need the same sort of thing for the daemons.
Regardless of whether or not jars are checked in,
On Wed, Jul 1, 2009 at 6:45 PM, Todd Lipcontlip...@gmail.com wrote:
Agree with Phillip here. Requiring a new jar to be checked in anywhere after
every common commit seems unscalable and nonperformant. For git users this
will make the repository size baloon like crazy (the jar is 400KB and we
On 7/1/09 11:58 PM, Nigel Daley nda...@yahoo-inc.com wrote:
On Jul 1, 2009, at 10:16 PM, Todd Lipcon wrote:
On Wed, Jul 1, 2009 at 10:10 PM, Raghu Angadi rang...@yahoo-
inc.com wrote:
-1 for committing the jar.
Most of the various options proposed sound certainly better.
Can
On Wed, Jul 1, 2009 at 10:10 PM, Raghu Angadi rang...@yahoo-inc.com wrote:
-1 for committing the jar.
Most of the various options proposed sound certainly better.
Can build.xml be updated such that Ivy fetches recent (nightly) build?
This seems slightly better than actually committing the
