tag:blogger.com,1999:blog-2968924507928694867.post2927817623531546060..comments2023-07-27T21:21:13.643+05:30Comments on The Portal Zone: Ant + Ivy = Maven ?navaneethhttp://www.blogger.com/profile/13353327711519176349noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-2968924507928694867.post-53873131051398450962010-06-23T20:02:04.829+05:302010-06-23T20:02:04.829+05:30I use ant + ivy + a set of importable ant build fi...I use ant + ivy + a set of importable ant build files that reproduce part of the maven process. I wonder if this set of importable build files already exists as a project somewhere or whether someone is interested in making this a project.<br /><br />For example, I make a java project by putting my code in src/main/java and src/test/java. I create an ivy.xml file and a build.xml file. Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-9612016765045414632008-01-03T19:18:00.000+05:302008-01-03T19:18:00.000+05:30Even though comparing Ant+Ivy and Maven 2 comes ou...Even though comparing Ant+Ivy and Maven 2 comes out very often, you really can't say that Ant+Ivy = Maven.<BR/><BR/>Both tools can be used to achieve very similar purpose, but in very different ways: with Maven you describe your project and let the tool drive your build, with Ant+Ivy you describe your build process with the help of the tools to deal with hard problems like dependency management Anonymoushttps://www.blogger.com/profile/06817947075459199523noreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-67568362489748620242008-01-02T17:33:00.000+05:302008-01-02T17:33:00.000+05:30Although I've never really used Maven neither Ivy,...Although I've never really used Maven neither Ivy, I think (by all the reading) both are different products that overlap in a very visible feature: dependency management.<BR/>In Ivy, this is the main feature, in Maven not. So the confusion arises.<BR/><BR/>The post title is a question about how this feature overlap affects both products as an effort division, not about the products themselves.CyberMandrakehttps://www.blogger.com/profile/07147374209560468214noreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-11391427303956074662008-01-01T20:06:00.000+05:302008-01-01T20:06:00.000+05:30Maven 2 (not Maven 1, because that was a prototype...Maven 2 (not Maven 1, because that was a prototype that made it into production) is a lot more then ant+ivy.<BR/>However, the best thing it did for us, is standardizing the build lifecycle (although you can easily customize it if you know how).<BR/>If an open source project uses maven 2, I do the effort to provide patches, otherwise I don't. Why?<BR/>I can check it out, build it (="mvn install"),Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-38271413410121963092008-01-01T15:07:00.000+05:302008-01-01T15:07:00.000+05:30I agree with the previous poster. Ant+Ivy != Maven...I agree with the previous poster. Ant+Ivy != Maven, because Ant+Ivy is by far more superior. Maven is good as long as you follow the Maven way. But just try to create a build environment that is not quick-and-dirty and more professional (let's say with a serious staging model (development,integration,qs,prductive for example) and recreatable builds (this includes the used dependency versions for Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-22218715343574011092008-01-01T04:29:00.000+05:302008-01-01T04:29:00.000+05:30I think if you look at the entire scope of what Ma...I think if you look at the entire scope of what Maven brings to the table you can see that Ant+Ivy != Maven.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-37436230920040362692007-12-30T09:41:00.000+05:302007-12-30T09:41:00.000+05:30Ignacio,I have a different point of view. I don't ...Ignacio,<BR/><BR/>I have a different point of view. I don't mind the magic in the build scripts as long as I understand what that magic is. But as you rightly put, the more you deviate from "The Maven Way" of doing things, the worse you are.<BR/><BR/>I currently use Maven. But fortunately I am not doing anything different from the standard functionality. There are a few nits and I have addressednavaneethhttps://www.blogger.com/profile/13353327711519176349noreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-52092810838706221592007-12-29T22:02:00.000+05:302007-12-29T22:02:00.000+05:30Many people think that magic in the integration bu...Many people think that magic in the integration build should be kept to a minimum. Ant scripts show what is being done, but maven does not. I don't like the amount of CoC that has been bundled into the maven environment (too much reading to get something done), and I don't think the 90-10 rule is correctly applied in maven. When you need something that breaks The Maven Way the amount of extra Anonymoushttps://www.blogger.com/profile/02874466783900738920noreply@blogger.com