[
https://issues.apache.org/jira/browse/HIVE-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634624#comment-13634624
]
Owen O'Malley commented on HIVE-4305:
-------------------------------------
Carl, I fully acknowledge that ant vs maven is a religious discussion. However,
to back up my five points:
* IDE support is much better
>From http://www.jetbrains.com/idea/features/ant_maven.html :
Maven integration reads the files and builds the modules and dependencies
between them.
Ant integration executes ant targets.
This is similar to eclipse too. For Maven projects, you don't need to maintain
a set of helper files that set up the project in the IDE. They can build it
automatically. Even with our eclipse helper scripts, users give up on building
Hive in an IDE.
* Offline support is much better
Try turning off the internet and build Hive. It is relatively difficult. Maven
will just work if you have the required jars in your cache.
* You can download a Maven project and build it without reading the build file.
This is obviously true from the fundamentals of each system. Ant provides a
wide open playing field and you can build "tar" in one project and "package" in
another. There are no rules. In Maven, I know what "package" will build.
* Publishing to Maven central is much easier.
Ivy can't publish to Maven central, so you end up use ant's maven tasks to
publish. This requires that you have two different descriptions of the projects
dependencies one for ivy and one for ant's maven tasks. Furthermore, based on
my experience as the release manager for Hadoop, ant's maven tasks are much
more error-prone. Futhermore, they don't support features like storing your
password encrypted.
* Profiles work much better in Maven.
Ok, this one is debatable. In my opinion, Maven profiles are cleaner and better
designed.
Finally, I fully support Brock's point:
* Maven is used by the other Hadoop ecosystem projects.
Hadoop in particular was using ant, ivy, and maven ant tasks for a long time
and traded them in for Maven. There is significant value in using similar tools.
> Use a single system for dependency resolution
> ---------------------------------------------
>
> Key: HIVE-4305
> URL: https://issues.apache.org/jira/browse/HIVE-4305
> Project: Hive
> Issue Type: Improvement
> Components: Build Infrastructure, HCatalog
> Reporter: Travis Crawford
>
> Both Hive and HCatalog use ant as their build tool. However, Hive uses ivy
> for dependency resolution while HCatalog uses maven-ant-tasks. With the
> project merge we should converge on a single tool for dependency resolution.
--
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
