Discussions

News: Maven 2.0.7 Released

  1. Maven 2.0.7 Released (45 messages)

    The Apache Maven team would like to announce the availability of Maven 2.0.7. This is the third maintenance release within 4 months and we are rapidly approaching our goal of providing maintenance releases on a monthly basis. The 2.0.8 release is scheduled and we are now trying to provide all relevant information about Maven development in one location so users can easily tell what's happening with Maven at any point in time. You can find the binaries here: http://maven.apache.org/download.html You can find the release notes here: http://maven.apache.org/release-notes.html You can find the roadmap here: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=13010&sorter/field=issuekey&sorter/order=DESC Enjoy, Jason van Zyl Founder, The Apache Maven Project

    Threaded Messages (45)

  2. Re: Maven 2.0.7 Released[ Go to top ]

    I really like the idea of maven but in practice it just does not work. Can we please go back to writing ant files ?
  3. Re: Maven 2.0.7 Released[ Go to top ]

    I really like the idea of maven but in practice it just does not work.
    Perhaps it would be useful to the people who wrote Maven if you would actually provide something factual about what "doesnt work" for you so that they could respond to it and help you with any possible misunderstandings ...
    Can we please go back to writing ant files ?
    You could go back to using "make" if you want. Nobodys stopping you :-P
  4. Re: Maven 2.0.7 Released[ Go to top ]

    This seems like a BS response. It it doesn't work then specify with detail how and where it fails to function. It may be lack of knowledge on your part or a genuine defect on Maven's part. However from your comment we'll never know.
  5. I really like the idea of maven but in practice it just does not work. Can we please go back to writing ant files ?
    yeah, that was just _packed_ with merit... Let's start discussion :D
  6. Re: Maven 2.0.7 Released[ Go to top ]

    We use maven at our place, and I think it's great, but I also think it has too many bugs. For instance: This bug is marked as fixed, but it was still broken in 2.0.6 http://jira.codehaus.org/browse/MNG-2900 I had to upgrade then downgrade. Now I'm afraid to upgrade because I see no activity on the so called fixed bug and it's probably still there.. Maven works for me, but I also have to support other developers with their use of Maven, and that's not easy. I figured out how to use it, but I have to explain everything because the documentation does not seem enough. Any news on the Maven Eclipse integration? http://jira.codehaus.org/browse/MNGECLIPSE I'm really looking forward to the new release (0.0.11), but the project looks abandoned. Currently I cannot use it because it's not possible to change the location of the local maven repository and the default does not work for me... This is another bug, not a missing feature. Thanks, C.
  7. Re: Maven 2.0.7 Released[ Go to top ]

    I also really like the idea of Maven, and I also agree that in practice it just doesn't keep up to its promises. Even seemingly simple things (like convincing the assembly plugin to do what I'd like it to do) often takes hours of frustrating Googling/debugging/trial-and-error. Now I have the whole Maven workspace and all its major plugins checked out, so that I can run Maven under the debugger --- I suspect anyone doing anything non-trivial is doing just the same as me, and that is often the only way to figure out how to use it. Then there's this verbosity of POM. The fact that it's XML is already a significant source of verbosity, but Maven makes it worse by designing the XML for programs (to make DI easier.) There's no attributes used anywhere, every repeatable elements need to be wrapped into the plural '' wrapper, etc. The really sad thing for me is that despite all these problems, all too often Maven is the only tool for the job. As someone else already posted, when you have a large number of "modules" that are built in similar way, or dozen or so small independent projects, Ant is just not an option. And I suspect I'm not alone in not liking Maven. See http://blog.labnotes.org/2007/04/18/introducing-buildr-or-how-we-cured-our-maven-blues/ for example. Or just Google keywords like "hate Maven" or "Maven sucks".
  8. Re: Maven 2.0.7 Released[ Go to top ]

    Even seemingly simple things (like convincing the assembly plugin to do what I'd like it to do) often takes hours of frustrating Googling/debugging/trial-and-error.
    That is why convention over configuration is a preferred way. Assembly and ant runner plugins are more like hacks to help to port some legacy stuff...
    Then there's this verbosity of POM. The fact that it's XML is already a significant source of verbosity, but Maven makes it worse by designing the XML for programs (to make DI easier.) There's no attributes used anywhere, every repeatable elements need to be wrapped into the plural '' wrapper, etc.
    That is relatively easy to fix, because in Maven internals everything is pluggable and I suspect you actually good candidate to do this work, given your experience. ;-)
    The really sad thing for me is that despite all these problems, all too often Maven is the only tool for the job.
    I really hope you won't take a traditional patch of reimplementing thing from scratch (it is a compliment, btw) and will contribute some cool stuff to Maven project. :-)
  9. I also really like the idea of Maven, and I also agree that in practice it just doesn't keep up to its promises.

    Even seemingly simple things (like convincing the assembly plugin to do what I'd like it to do) often takes hours of frustrating Googling/debugging/trial-and-error. Now I have the whole Maven workspace and all its major plugins checked out, so that I can run Maven under the debugger --- I suspect anyone doing anything non-trivial is doing just the same as me, and that is often the only way to figure out how to use it.

    Then there's this verbosity of POM. The fact that it's XML is already a significant source of verbosity, but Maven makes it worse by designing the XML for programs (to make DI easier.) There's no attributes used anywhere, every repeatable elements need to be wrapped into the plural '' wrapper, etc.

    The really sad thing for me is that despite all these problems, all too often Maven is the only tool for the job.
    I think it because Maven 2 uses its own lightweight xml parser to overcome the slowness experienced with Maven 1. I remember reading that they were going to port Maven to a stax xml parser in a subsequent release.
  10. Re: Maven 2.0.7 Released[ Go to top ]

    The Assembly Plugin, by a considerable degree, is larger and more complex then any other plugin. The only plugin as complex is the release plugin so putting an assembly together is not a super simple task ... there are 25 pages on the site dedicated to making assemblies (http://maven.apache.org/plugins/maven-assembly-plugin/). People always forget that the POM is not strictly procedural and if it's easier to use a Ant script to wire up an assembly then you can with the Ant Run plugin and the use the Build Helper Plugin to integrate it into the rest of the process by attaching your assembly (http://mojo.codehaus.org/build-helper-maven-plugin/howto.html). As to the verbosity, it's a big complaint. Not falling on deaf ears though: http://docs.codehaus.org/display/MAVEN/Terse+POM+Syntax+-+Design+Discussion . This will be something we mostly likely tackle in 2.1 as result of feedback from users. Much like the evolution of the Spring configuration format which users bitched about while resulted in a change. We will likely do the same thing. I don't think anyone is religious about the format we just need to make the new and old work. While trying to tackle these problems for all users we are obviously going to run into some serious short comings. You can always fall back to Ant via the Ant Run plugin which has been available for a long time and provides a work around for almost anything. It will also soon be possible to do something similiar with JRuby and Groovy. So if you need to fall back on the power of scripting for some custom portions, or work around crap that just doesn't work you can. It is a fallacy that you are trapped with only the declarative POM. So let's not throw out the baby with the bath water. I fully admit to there being a lot of bugs, but we have a lot of users and we still don't have that many full-time people working on the core. This is something I'm working on remedying but it takes time and my first effort failed. There is myself, John Casey, Kenney Westerhof, Andy William, and Brett Porter who understand the intimate gory details of the core and that in reality translates to 2 full-time people when it boils down to actual time spent on core work and documentaton. I don't imagine this is much different with Ant. And can anyone remember back to the days of trying Ant a couple years into its life? It wasn't pretty either (I'm just ignoring that Maven 1.x ever existed). Software which serves common infrastructures is hard work. We'll eventually get there. As long as Sun doesn't try to reimplement Maven we'll all survive the ordeal. To be honest many of the problems stem from plugins which we simply don't have full control over given the completely distributed model we have. Also the reference to the BuildR is somewhat misleading as that post is generally a vitriolic diatribe by Ruby zealot who thinks he likes to write build systems. Everyone thinks they like to write build systems until they have users who aren't their friends (You would be amazed at how much you can mitigate the deleterious effects of your crappy build system with free beer and fart jokes. Tip: don't do this in the UK unless you have very few friends, or are independenty wealthy). If you look at the script offered as a solution, which would be incomprehensible to people using Java, then you have some perspective. Ruby is not a panacea and not every Java programmer should be forced to learn Ruby to build something (I use Ruby everyday and love it, so I'm not a rabid Ruby hater either). That's not to say there aren't people who get completely pissed with Maven and take drastic measures. It's unfortunate people react like this for in this particular case of BuildR the embedder can be used from JRuby like so: require 'java' class Maven def initialize goals @goals = goals end include_class 'java.io.File' include_class 'org.apache.maven.embedder.MavenEmbedder' include_class 'org.apache.maven.embedder.DefaultConfiguration' include_class 'org.apache.maven.execution.DefaultMavenExecutionRequest' def run configuration = DefaultConfiguration.new maven = MavenEmbedder.new(configuration) r = DefaultMavenExecutionRequest.new r.setBaseDirectory( File.new( "." ) ) r.setGoals( @goals ) result = maven.execute( r ); end end m = Maven.new( ["clean"] ).run And Maven can be utilized for anything deemed useful by the Lords of Ruby. And for cases outside the Maven command line proper I would be happy to provide an option to do non-transitive dependency resolution which could be accessed via the embedder. Then you can list all the dependencies you like. Not being able to disable transitive dependency resolution was another justification they had for writing BuildR. It would be a 10 line addition to Maven's core to add this. The critique the BuildR fellow had was perfectly valid, though erroneous in several places, and if it helps a few guys from Intatlio build Apache ODE then all the power to them but I'll be clear in that BuildR solves none of the problems that Maven sets out to solve insofar as providing a solution for building projects for as many disparate groups as possible. Attempting to satisfy everyone who is trying to use a tool in a common way is not easy. If Maven makes you want to shove bamboo under your own fingernails then don't use it. Use Ant , BuildR or whatever causes less Build Flatulence (BF).
  11. Re: Maven 2.0.7 Released[ Go to top ]

    IMHO, Maven is a good tool. I think people should use Ant with the ant-lib plugin, if Maven is considered too complicated for their purpose. I think that a tool complexity should be faced only to have a gain; but if you must build-and-deploy only litle and simple projects, managed by 1 or 2 programmers, the whole Maven world could be an obstacle.
  12. Re: Maven 2.0.7 Released[ Go to top ]

    IMHO, Maven is a good tool.
    I think people should use Ant with the ant-lib plugin, if Maven is considered too complicated for their purpose.

    I think that a tool complexity should be faced only to have a gain; but if you must build-and-deploy only litle and simple projects, managed by 1 or 2 programmers, the whole Maven world could be an obstacle.
    I dont think so, the entire dependency resolution can save a lot of time, the project kickstarters as well. I personally only see real problems, if the projects cannot follow the maven structure guidlines.
  13. Re: Maven 2.0.7 Released[ Go to top ]

    I'm indeed using the antrun plugin in many of the projects as a fallback, but I felt it's actually fairly disconnected with the rest of the maven world to be a really useful fallback. For example, if I were to use it to assemble a zip file, I need to access dependency jars (which is only available as a Path-like structure), and I needed to be able to attach the result as an artifact (which requires another plugin.) It's workable, but the effort it takes to use it is often quite non-trivial. I think the officially blessed BSF plugin would be a better fallback tool, and so I'm happy to see that you mentioned it. In any case, it's good to hear that the Maven team is aware of these perceived problems and plan to work on them. And as long as I have your ears, I hope you examine Buildr little more carefully, instead of just dismissing it like that. The core idea that really appealed to me was that it manages to bridge the declarative world and the procedural world very smoothly, which definitely cannot be said with Maven so far. Whether it's implemented in Ruby or not is not that important. I can easily see this implemented in Groovy, JavaScript, or any other script languages of the day. You are right to question whether Buildr itself can be a practical "cure for maven blues", but there are some pretty good ideas in it.
  14. Re: Maven 2.0.7 Released[ Go to top ]

    Then there's this verbosity of POM.
    Yes, I was wondering if maven team belongs to that philosophical xml thinking, where attributes are a bad thing. The truth obviously (and I repeat obviously) stays on the middle...noalways attributes, but use them when they are suited.
  15. Re: Maven 2.0.7 Released[ Go to top ]

    My critic to Maven2 is about the plugins management: why does my local repository (.m2/repository ) contain together plug-ins libraries (with SNAPSHOTs....) and dependencies jars? I think that a good maven improving feature should be to provide a mechanism to divide two repository, thus I could separate and zip all the plug-ins needed to Maven to compile/deploy and provide that zip independently from my own libraries. Bye.
  16. Re: Maven 2.0.7 Released[ Go to top ]

    I really like the idea of maven but in practice it just does not work. Can we please go back to writing ant files ?
    I haven been using maven for quite a while in various oss projects and have been moving it into my own projects recently. The funny thing was although some of those projects did weird things and maven sometimes felt weird in usage I was able to pull everything together in a reasonable amount of time. And I cannot really agree here, once you move towards the mentality of having maven deal with your project structure instead of rolling your own things become easier. Massols maven book also helps a lot. But I can see szenarios where it simply cannot work without an ant fallback. Most of them have to deal with enforce project szenarios. But even then the maven2 plugin api seems simple enough so that rolling your own plugin for such cases seems like a non issue.
  17. Doesn't work...[ Go to top ]

    Nobody forces you into loving Maven. But it works for others. I don't even want to mention the amount of custom coding and hacks required to enforce consistent rules and conventions for a nearly 100-module project. Guess what, it is the nature of m2 to handle such scenarios. I don't mean it doesn't have problems, but when you go large-scale, none of the tools would work OOTB, it's only a matter of choosing what's best suited for the job given all the input.
  18. Re: Maven 2.0.7 Released[ Go to top ]

    With my previous tests and application, Maven troubled me on "Transitive Dependency" Hierarchy and some ugly poms in central repository (also related to Transitive Dependency). So I'm concerning on the issues.
  19. Maven is the best[ Go to top ]

    I love maven and use it on all my projects. It is the best.
  20. Maven is the worst[ Go to top ]

    I hate Maven. It is unusable. I try to do something weird with it and it becomes hard. Everybody who is using it and likes it are fools.
  21. Re: Maven is the worst[ Go to top ]

    You are not smart for having the opinion you have on Maven.
  22. Re: Maven is the worst[ Go to top ]

    I hate Maven. It is unusable. I try to do something weird with it and it becomes hard. Everybody who is using it and likes it are fools.
    But I find it useful. It took me awhile to learn how to use it but it is nice having all my builds the same.
  23. Re: Maven is the worst[ Go to top ]

    I hate Maven. It is unusable. I try to do something weird with it and it becomes hard. Everybody who is using it and likes it are fools.


    But I find it useful. It took me awhile to learn how to use it but it is nice having all my builds the same.
    Bah, for my company I need much more flexibility and control than Maven provides. It's Ant all the way for me and should be for you too.
  24. Re: Maven is the worst[ Go to top ]

    I hate Maven. It is unusable. I try to do something weird with it and it becomes hard. Everybody who is using it and likes it are fools.


    But I find it useful. It took me awhile to learn how to use it but it is nice having all my builds the same.


    Bah, for my company I need much more flexibility and control than Maven provides. It's Ant all the way for me and should be for you too.
    But isn't that the point? If your needs fit into Maven's wheelhouse then life is easy. I haven't had to worry about writing my own build file for years.
  25. Re: Maven is the worst[ Go to top ]

    I hate Maven. It is unusable. I try to do something weird with it and it becomes hard. Everybody who is using it and likes it are fools.


    But I find it useful. It took me awhile to learn how to use it but it is nice having all my builds the same.


    Bah, for my company I need much more flexibility and control than Maven provides. It's Ant all the way for me and should be for you too.


    But isn't that the point? If your needs fit into Maven's wheelhouse then life is easy. I haven't had to worry about writing my own build file for years.
    Well, that may work for you in your so-called development shop. At my company we do things in a much more impressive and powerful way. Therefore we've abandoned Ant and are doing all our builds in lisp.
  26. Re: Maven is the worst[ Go to top ]

    You guys are going to keep this trolling going? I'd think that after the first two posts you'd see that this guy either suffers from a brain disability and/or is trolling.
  27. Re: Maven is the worst[ Go to top ]

    Ah, I guess you got me pretty good:-) Haha, I didn't even realize you were the one posting all of this. Sorry, that does sound like an imitation of maven posts:-)
  28. Re: Maven is the worst[ Go to top ]

    George, that is hilarious! :D
  29. Re: Maven is the blurst[ Go to top ]

    Ah, I guess you got me pretty good:-) Haha, I didn't even realize you were the one posting all of this. Sorry, that does sound like an imitation of maven posts:-)
    No problem. I had a few beers last night while catching up on my TSS and figured I'd save all the other trolls the work of the typical Maven relase post. I'm glad people got the joke. BTW: I actually do like Maven2 when it fits the project and especially when I already have all the required libraries in my .m2 repository. I've had some troubles with it too but I'd have to say the same for almost every OSS technology I've used lately: XFire, iText, Prototype etc. Sometimes it isn't worth throwing something away even if it is a bit buggy - sometimes it is.
  30. Re: Maven is the worst[ Go to top ]

    I do not agree. I used maven since versione 2.0.4 and, really, there were too many bugs, thus it did not work very well. But now many bugs have been fixed, it works. I like very much the library dependency mechanism, and the transitive dependency in particular. Many features are good, I like the possibility to make a "Standard" site for my project, to link the site to Jira and SVN. If you don't like maven, I suggest you two things: - use only the ant-lib library, that's the ant plugin to manage the jars dependency; - take a look to Apache Ivy (now in alpha version). I think maven now is a good product, you cannot ignore it. All the world OpenSource java community is migrating to maven. Surely it will be very soon the standard de-facto for managing projects life-cycle in Java (Standard Convention ->Build ->Site (documentation) ->test).
  31. - take a look to Apache Ivy (now in alpha version)
    version 2 is in alpha but 1.x line is stable and mature product donated to apache by jayasoft. IMO IVY dependency resolution is far superior to Maven's dependency resolver.
  32. Re: Maven is the worst[ Go to top ]

    IMO IVY dependency resolution is far superior to Maven's dependency resolver.
    Can you give any specifics?
  33. Re: Maven is the worst[ Go to top ]

    IMO IVY dependency resolution is far superior to Maven's dependency resolver.
    Can you give any specifics?
    Easy to understand what come from and why thanks to extensive reporting; Easy to bring dependencies to local directories and rename (strip them of versions) if necessary.
  34. Re: Maven is the worst[ Go to top ]

    IMO IVY dependency resolution is far superior to Maven's dependency resolver.
    Can you give any specifics?

    Easy to understand what come from and why thanks to extensive reporting;
    Easy to bring dependencies to local directories and rename (strip them of versions) if necessary.
    Pretty much the same is true for maven once you understand the concepts well.
  35. Re: Maven is the worst[ Go to top ]

    ..Pretty much the same is true for maven once you understand the concepts well.
    Unfortunately it is not enough to understand concepts -they are sound and fine. Implementation however is unstable and quite obscure - it is not easy to trace why certain things happening or do not happening , Maven feels blackboxy. Ant might be verbose but it is easy to understand and trace. IMO build tool just must work, it must not cause people feel uncertain about outcomes - verbose, not-that convenient, lack functionality - I can tolerate those things - obscurity and unpredictability - no thanks.
  36. Re: Maven is the worst[ Go to top ]

    ..Pretty much the same is true for maven once you understand the concepts well.

    Unfortunately it is not enough to understand concepts -they are sound and fine. Implementation however is unstable and quite obscure - it is not easy to trace why certain things happening or do not happening , Maven feels blackboxy.

    Ant might be verbose but it is easy to understand and trace. IMO build tool just must work, it must not cause people feel uncertain about outcomes - verbose, not-that convenient, lack functionality - I can tolerate those things - obscurity and unpredictability - no thanks.
    Explain please, where is the obscurity in maven dependency resolution? You have remote and local repos, you can specify whether to use a particular version or snapshots, etc..., you can easily install your own version into your local repo and force maven to utilize it if you're not comfortable with seeking newer releases each time. I'm not sure what you mean by blackboxy, the fact that it does things for you declaratively and implicitly without having to use ant (yet another xml language) to script your build explicitly? No thanks, I'd rather start working on the core of the code than to spend days setting up a viable build. I still find many uses for ant, in cases where the project is a non standard java, webapp project and needs a lot more flexibility which can be achieved with maven, but doesn't save any time, for any standard java based project, maven rocks. Ilya
  37. Re: Maven is the worst[ Go to top ]

    I still find many uses for ant, in cases where the project is a non standard java, webapp project and needs a lot more flexibility which can be achieved with maven, but doesn't save any time, for any standard java based project, maven rocks...
    I often want to do or try something not quite standard and cannot find easily if I can do it with Maven or I need to resort to Ant. With Ant there is no uncertainty - I know I can do anything I want ( I might not need it after all, but if I want I can). Even for standard Java projects - Maven dependency resolution works predictably only if artifacts and and plugin repositories are tightly controlled too. I cannot override dependency in the chain or exclude some from command line - therefore messing with repository and POMs there is necessary.
  38. Re: Maven is the worst[ Go to top ]

    This page list some of desirable features http://docs.codehaus.org/display/MAVENUSER/Improving+Maven2+Dependency+Resolution And I think that most of them kind of obvious and well known: for example Gentoo handles complex dependency graphs pretty gracefully and allows all sorts of overrides thus putting developers on control when necessary - there is much to learn and copy. I wish we had something like this in Java world...
  39. Re: Maven is the worst[ Go to top ]

    Learning ivy it's 10 mins. And IT SIMPLY WORKS. I have been using maven daily, for about 2 years but new problems arise every day, or lasts indefinitely. And finding problems cause it's so awfully painfull...
  40. Re: Maven is the worst[ Go to top ]

    Do not agree. I think if you want to use simply a dependency mechanism in your project, the best solution is ant-lib, the maven plugin for ant. It works well and it is very simple to understand (10 minutes!).
  41. Re: Maven 2.0.7 Released[ Go to top ]

    I helped move my current organization to maven about 8 months ago and I have to say that, so far, it's not too bad. Like most OSS projects, though, it wasn't a smooth transition. Lots of bugs. Lots of quirky behavior. Also, lots of unimplemented features. In my mind, Maven is kinda lame without Archiva. It's very annoying to have to maintain a repository by hand. But archiva is barely an Alpha product--even though the docs talk about it like it actually exists. To me, Maven feels like a project that is dying. Spring has a much healthier community, even though it is also run by a private group. Whoever it is that is running this thing needs to really get on the ball. They are way behind on delivering things.
  42. Re: Maven 2.0.7 Released[ Go to top ]

    I helped move my current organization to maven about 8 months ago and I have to say that, so far, it's not too bad.

    Like most OSS projects, though, it wasn't a smooth transition. Lots of bugs. Lots of quirky behavior. Also, lots of unimplemented features.

    In my mind, Maven is kinda lame without Archiva. It's very annoying to have to maintain a repository by hand. But archiva is barely an Alpha product--even though the docs talk about it like it actually exists.

    To me, Maven feels like a project that is dying. Spring has a much healthier community, even though it is also run by a private group. Whoever it is that is running this thing needs to really get on the ball. They are way behind on delivering things.
    I dont think maven is really dying, I see more and more OSS projects move towards maven, I personally think maven will get an influx of new developers soon or maybe already is getting it. On the other hand this movement might hurt ant in the long run a little bit.
  43. Re: Maven 2.0.7 Released[ Go to top ]

    Not sure what specific deliverables you're talking about in the Maven project as a whole but the dashboard for the project is here: http://docs.codehaus.org/display/MAVEN/Home I think we've been pretty good with the core Maven releases over the last few months and it's a vast improvement over waiting 10 months for maintenance releases. All the releases that are made are tracked here: http://docs.codehaus.org/display/MAVEN/Releases If you're looking for a Maven repository manager today, then Proximity is your best choice in my opinion. Tamas has done a good job making something that works. It can be a tad hard to setup but once that is done it will do the job. You can read about Proximity here: http://proximity.abstracthorizon.org/
  44. Some positive words...[ Go to top ]

    We use maven2 since several months. Even though we (more as, my collegues) had to find out the exact implementation of the pom and the right use of some plugins, it all works fine. Now we're able to cheout any project and run it locally from the spot right away (also thanks to a standard configuration for tomcat on every workstation). We use proximity and contiunuum and are able to reproduce the exact version that ever went to production. Heck, we now have a single deploy button in our local intranet to deploy any version of any app to develop, test and production and it uses maven2! I now keep forgetting which on which server an app runs... Just because I don't need to know any more... So, yes there was some trouble, and no, not everything is perfect, but it works way better than editing ant scripts (which was a good tool at the time and is a good tool for very simple projects) and it produces reproducable results. Sometimes it's not exactly clear why a certain lib version is included, but that's solved by specifying the exact version. I'd like to see some eclipse IDE support, as I hate editing xml files by hand. Some wizards for editing/setting up a (new) project would be great. Overall, I'd say the result is very workable so keep up the good work!
  45. Re: Maven 2.0.7 Released[ Go to top ]

    For me ,I would like use ant instead of Maven. In China , the internet velocity is unstable and very slow. Maven deal with the dependency will waste much time. For the Maven tool, I think Netbeans(http://www.netbeans.org) would the perferred tool. NetBeans 6 will ship with Mevenide and native support maven 。
  46. Help welcome[ Go to top ]

    I'm working on a light build system http://el4ant.sourceforge.net/, begun in my company and now published on sourceforge. To sum up, it uses a project description and easy-to-design plugins to generate a pure Ant build.xml So fast, easy to use/understand/extend/debug. My current development focus on: . support Maven2 repository for download . integrating Ivy for dependencies management Do not hesitate to contact me on sf.net if you're interested in el4ant. Thank you. Yves