Drew Farris wrote:
On Fri, Apr 2, 2010 at 8:23 AM, Enis Söztutar enis@gmail.com wrote:
.Do we have any build-specific reason that cannot be done with ivy.
It can be done with ivy, but it's generally far more manageable to do
everything with maven because there is considerably less
On 04/01/2010 09:09 PM, Giridharan Kesavan wrote:
I would like call for a vote to created a development branch of common
trunk to work on mavenizing hadoop common.
-Giri
+1 for exploring, but my previous experience with Maven made me switch
back to ant+ivy. Maven is great, but ant+ivy is
On Fri, Apr 2, 2010 at 8:23 AM, Enis Söztutar enis@gmail.com wrote:
.Do we have any build-specific reason that cannot be done with ivy.
It can be done with ivy, but it's generally far more manageable to do
everything with maven because there is considerably less configuration
required. Less
Maven could also give us a more robust eclipse-files target based off of
the dependencies as defined in pom.xml, and possibly
assemble-projects-eclipse and assemble-projects-dist targets which could
pull down into an eclipse workspace or a distribution directory that was all
wired together and
I would like call for a vote to created a development branch of common
trunk to work on mavenizing hadoop common.
-Giri
+1 -C
On Thursday, April 1, 2010, Giridharan Kesavan gkesa...@apache.org wrote:
I would like call for a vote to created a development branch of common
trunk to work on mavenizing hadoop common.
-Giri
+1 for exploring. HBase TRUNK is now mavenized. Has kinks still but
its getting there. Will see if can get some of the experts hanging
in hbase space to help out with this effort.
St.Ack
On Thu, Apr 1, 2010 at 7:34 PM, Chris Douglas cdoug...@apache.org wrote:
+1 -C
On Thursday, April 1,
