Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # user >> I wonder why split the project

Copy link to this message
Re: I wonder why split the project
Though I should probably ask this question on the dev list, but since
we are talking about it here, let me ask it.

I had a patch for a JIRA which have a few file changes in the common
and the rest in the mapreduce sub-project.  Now after this split into 3,
I am wondering that how I make a new patch?

(a) Should I make two separate patches (one for common and the other
for mapreduce) and also make a new JIRA in mapreduce and link the
two JIRAS and post the respective patches there.

(b) Make two patches and merge them and submit on the current JIRA.
But then the question is that will Hudson run it correctly if it has files
related to two different sub-projects?

Thanks for helping me out of this.

Abdul Qadeer

On Tue, Jul 14, 2009 at 4:21 AM, Edward J. Yoon <[EMAIL PROTECTED]>wrote:

> Have you thought about the Maven project management model?
> And, I thought, the slow running time of integration tests and the
> large source tree also were problematic.
> On Mon, Jul 13, 2009 at 2:52 PM, 김대현<[EMAIL PROTECTED]> wrote:
> > Hello.
> >
> > I saw the svn last week,
> > the project is splited to common, hdfs, mapreduce.
> >
> > I'd like to know the reason why split the project.
> > I can find the reason in the web page of hadoop.
> >
> > please someone tell me :)
> >
> --
> Best Regards, Edward J. Yoon @ NHN, corp.
> http://blog.udanax.org