Slashdot Mirror


Apache Maven 1.0 Released

darthcamaro writes "internetnews.com is running a story on the release of Apache Maven 1.0 this week. Maven is a very robust project-management and project comprehension tool that is unparalleled in either open source or proprietary software. 'Maven has a long history of pushing out beta after beta, so this is definitely an important release,' Jason Van Zyl, Maven architect release manager, told internetnews.com. 'For users it means that they will have something reliable now for their production builds.' From some of the comments that Van Zyl makes in the story though, it look like the upcoming 2.0 version will be the real killer app, though 1.0 is certainly nothing to sneeze at either..."

167 comments

  1. Link to project by Inominate · · Score: 5, Informative
    Why do stories like this so often leave out a link to the actual project?

    http://maven.apache.org/

    1. Re:Link to project by lumpenprole · · Score: 1

      To give somebody something other to write than 'Frist Post!"

      --
      Disclaimer: MINAA (Mummy! I'm Not An Animal!)
    2. Re:Link to project by strictnein · · Score: 1, Interesting

      And how can a site for a software product not have screenshots showing off its functionality? That's the real question.

      So I have to install it on one of my servers just so I can see what the interface looks like? Give me a break...

    3. Re:Link to project by Anonymous Coward · · Score: 5, Informative

      It's not a project management tool.

      It's a Java programming project management tool.

      There is a huge difference between the two things.

    4. Re:Link to project by aled · · Score: 1

      Why bother if nobody is gonna RTFA?

      --

      "I think this line is mostly filler"
    5. Re:Link to project by radish · · Score: 3, Informative

      Errr...it is it's own screenshot. Maven is used to build Maven, and the output is the site you see before you.

      --

      ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    6. Re:Link to project by legenx · · Score: 5, Informative

      Maven is a command-line tool. The screenshots are not that impressive...:)

      If you know Ant (Java much improved version of make), Maven is like Ant on steroid. Maven handles intra/inter-project dependencies, project site documentation generation, unit testing, code coverage, packaging, deployment, and there's even a plugin to test whether your code conform to the coding standard.

      One of the major strength of Maven is that it manages the various jar (library) dependencies in a seemless way. Multiple subprojects do not need to duplicate the jars that they depend on. You can even throw multiple subprojects into a "reactor" and it'll build them in the correct order based on their dependency graph.

      It's sad that it's for Java only. I wish there's something like Maven for C/C++, or even C#, but so far I don't think I find anything yet.

    7. Re:Link to project by sbrown123 · · Score: 2, Interesting


      Maven is like Ant on steroid.


      Great. This is just what the world needs. Ant has something like 100 different tags with like 10 attributes to each of those. Creating large projects with Ant becomes a huge task of managing xml errors while trying to get the damn thing to build something. Now lets add some complication! People will love this. Eat it right up!

      Someone really needs to build a better make. Make a better make. Whatever. If your one of those wacky open source coders who dont have a project to waste your time on this planet behind a computer than this is a project for you!

    8. Re:Link to project by tftp · · Score: 1
      I use qmake and don't ever plan to go back:
      TEMPLATE=app
      TARGET=foobar
      HEADERS=foobar.h
      SOU RCES=foobar.cpp
      That's all it takes. Run qmake on this and then make. And it is platform-independent too, meaning that it will use whatever *make you have (gmake, nmake etc.) on any supported OS (the list is long enough.)

      I had a look at Maven's project description file, and I definitely won't use it any time soon even if I get a Java project to work on. It will cost me and other developers way too much time to learn it. I say, this may be OK for some CMM Level 999 compliance (such as overmanaged beyond belief), where each code line requires 1000 approvals from 2000 unrelated departments (and it costs $1,000,000 per line too.) But until you come up with a check that large I won't be even looking in that direction.

    9. Re:Link to project by yandros · · Score: 1

      Plan 9 provides mk, as a replacement for make. There are unix ports available. Since this isn't really a `better make' story, I'll not post more, but the papers and manual pages (yes, actually used in Plan 9) are often interesting reading regardless.

    10. Re:Link to project by dubious9 · · Score: 1

      It will cost me and other developers way too much time to learn it.

      From my experience, it does take a couple days to get up and running with Maven. Say ~10 man hours. This time is insignificant compared with the benefits that it bestows.

      Remember, a good programer knows when not to program, and plan, improve processes instead. Also, Maven really only needs to be touches by one person, the project lead. The rest only need to know a couple commands and spend a couple hours to learn how to document stuff in Maven.

      Let me end by saying that it's no magic bullet (nothing really is), but it fills a niche (automated project management) nicely that many people don't even consider. The only things that it doesn't do is task and bug management (AFAIK). I'd urge you to give it a try.

      --
      Why, o why must the sky fall when I've learned to fly?
  2. screenshots? by hey · · Score: 0, Redundant

    If it's a visualization tool... where are the screenshots?!

  3. Aha. by Inominate · · Score: 0, Troll

    It's for karma whoring!

  4. MOD PARENT +5 INTERESTING by Anonymous Coward · · Score: 0, Troll

    The parent post is right-on.

    I also am a manager of sorts (CIO) and we are currently farming out 20-30% of our work (mostly backend and server development) to India.

    We once standardized our webapp on Apache (Maven included) with MySQL but have since moved to IIS on Advanced Server 2003 with Oracle 10g on the servers.

  5. Re:Okay, Who's used this? by Anonymous Coward · · Score: 0

    Mod parent down, thats the wrong site.

  6. definition by zogger · · Score: 5, Interesting

    I would imagine there are a lot of people (like me) who had *no idea* what this is or what it is for. Here is the one paragraph definition of it FTA:

    "Maven defines itself as a project-management and project-comprehension tool. Its project object model (POM) controls the development and management of a project. The POM controls builds, document creation, site publication and distribution publication and can be stored in an XML file. Maven also provides a set of tools to enable developers to automatically generate a number of critical items, such as source metrics; mailing, developer and dependency lists; software development process documentation; change logs based directly on source repository; and source cross-references."

    In other words, it looks like a cross between the head cheese coding despot on any development project mailinglist and an automated webmaster thingee.... a management worker bot whatever.. it's a....

    I still don't know what it is :(

    1. Re:definition by MythMoth · · Score: 4, Funny

      Let me clarify.

      It's a great big pain in the butt.

      --
      --- These are not words: wierd, genious, rediculous
    2. Re:definition by poot_rootbeer · · Score: 5, Informative

      I still don't know what it is :(

      Imagine a superset of `ant build` that not only compiles your binaries, but also generates your documentation and install and test everything you need to run your application out-of-the-box in a single step.

    3. Re:definition by multipartmixed · · Score: 2, Insightful

      > Imagine a superset of `ant build` that not only compiles your binaries, but
      > also generates your documentation and install and test everything you need
      > to run your application out-of-the-box in a single step.

      You mean like 'make' with a default rules, plus a couple of shell scripts and Doxygen?

      *yawn*

      I've been doing that for a while, now.

      --

      Do daemons dream of electric sleep()?
    4. Re:definition by Atzanteol · · Score: 2, Interesting

      Out of the box? Or after three days of configuration?

      Everytime I encounter one of these huge java 'management' thingys it takes more time to configure the bloody thing than is ever saved.

      Also, what does it do that Ant doesn't? I mean, one can have ant generate javadoc, or run unit tests too...

      --
      "Ignorance more frequently begets confidence than does knowledge"

      - Charles Darwin
    5. Re:definition by speek · · Score: 1
      Ant + emerge/apt-get type thing + set of premade scripts that will do everything you ever needed provided you agree to organize your project directories exactly as Maven demands.

      I think someone else said it best: huge pain in the ass.

      --
      First, make it work, then make it right, then make it fast, then, make it bloated!
    6. Re:definition by Anonymous Coward · · Score: 1, Interesting

      It definitely fails the "30 second test" for me.

      I have this little rule: If I can't figure out how to get some supposed "productivity enhancer" up and running in 30 seconds, I don't bother. That means it needs to be easy to configure, have reasonable defaults, and allow doing unimportant things "later".

      Maven definitely did not pass.

    7. Re:definition by M1FCJ · · Score: 4, Informative
      If you download the maven source, with a minimal set of configuration, you have something going because Maven is used to build Maven.

      If you are building a new project, it takes a couple of hours on a sizeable project, if it is quite complex, it will take some time to incorporate everything. You can't build a complicated compile/tool chain without spending some time.

      It is more visual compared to ant, more interactive. Ant is just a workhorse, this has some estethics. On the other hand, if you are happy with ant, maven doesn't add anything new.

      If you are going to start a new project, give Maven a try. If you already have something mature based on complicated Ant scripts, moving to Maven won't add any value to your development system.

    8. Re:definition by MythMoth · · Score: 4, Informative

      Hmm... I seem to have been modded funny for that, but actually I kind of mean it.

      Having tried to use a couple of projects that depended upon it, I found that maven really was quite painful to use, and the projects seemed less "clean" than ones built by Ant with greater constraints on the library versions they can use.

      Worse yet, trying to build a project that's been mavenized when you're subsisting on 28.8K thinband is a nightmare. Maven's repository may seem like a great idea, but it's a terrible one for anyone behind a restrictive proxy, or otherwise unable to take advantage of this "feature".

      If you are choosing between a project based on maven and one based on Ant then I'd recommend the Ant one. Maven has no features that I consider compelling over and above Ant, but it is much more complicated, and it does introduce problems for some users' circumstances.

      --
      --- These are not words: wierd, genious, rediculous
    9. Re:definition by Svennig · · Score: 1

      I might be tempted to use it if SOMEONE could give me a reason why it's better than Ant and Forrest in combination.

    10. Re:definition by Anonymous Coward · · Score: 0

      In addition to providing facilities to build the project and generate documentation, maven also (a) manages external library dependencies and (b) inter-project dependencies for you. All that's in one place, rather than two, three, or more. Of course, you can *do* all that with Ant and Forrest, but maven also (supposedly, I don't have much experience with it) makes it easier.

  7. Incredibly useful build tool by d-rock · · Score: 5, Informative

    We have started using Maven for in-house development and it really simplifies things. Being able to declare dependencies on libraries, etc, and have Maven go and grab the correct versions during build is cool enough, but all of the reporting and site building tools are really incredible. The PHBs were very impressed with the code analysis reports that it generates, and the CVS annotation of code is very nice for our internal sites. It takes a little getting used to, but if you've used Ant, you're halfway there.

    Derek

    --
    Don't Panic...
    1. Re:Incredibly useful build tool by aled · · Score: 1

      How about security? our cvs has permissions per project.

      --

      "I think this line is mostly filler"
    2. Re:Incredibly useful build tool by Zaiff+Urgulbunger · · Score: 1

      So is it Ant with extra bits?

      And does it work with repositories other than CVS (I'm running Subversion myself but keep finding it isn't supported things, e.g. jEdit)

    3. Re:Incredibly useful build tool by clamatius · · Score: 2, Informative

      I've been using Maven for the last week or so to see what it's like. You can think of it as Ant's big brother - you use it for automating build systems and all the stuff associated with that like javadoc, reporting, changelogs and so on.

      I have mixed opinions on Maven.

      On the good side, the console mode is useful. Maven is pretty slow to start up as it's written in Java and the JVM takes a while to get moving - console mode works round that. The site generation plugins are also pretty cool, as you pointed out.

      On the bad side, it uses Jelly for its scripting language. Jelly seems kind of evil and I'm guessing the Maven developers think the same since I don't think they're going to be using Jelly for Maven 2.0. The documentation on writing new plugins (half the point of Maven if you ask me) also leaves a lot to be desired. I found I had much better luck just un-jar-ing the plugins Maven was using and looking at those rather than trying to find something out from the Jelly or Maven documentation. It's also pretty much a Java tool - while in theory you can write plugins to deal with other languages, all the existing plugins are very Java-focused.

      So in summary, better than Ant? YMMV, depending on your needs.

    4. Re:Incredibly useful build tool by d-rock · · Score: 2, Informative

      My understanding is that it's built on top of/around Ant. One of the Maven tasks is to spit out an equivalent Ant build file for the project.

      Derek

      --
      Don't Panic...
    5. Re:Incredibly useful build tool by d-rock · · Score: 1

      I use CVS over ssh and I have the CVS url in the project config file set up that way. When I run the document/report generation it prompts me for my SSH password. I think that it handles other types of CVS authentication, but I'm not positive.

      Derek

      --
      Don't Panic...
    6. Re:Incredibly useful build tool by clamatius · · Score: 2, Informative

      Maven Subversion support (haven't tried it myself).

    7. Re:Incredibly useful build tool by clamatius · · Score: 1

      I was going to write a screed about why I thought Jelly was evil but it turns out someone already did that.

    8. Re:Incredibly useful build tool by EphemeralPhart · · Score: 0, Flamebait

      I've never used an Ant, and I never will you sick bastard !

  8. Maven Bile by Anonymous Coward · · Score: 5, Informative

    The Bileblog has an alternative view on Maven.

    1. Re:Maven Bile by malloc · · Score: 5, Interesting

      That could win the best-FUD-of-the-year award. Full of scathing remarks, but nary an actual hard fact in sight.

      -Malloc

      --
      ___________________ I want to be free()!
    2. Re:Maven Bile by Sjobeck · · Score: 0

      That is one awesomely powerfully written review, whether it is accurate is irrrelevant, that is a fine example of powerful writing. Thanks for linking it for us & our enjoyment.

    3. Re:Maven Bile by hikerhat · · Score: 1

      Well, it's a view of Maven users. I don't know what maven is, and I still don't after reading that. It was kind of funny for the first paragraph though.

    4. Re:Maven Bile by bokmann · · Score: 2, Interesting

      Did that weblog actually contain any substance? It doesn't say a thing about WHY this person doesn't like Maven, it just criticizes the people that code and maintain it. It doesn't even really criticize them, as much as call them names.

      Give me a concrete reason why Maven isn't worth using... This weblog doesn't do that.

      For the record, I am well aware of Maven's shortcomings - the draconian 'one size fits all' approach to some aspects of the build system. While I don't agree that 'one size fits all', I DO believe that Maven fits many, many projects quite nicely.

      If you work in a shop obsessed with process management (CMM, CMMi, ISO900x, and even some 'agile' stuff), if you work with Java, and/or if you just want a no-hassle build system that gives you a bunch of stuff 'boiler-plate', check it out.

      Love it or hate it, form your own opinion and be 'in the know'. Maven is not going away anytime soon. (And it is NOT an Ant replacement.)

      -db

    5. Re:Maven Bile by Anonymous Coward · · Score: 1, Informative

      Obviously, you haven't read the bile blog before. Hani's point is to spew pedantic humor about the "asshats" of the java community. If you're looking for a serious argument on the subject, see:

      http://jroller.com/page/tdak/20040715#maven_over vi ew

    6. Re:Maven Bile by Anonymous Coward · · Score: 0

      UHh, I consider myself an "agile" developer, and maven seems about as un-Agile as you could get. All that config (in XML no less).

      It looks like it requires a lot of set up to get working. That disqualifies it right off the bat for me.

    7. Re:Maven Bile by Knight2K · · Score: 4, Informative
      I agree with some other posters here that the BileBlog posts on Maven don't really offer clear reasons why Maven is bad. If you read enough of his posts on Maven you can pull out some of his general issues:

      1. The auto-generated website has a lot of pointless information that most people don't care about.
      2. The language it's implemented in is crap.
      3. The project favors features over stability.
      4. Maven highly constrains project layouts
      5. New releases break stuff that worked in old releases


      For the record, I don't think the idea of Maven is bad. The sexiest feature in my mind is declaring library dependencies by name and version number and having Maven pull down the required library from a central repository. No more cryptically named jars checked into version control. Upgrading the library is as simple as changing the version number. Inter-project dependencies are simplified since Maven publishes build artifacts to the repository for you. Other projects can just treat your project like another library dependency. Think of it like APT for Java builds.

      I find myself writing the same constructs over and over in Ant. There really aren't that many ways of build a J2EE application. Maven takes care of a lot of the tedious details by letting you specify at a high-level what you want to build; it takes care of building classpaths and assembling pieces into an EAR file. You can just get on with the code.

      I also don't have a significant problem with some of the constraints Maven puts on projects. It's a pain when you have something specific in mind or are trying to retrofit a project, but it is kinda nice to be able to look at any Java project and instantly grasp where to find things. Enforcing a directory layout may constrain the developer but increases transparency. The GNU projects generally follow a standard project layout with Autoconf support. I personally would not want to give up ./configure;make;make install. Standardizing project layouts helps make ease of use like that possible. Whether Maven picked a good standard or not is another matter.

      Where I agree with Hani's blog is:
      1. The implementation language sucks. Using XML as the syntax of a scripting language has to be the worst idea ever. I had to go in and tweak a few Maven plugins when it was in beta and I still have nightmares.
      2. Compatibility was broken between releases. I know that for a while Maven was in beta, but the beta cycles were so long that people assumed it was 'good enough', like JDOM. At a few points, I thought the project was dead. So it was majorly irritating when simple things broke when upgrading releases. The BileBlogger rightfully points out that betas should be about stabilizing releases, not doing a lot of feature fiddling


      I've been thinking about bringing it in for an effort I am currently working on. A lot of its features would match my needs. The issues that Hani identified however, especially the implementation language, are holding me back.

      There is also the fact that Ant is very well known. Many people are capable of fixing issues with Ant scripts. Extending Ant for custom tasks is also fairly trivial. I wouldn't really want to write a Maven plugin. And debugging the damn thing is tough since most of the logic is hidden.
      --
      ======
      In X-Windows the client serves YOU!
    8. Re:Maven Bile by Anonymous Coward · · Score: 0

      What the fuck is an agile developer?

    9. Re:Maven Bile by Anonymous Coward · · Score: 0
      Full of scathing remarks, but nary an actual hard fact in sight.
      You say that like it's a bad thing.
    10. Re:Maven Bile by gwalcharian · · Score: 1

      It's kind of funny. Maven IS a love it or hate it tool. I've a habit of joining failing projects and turning them around, and Maven is one of my key tools to do that.

      I've often found the people who rail against XML are the ones who do not really know the various XML technologies out there.

      Several people argue against an XML programming language. Granted that it, like ALL things, is not a one size fits all solution.

      However, I've used Jelly outside of Maven for the following:

      • Storing of XML based Jelly scripts in Oracle 9 R2, or some XML enabled database, and then searching/executing whole scripts or fragments thereof from the db using XQuery
      • Using XSL to transform a Jelly Script for several uses
      • The use of pre-canned XML compression, encryption, and XML signature libraries to implement mobile code with Jelly scripts.
      • Quickly creating the GUI for an desktop app whose GUI was different for each of several different customers. XUL was examined, but wasn't able to meet severl of the client's needs. No slam against XUL, I like it, it just didn't meet the client's specific needs for use with pre-existing Java code.

      That said I do agree with some of the complaints:

      Complaint: Compatibility issues between releases

      Suggestion:

      • Maven team: Be more rigorous about eating your own dogfood and adopt known best of breed engineering release management.

      Complaint: Plugin writing/modification is neither fun nor as easy as it should be.

      Suggestions:

      • Scrap the current plug in system for Maven 2.0
      • Replace it with an OSGI based plug in system, as Eclipse has done
      • Keep Jelly as an option for plugin scripts, but use the beanshell framework to expand script options
      • Strip out as much functionality out of the Maven core until you have a Maven micro-kernel. Put the extra functionality into OSGI bundles managed as separate projects
      • Test, Test, Test!

      Complaint: The auto-generated website has a lot of pointless information that most people don't care about

      Suggestions:

      • I edit my Maven builds so that it only generates the reports I am are interested in. Many of those reports are kind of like lint though...you don't realize how useful it actually is until you use them for the first time. For example I used the checkstyle report on a project with many developers and it made my life was easier.

      Is Maven for everyone? No, definitely not. For me, and those engineers I have trained, Maven and Jelly are definitely two of the essential items in our everyday toolbox for medium to large projects.

    11. Re:Maven Bile by k8to · · Score: 1

      Okay, I'm curious. How does the XML nature of this Jelly directly benefit in any of your examples? For comparison, ask yourself: Could this have been done in a language which is implemented in plain text?

      --
      -josh
    12. Re:Maven Bile by gwalcharian · · Score: 1
      Jelly does not allow these things to be done. They can be done in XML, plain text, CSV, in the same way the code can be implemented in C, Java, or even C#. The benefit that Jelly brings to the table is the ability to leverage the many XML technologies out there without re-inventing the wheel for a proprietary or little-used format. Also the more in use a technology is the quicker it's implementations will become stable. In short it's about minimization. Minimization of risk. Minimization of time to market.
      1. Storing of XML based Jelly scripts in Oracle 9 R2, or some XML enabled database, and then searching/executing whole scripts or fragments thereof from the db using XQuery" Let's say I want to find all scripts that access a database. Then I can create an xpath expression that represents this and submit it to the XML database which handles the searching for me. I can then run a stylesheet on the query results to create a report in pdf format. Granted this could be done using SQL, and the report code could be custom written, but again the point is not whether it can be done. The point is how much of the code used in the solution is new code, and how long does it take to solve the problem. In the scenario above I would have to write only TWO things: (1) the XSLT that transforms the query results to xsl:fo, and (2) the xpath expression that represents the query I want to do. As an additional plus these are implemented in well known technologies, so if I transfer to another project someone else can come in and take my place with ease, as long as they have XSLT/XPATH in their skill set.
    13. Re:Maven Bile by k8to · · Score: 1

      I'm lost. You're searching scripts in a database which access the database? This seems kind of a 1 to 1 ratio here.

      Also, wouldn't just a regex across the scripts work?

      --
      -josh
    14. Re:Maven Bile by gwalcharian · · Score: 1
      Ok, let me try to clarify the example.

      I am using Oracle 9i to serve an XML database of say project management information for many projects. The operations done on this data change frequently and are captured as Jelly scripts, which are also stored in the database.

      Each user has a customized view, which is created by a different Jelly script stored in the database. A thin client fetch's that user's Jelly view script and Jelly swt tags in that script create the user's personalized GUI from XML stored on the server.

      Now at some point I want to see what projects, or other data, each view accesses, and I want that information to be presented as a PDF report.

      Could I do that with SQL, regex? Yes, of course. But I would need to roll my own parser, a set of regex, and code to take the match groups and put them into a report, and the code to publish the report as a PDF.

      Using the XML technologies I can instead do the following:

      1. Create an xpath expression to gather the information I need as XML
      2. Create a XSLT stylesheet that translates that XML into xsl:fo. The stylesheet has as a source document the URL to query the db with the xpath expression.
      3. Run the result through Batik or some other xsl:fo to PDF converter.

      For me the second way will take half or less of the time the first method would take, and it would be much more re-usable.

  9. Re:Sheesh by rkuris · · Score: 2, Informative
    MS Project is NOT bug free; not even close. I would venture to guess that MS Project has more bugs than IE. It's non-intuitive also.

    I, for one, am glad to see this project get moving. I'd love to see open-source and closed source projects get real project managers using real project management software.

    Everyone will be more organized that way!

    --
    Get rid of everything Micro and Soft: Buy Viagra and/or Linux
  10. Screenshots? by Anonymous Coward · · Score: 0

    Anybody have links to screenshots?

  11. Not the only thing left out: it's for Java only by Anonymous Coward · · Score: 5, Informative

    Sadly, the headline also left out the rather key information that this tool is for Java projects only.

    I was quite looking forward to a revolutionary project management tool ... alas, this one is yet another myopic product of the "Java is the whole universe" generation.

    Java is great ... but there is a larger world out there you know.

  12. Re:aaachooo by Anonymous Coward · · Score: 0

    I was wondering the same (see my reply below). I checked his previous posts, and he has been asked this before, and answered...

    "AI backed Maoists in Nepal"

    That might help... off to google I am.

  13. Java by yamla · · Score: 2, Informative

    This is only for Java projects, it seems.

    --

    Oceania has always been at war with Eastasia.
  14. Indian stomach - wtf? by damgx · · Score: 1

    Hum, this headline caused me some confusion.

    In danish 'maven' is the word for stomach.

    Well, can't win them all :)

    --
    I only read slash. for the articles...
  15. Visualize them! by Mustang+Matt · · Score: 3, Informative

    I'm trying to get it to run on windows.

    I must not have the right "Java" as it is telling me it can't lib/tools.jar so I'm going to go grab the latest jdk and see what happens.

    For anyone getting the JAVA_HOME environment variable not set, a reminder is that you can set env. vars by right clicking on my computer and going to advanced and then there's an environment vars button.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
    1. Re:Visualize them! by furball · · Score: 2, Informative

      There's a godawful lot of things you have to point the JDK to in order for it get everything it needs. I used to hack on a code metrics analysis tool. The build instruction for Windows was a complete mess.

      Mac OS X just did things right. It did it even better than Solaris.

      However, this being a development tool rightfully has some fairly high minimum knowledge requirements. If you're trying to get it to find lib/tools.jar by upgrading to the latest JDK, you're not in the intended audience for this sort of thing. I'm not being insulting. It's just that most people who work with Java knows what lib/tools.jar is and how to get it found.

    2. Re:Visualize them! by minniger · · Score: 2, Informative

      Also make sure your path is set correctly.

      Click on PATH and edit it so the JAVA_HOME is at the FRONT
      of the path as so:

      %JAVA_HOME%\bin;<... rest of path ...>

      and you have JAVA_HOME set as:

      JAVA_HOME=<path to jsdk or jre home>

      This will save you boatloads of problems.

      ------------

      It's a good thing Swing sucks and is too hard to use or else
      I wouldn't be able to do my dev on a mac and deploy my apps
      to windows. Silly me.

    3. Re:Visualize them! by Mustang+Matt · · Score: 1

      No offense taken. I think you're absolutely right.

      I do know a bit of java but I've always been intimidated by the nasty java installers so I always fallback to php and web based applications vs java applications.

      So to educate me... Where is tools.jar?

      --
      The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
    4. Re:Visualize them! by SpamJunkie · · Score: 1

      Seems like a major assumption to have to have PRODUCT_X_PATH as the very first item in the path list. What is to be done when PRODUCT_Y and PRODUCT_Z have the same requirement? Surely it's trivial to be able to accept the path no matter where it appears?

    5. Re:Visualize them! by M1FCJ · · Score: 1
      What installer? Just download the tarball version of the JDK if you don't want to bother with the rpm package, export JAVA_HOME, then add $JAVA_HOME/bin to your path and Bob's your uncle.

      Same thing also works with the Windows version. Most packaged applications behave well with JAVA_HOME env. defined properly. You are ready to roll. Maven and Ant are no different.

    6. Re:Visualize them! by M1FCJ · · Score: 1

      tools.jar is in $JAVA_HOME/lib/tools.jar, if you have the JDK. On the other hand, in many cases you only jave to define JAVA_HOME correctly. If you have JRE, you don't have tools.jar.

    7. Re:Visualize them! by minniger · · Score: 1

      It's not a maven requirement (I've done nothing more than read
      about maven).

      By putting the JAVA_HOME/bin at the front of your path you
      are ensuring that the version of java being used is the one you want.

      Oracle, Sybase and others tend to drop all sorts of JVM versions into your path. Effing everything up.

      There are other various ways of making sure your app uses the right jvm, but this is the easiest that I know about.

      For the situation you describe you can include a JRE with your installer (install anywhere does this). By passing the path altogether. Or you can have a bat file that always looks for the JAVA_HOME (or attempts to find it). Or about 20 other methods.

    8. Re:Visualize them! by fishing · · Score: 1

      The reason it's complaining about not having lib/tools.jar is because the version of Java you have is "Runtime-only".
      The other version, the "Developer version" includes the compiler and other assorted stuff needed to build things in Java.

      So, you're doing the right thing by downloading "another version", just make sure that it's the developer version, though.

  16. "Of course" by Anonymous Coward · · Score: 0

    Why do submitters always say "of course" like everyone on the fucking planet should now what these things are innately? How many casual users use Maven anyway?

  17. Also a perfectly good english word... by Ieshan · · Score: 1

    Maven is also a perfectly good english word, meaning "expert".

    1. Re:Also a perfectly good english word... by Doc+Ruby · · Score: 1

      The English word maven comes from the yiddish, where it means, more or less, "a definitive expert".

      --

      --
      make install -not war

  18. Re:Sheesh by Pieroxy · · Score: 0, Troll

    I must tell you something. Please don't blame me I'm just the messenger:

    Your sense of humour is inexistant.

    Now there might be several reasons:
    1. You never had one. This situation is not desperate, but will require some work.
    2. You lost it. Go get it!

    Cheers

  19. Plone-esque proportions by Pac · · Score: 1, Informative

    So I am not the only person who had bad experiences with Plone? Good to know it was not my own dumbness alone that led me to the conclusion Zope would be a good idea if the Zope people stopped having revolutionary ideas and sat down to document and clean up what they already have... :)

    1. Re:Plone-esque proportions by Anonymous Coward · · Score: 0

      I've been running a Plone based site for two years. The SQL database became non writable on a couple of occasions but apart from that it has been very stable and a breeze to use after about a week getting the hang of it.

    2. Re:Plone-esque proportions by Anonymous Coward · · Score: 1, Informative

      We just lost half a year trying to build a scalable Intranet site with Plone and Zope, for an organisation which really needs that scalability. Never again.

      We even had some of Europe's best Plone/Zope experts on the project, and they came to the conclusion that it's not really possible (outside some very narrow fields where you can just use Squid or other similar caching to create scalability from where there is none) to create scalable web applications using those tools.

      One of the largest problems was the fact that there are only two Oracle adapters for Python, of which neither is really production-ready, compared to JDBC connectivity or the Perl Oracle modules, or any of the C OCI redirect APIs I've seen.

      Summa summarum: we came to the conclusion that the only people who should invest in Zope products and knowledge are those who expect to profit from directly selling that knowledge - as a serious tool Zope/Plone certainly doesn't have anything over Java or even PHP and .NET.

      Unfortunately, those UI screens people generally demonstrate make it a dangeously seductive waste of time.

  20. Jelly by Anonymous Coward · · Score: 0

    Another part of this project (or at least one that depends on it) is the Jelly project. It allows you to define a GUI (SWT or Swing) in an XML file. I suppose it's similar to XUL, but it's an interesting project nonetheless.

    Jelly SWT

  21. Zyl...Zuul...Coincidence by GaryOlson · · Score: 2, Funny

    Codebusters?

    --
    Every mans' island needs an ocean; choose your ocean carefully.
  22. Re:MOD PARENT +5 INTERESTING by Anonymous Coward · · Score: 0

    It appears quite a few have an ax to grind when more than half the posts are moderated "-1"

  23. this smells of propaganda by vegasbright · · Score: 0

    Is it just me, or does this seem like another cleverly placed advertisement?

    --

    Tyler: You don't know where ive been, Lou. YOU DONT KNOW WHERE IVE BEEN!!
  24. Java thing? by Queuetue · · Score: 0, Redundant

    So, this is some java thing?

    1. Re:Java thing? by Anonymous Coward · · Score: 0

      god i hate java...

  25. Hell, by eril · · Score: 2, Interesting
    I've been using it for about a month and I still don't know what it is. All's I know is that I go to the project directory I just downloaded from CVS, I type
    maven eclipse
    and all the extra files and shit I need for the project to compile and work are automatically there.

    Aside from that, I know that Maven reads from an xml based config file that's in the project directory.
  26. Check out JAM for Maven by alphafoo · · Score: 5, Informative
    I started using Maven about a month ago, just to see what all the fuss was about. There is a lot to it, and it can be overwhelming. But there is a good middle ground between roll-your-own-ant and Maven, and it's called Javagen Ant Modules (JAM) and it's here.

    What I got from JAM that is useful to me:

    • dependency management automatically downloads library JARs for me during build.
    • common build.xml file and framework, so all my Maven projects have same basic structure.
    • Reduced learning curve so I could get going without learning everything about Maven all at once.
    • access to lots of cool Maven "plugins" like maven-eclipse that integrate the whole thing into my Eclipse3.0 setup.
  27. Its a love it or hate it project by Timesprout · · Score: 2, Insightful

    Unfortunately most people seem to hate it. Maybe thats just my bias because I tried it and found it a complete pain in the ass to work with. I dont like supposed development aides thats want to tell me how I should organise everything to suit its quirks rather than my preferences. Its really irritating when this demands vast amounts of configuration to achieve and requires a scripting language who creator has apologised for creating an abomination.

    Think I (and many others) will stick with ant for the time being

    --
    Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
    What truth?
    There is no dupe
    1. Re:Its a love it or hate it project by M1FCJ · · Score: 1

      Well, what do you expect? That is its purpose, managing your development. I personally abstracted ant scripts where you can define where the files in properties. Then it is a matter of policy and taste where to put the files.

    2. Re:Its a love it or hate it project by Anonymous Coward · · Score: 0

      Maybe it's better now, but when I first ran across it, the projects that seemed to be using it were incredibly poorly organized. I couldn't figure out where to download binaries, nor what the dependencies were. Not particularly useful for a "project management system".

    3. Re:Its a love it or hate it project by svetlin · · Score: 5, Informative

      Unfortunately most people seem to hate it.
      Maven mailing list(s) is one of the most active ones, with +50 messages a day. Most articles and comments at ServerSide, IBM DeveloperWorks and elsewhere are quite favorable toward it. Many major projects (e.g. Geronimo) are using it.

      I dont like supposed development aides thats want to tell me how I should organise everything to suit its quirks rather than my preferences.
      Maven follows well established practices (e.g. directory structure) from the Apache Jakarta projects. Accustomed to Ant's freedom, I also was unhappy with some defaults/behaviors initially, but gradually all of them made sense.

      Its really irritating when this demands vast amounts of configuration to achieve
      I interpret this to mean that attempting to implement your quirks in Maven took vast amount of configuration to achieve, and have no objection to that.
      Another massive configuration effort is required when an existing complex and rather quirky Ant build of a large application is migrated to Maven (as it was in my case, I should mention that I wrote also the Ant build ;-)).
      But starting with Maven on a common medium-sized app is relatively easy when using the GenApp plugin.

      requires a scripting language who creator has apologised for creating an abomination
      I agree here. I also do not like the idea of executable XML, of using XML as a programming language. Please note, however, that Jelly is an interface for tags in Maven used to implement plugins. In principle, any mechanism for embedding tags will do (and there is significant work in this direction for v2 AFAIK).

      So, apart from personal taste, Maven is quite a solid production-ready project build and comprehension tool.

      --
      Svetlin

  28. Bloated project mgt software killed Netscape by xxxJonBoyxxx · · Score: 1

    Bloated project management software helped kill Netscape - they spent all their time farting around with a bugtracker when they should have been fending off Microsoft.

    Apache doing non-web server things makes me worried.

    1. Re:Bloated project mgt software killed Netscape by radish · · Score: 3, Interesting

      Ha!

      Jakarta has been running for years and is without a doubt the most important open source project in the Java world (and one of the more important anywhere). And it's part of Apache.

      Apache is not just a webserver and it hasn't been for a looooong time.

      --

      ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    2. Re:Bloated project mgt software killed Netscape by Anonymous Coward · · Score: 2, Insightful

      The ASF has been doing projects that aren't directly related to web servers for a long time. Also, poor software engineering killed Netscape. They were pouring resources into the horrible 4.x codebase and weren't getting anywhere. That's why Mozilla started from scratch.

    3. Re:Bloated project mgt software killed Netscape by michaelggreer · · Score: 1

      Really, go to Jakarta and take a look around. Tomcat, Struts, Log4j... the list goes on of fantastic Java software. They are one of the major players in Java, next to IBM and Sun, and a great gadfly in the Community Process.

  29. Maven Great??? by jhouserizer · · Score: 1

    Maven may be "neat" to some, but it also has real issues...

    1. Re:Maven Great??? by Anonymous Coward · · Score: 0

      Whoever writes that is a serious bitch.

    2. Re:Maven Great??? by lorcha · · Score: 2, Insightful

      Real issues? I read that rant, but I must have missed all those "real issues". Could you please point me to a single "real issue" in there?

      --
      "Avoid employing unlucky people - throw half of the pile of CVs in the bin without reading them." -- David Brent
  30. OT: FOSS competitor to Microsoft Project? by Anonymous Coward · · Score: 0

    This is a dumb question.

    Is there a FOSS competitor to Microsoft Project, or do we have nothing in that area yet?

    1. Re:OT: FOSS competitor to Microsoft Project? by Anonymous Coward · · Score: 0

      Wait a second.

      So Microsoft Project can only manage software development projects? I thought that you could use it to build a skyscrapter or whatever. That's the picture on the box.

      So what if I want to organize my life into "projects." Is there some management software I can use to help me keep track of things?

    2. Re:OT: FOSS competitor to Microsoft Project? by Anonymous Coward · · Score: 0

      uuuuuhhhhhhh Mr. Project??

    3. Re:OT: FOSS competitor to Microsoft Project? by _termx23 · · Score: 3, Informative

      Try dotproject.

      http://www.dotproject.net

      Not yet the equal of M$ Project, but given time...

    4. Re:OT: FOSS competitor to Microsoft Project? by Anonymous Coward · · Score: 0

      Dunno if this is what you're talking about, but I'm totally in love with a hosted service called basecamp.

      It is ULTRA simple. You can get started in 10 seconds. Barely anything has to be done "up front". Great for bringing people together in discussions too.

      It actually has a lot of cool features, it's not really "feature-packed" but the main thing is how easy and simple and flexible it is.

      I used to never think I'd like a web-based app but this one is so Mac-like ("it just works")...

      You can manage one project for free.

  31. Re:Not the only thing left out: it's for Java only by Kingpin · · Score: 4, Insightful


    Is it really Java only? It's written in Java yes, it supports many common Java paradigms - would it not be fairly simple to use doxygen rather than javadoc, gcc rather than javac, nunit rather than junit etc etc.

    Ant allows this, and I understand Maven to be an evolution of build tools, so I don't see why it should not be project-development-technology-agnostic.

    --
    Unable to read configuration file '/bigassraid/htdig//conf/14229.conf'
    Geocrawler error message.
  32. Quoth Frink? by Cyno01 · · Score: 0, Offtopic

    Hoyven maven! Nggyai...

    --
    "Sic Semper Tyrannosaurus Rex."
  33. Re:Not the only thing left out: it's for Java only by radish · · Score: 4, Informative

    Not true. It uses ant, ant can do anything (think of it as a replacement for make). People here build C, C++ and a bunch of other stuff using ant. With the correct modules you wrap all that up (with your Java components) into one nicely managed project.

    Sure it's written _in_ Java, but it's not just _for_ Java (but naturally, the user community is heavily biased in that direction).

    --

    ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

  34. Screenshot by _xeno_ · · Score: 4, Funny

    C:\maven-1.0>bin\maven
    .__ __
    | \/ |__ _Apache__ ___
    | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
    |_| |_\__,_|\_/\___|_||_| v. 1.0

    BUILD SUCCESSFUL
    Total time: 1 seconds
    Finished at: Fri Jul 16 17:34:27 EDT 2004

    ---

    It's a console app. You call it and it builds "stuff", much like Ant does. I don't really know much more than that right now, though, so no complicated questions please. :)

    (Oh, and that "screenshot" is messed up, I had to add a "." to make sure it stayed indented properly, Slashdot messed it up otherwise.)

    --
    You are in a maze of twisty little relative jumps, all alike.
    1. Re:Screenshot by Orick · · Score: 1


      So instead of spending time writing scripts and configuring your make files, you spend that time configuring Maven?

      Got it.

      --
      Kirby Reviews

    2. Re:Screenshot by dubious9 · · Score: 2, Informative

      Erm... so you didn't really read the page huh? Maven is a project automation tool, not a build automation tool. You configure it to do (continuous) builds, but also to do documention, collaboration etc.

      I guess I shouldn't be too surprised, I wasn't on the bandwagon either until I actually used it for a project.

      --
      Why, o why must the sky fall when I've learned to fly?
  35. Re:Not the only thing left out: it's for Java only by clamatius · · Score: 5, Informative

    It's technically possible but part of the point of the thing is that you don't have to spend forever writing build scripts to get going. So once there's a set of users writing plugins with better support for (e.g.) C# and C++, sure it'll be agnostic.

    Right now it's effectively a Java tool since most of the plugins are for Java (jar, javac, javadoc, junit, etc).

  36. Oh, you for mean for programming projects only by Jayfar · · Score: 2, Insightful

    I was hoping it was a project management system, not a programming project management tool, not a java thing. Nothing to see here for me; I'll move along now.

    1. Re:Oh, you for mean for programming projects only by tntguy · · Score: 5, Funny

      This isn't the project you are looking for.

  37. Re: The PHBs were very impressed by Morgaine · · Score: 4, Funny

    The PHBs were very impressed ...

    I didn't follow whether this was intended as praise or criticism.

    --
    "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
  38. A different opinion by joeykiller · · Score: 4, Interesting

    Not everyone seems to be fond of Maven. This guy lists both pros and cons with Maven, but lands on the negative side.

    I havent used Maven myself, but since this was mostly a very positive announcement, I guess it cant hurt to point to another point of view.

  39. Wow. by Mustang+Matt · · Score: 1

    The project is no longer stagnant.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  40. Java as a system facility by Brian+Blessed · · Score: 3, Interesting

    I've only used Maven in the way that it has been part of projects that I've downloaded.
    Something that gives me reservations is the way that it manages library dependencies by downloading them into the project tree. On a Unix system this feels inconsistent because I prefer to manage installed software (libraries) on a system-wide basis.

    It would be nice if there were a consensus on Java library dependency resolution/installation. I used to use the exellent jpackage.org on Mandrake, but now I appreciate the source compilation aspect of Gentoo (although many of Gentoo's Java packages are old). A combination of the two would be ideal.

    And whilst I'm forming a wishlist, I'd also like Java applications to have greater integration with the system, not on the desktop, but in the way that multiple invocations might have less of a memory penalty (like a Java subsystem).

    - Brian.

    1. Re:Java as a system facility by Twinkle · · Score: 1

      Maven doesn't bring library dependencies into your project tree.

      Maven's 'repository', under Linux (and with the default properties), is under ~/.maven/repository/

      Admittedly each user gets a copy of all the dependencies (rather than, say, having things under /usr/local/maven/), but it's certainly not put into each project.

      Managing different versions of dependencies without duplicating them into each project is, for me, the entire *point* of Maven.

      You can override this state of affairs to create a system-wide repository, if you really want...

    2. Re:Java as a system facility by Brian+Blessed · · Score: 1

      Maven's 'repository', under Linux (and with the default properties), is under ~/.maven/repository/

      You're right - my memory had become slight hazy about this. It was the per-user package repositories that I was remembering as a potential problem.

      What it needs now is source compilation ...
      [I know that the Java bytecode won't vary much with recompilation, but it is using the "preferred source format" that I like]

      - Brian

    3. Re:Java as a system facility by michaelggreer · · Score: 1

      And whilst I'm forming a wishlist, I'd also like Java applications to have greater integration with the system, not on the desktop, but in the way that multiple invocations might have less of a memory penalty (like a Java subsystem).

      Then you might want Mac OS X. Library memory is shared across VMs. I think this is coming in Java 5 (1.5) for everyone, but I forget. Maybe its 1.6 (6?).

  41. It a time saver by Anonymous Coward · · Score: 1, Informative

    I've found Maven to be very handy. It can be really hard to write a portable build script in Ant (especially if you use several external JARs). Maven will automatically download dependencies and build your classpath.
    Back when I used Ant I had to write a new build script for every project. Maven is able to handle most of that kind of thing for you.

  42. Re:Sheesh by Anonymous Coward · · Score: 0

    If you actually read up on Maven, you would realize this this is completely orthogonal functionality to MS Project. Maven is a more of a build management tool for java (and only java) software projects. Its a glorified ant with some additional bells and whistles.

  43. Right .... by Anonymous Coward · · Score: 1, Funny

    All's I know is that I go to the project directory I just downloaded from CVS, I type

    maven eclipse

    and all the extra files and shit I need for the project to compile and work are automatically there.


    So far then, we've established that it's entirely opaque. OK, I feel we're getting there.

  44. Re:Sheesh by Anonymous Coward · · Score: 0

    Might I enquire why you are answering to me? I was quietly trolling over a post that didn't get the humoristic side of its parent. I wasn't comparing Maven and MSP...

  45. Re:Not the only thing left out: it's for Java only by nettdata · · Score: 4, Informative

    Sadly, the headline also left out the rather key information that this tool is for Java projects only.


    Actually, no, it's not. We use it to build C code, install and configure Oracle and DB2 databases, automate some OpenSSL stuff, put together PHP sites, and rsync stuff all over the place. We also use it for managing our main Java app as well.

    Just the tool is Java-based.

    --



    $0.02 (CDN)
  46. Easy to relate to the flaming though by Anonymous Coward · · Score: 0

    The weblog item was obviously just a huge flame, so I won't comment on the content.

    However, it's easy to relate to the feelings that the author expressed so magnificently. I've come across other projects where the problem is entirely the myopia of the (very specifically) Java-centric personnel, to the extent of pushing slightly wider-read developers to other pastures.

    I put it down to the fact that Java is often taught in college as the one and only programming language, due simply to lack of time to educate students more broadly. They then go out and are totally dead to the concept that anything exists outside of the Java universe. Reasoned argument about integration falls on deaf ears.

    Maybe the weblog author had a similar experience with the Maven developers. It can be very frustrating. :-)

  47. Red Dwarf Does Maven by SuperBanana · · Score: 2, Funny

    Cat: "What is it?"
    Cryten: "a project-management and project-comprehension software tool that uses a Project Object Model with XML storage"

    (blank, smiling stare)

    Cat: "What is it?"
    Cryten: "a project management tool that increases developer productivity when working on Java projects."

    (blank, smiling stare)

    Cat:"What is it?"
    Holly: "a computer thingy"
    Cat: "Aaaaaah. Now why didn't you say that in the first place?"

    (everything I needed to know, I learned watching Red Dwarf!)

    1. Re:Red Dwarf Does Maven by zogger · · Score: 1

      heheheheh, you win! Best explanation yet!

    2. Re:Red Dwarf Does Maven by Anonymous Coward · · Score: 0

      Zim: This is a proect manage--
      GIR: What is it?
      Zim: A project m--
      GIR: What is it?!
      Zim: A proj--
      GIR: WHAT IS IT??!?

  48. Ouch, not "JAM" ! Non Java-centric "jam" exists by Morgaine · · Score: 2, Informative

    But there is a good middle ground between roll-your-own-ant and Maven, and it's called Javagen Ant Modules (JAM) ...

    That's very bad news, because the open-source build tool "jam" already exists and has been around for a very long time. And it's really good too.

    People really ought to google a bit before picking names for their project tools. Sure, names can often be reused without conflict, but here both jam's are program build tools, and that's just plain short-sighted.

    --
    "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
  49. You want this then... by Big+Sean+O · · Score: 3, Interesting

    Gantt Project

    It's similar enough to Microsoft Project. Gantt Charts have been a project management standard for almost 100 years.

    Linux, Mac OS X, Windows. It's Java, so take yer pick. GPL'd too.

    --
    My father is a blogger.
  50. Re:Sheesh by rkuris · · Score: 1

    You're right. I wasn't proposing that this is a replacement for MS Project. All I'm saying is that I'm glad there's some focus on project management and I'm hoping for more!

    --
    Get rid of everything Micro and Soft: Buy Viagra and/or Linux
  51. My impressions of maven by scrytch · · Score: 3, Informative

    Maven is probably best thought of as a java equivalent to portage, i.e. it concerns itself with fetching, building, packaging (including metadata like authors and such), and version tracking. It just lacks a browseable set of package skeletons the way ports and portage does.
    I used maven about a year ago, and I found it to be incredibly slow, bloated, underdocumented, amateurish, slipshod, and oh yes, buggy. It seems designed around some sort of "kitchen sink" approach of "xml is kewl, plugins are kewl, let's glom it all together and make something ... kewl".

    Honestly, whenever I see the word "plugin", I think someone hasn't really designed things well. Instead of providing a coherent app, they make a library of functions and let random piecemeal bits added after the thought take over the actual functioning. I'm not knocking component design, just the typical thought process that goes into typical "plugin" architectures. Stick with ant, you'll be much more sane for it.

    --
    I've finally had it: until slashdot gets article moderation, I am not coming back.
  52. try the ACTUAL bile by BoxedFlame · · Score: 3, Informative

    Why Maven Sucks

    The bile you linked is just a reminder so no one forgets that it indeed still sucks.

  53. It is a build tool . by Anonymous Coward · · Score: 5, Insightful

    It is a Build Tool, not a "project management tool".

    What it builds are software programs.

    What it was designed for and is good at is building the software called "Apache". The more a software development project looks like the Apache one, the more likly it is a useful tool for that project.

    You want a management tool. This is NOT it.

    You want a nonsoftware project tool. This is NOT it.

    You want a build tool for a research software project, say in AI or written in LISP. This is NOT IT.

    You want a build tool for far flung contributors writting code in Java (or java like language) with all the structural details about the project already known. Bingo!!! This is the tool for you.

  54. Uhm.... what? by gumpish · · Score: 1


    Maven is a very robust project-management and project comprehension tool

    Uhm... what?

  55. Sir: by Anonymous Coward · · Score: 0

    Please to be advised based on your excellent and technical analysis and subsequent implied recommendation, that I will not download and install this software, thereby saving both ends of my anatomy from any painful interactions. It was close, too, very, very close.......

    zogger

  56. ... a long history of pushing out beta after beta by Fry+a+Lad+Up · · Score: 2, Funny
    "Maven has a long history of pushing out beta after beta, "
    If only they had a good project management tool.
  57. The first... ummm? by Anonymous Coward · · Score: 0

    Check out http://qbal.mozdev.org I've been building engineering intranet sites since 1995... although inferior to Mavens techology. I'm in the process of coming up to speed on developing in the Mozilla environment using XUL and will be initially building a framework to build and manage linux distros and will follow that up with the rest of the QBAL applications. QBAL will scale to manage corporate engineering organizations where 100's of projects are occuring at any given time. There are 27 applications in all. The work will be GPL'd.

    Kramer

  58. see qbal.mozdev.org by bigusputicus · · Score: 2, Informative

    I posted earlier anonymously. I'm bulding a superset of what Maven provides for Linux distros and projects. Been building engineering intranet sites since 95 that provide some of the features maven has along with some features maven does not have. QBAL will be GPL'd. I'm coming up to speed on Mozilla/XUL now and will have something ready this fall. Take a look at http://qbal.mozdev.org to get an idea of the scope.

    Bigusputicus

  59. Maven is badly designed by Anonymous Coward · · Score: 1, Interesting

    Maven is not a general purpose Java build system, so i doubt it will ever overtake Ant's popularity.

    The main problem is that it can only build projects with certain very rigid structures, it also has a number of features that should never be part of a build system at all, such as documentation generation and repository management. None of these extra functions it does particularly well.

    For example if you want a shared jar repository - it would be quite simple to come up with something more sophisticated that Maven in few lines of an Ant script.

    The documentation generation functionality didn't require a new alternative build system to be created.

    The underlying problem is that Maven was never designed as a general purpose system, it grew out of a custom system designed for the Jakarta project, which is open source Java project consisting of a number of dependent jar libraries. The main goal of Maven is to manage the dependencies between these libraries and build the Jakarta documentation sites.

    If your project is similar to the Jakarta project then you might find it useful, otherwise i would steer clear.

  60. Re:I don't know by fishing · · Score: 1

    It's a system for building software, similar to "make".
    It's a way of scripting all of the steps required to deliver software in it's final state.
    A typical project-build for me often includes stuff like getting the latest library files that work with my code, compiling source to byte-code, byte-code enhancement (e.g for JDO object persistence), packaging into JAR files, inserting macros into config files and source code for server-names, test login and passwords, etc., then copying a myriad of files into various places, starting and stopping system services (like Tomcat), then executing tests, building JavaDoc documentation, then uploading all to a webserver.
    Maven automates the process of doing this. You can do the same sorts of things with Ant (which Maven uses, also), but after your 5th or 6th project you end up saying to yourself "hey, I keep writing the same stuff over and again", and improvements to your build process in one project don't get percolated through to the older ones.
    I'm certainly looking forward to adopting this in our work environment... I'm DEFINITELY spending far too much time writing build scripts, so it's people like me that need this.
    Apparently, you don't do much coding?

  61. Re:MOD PARENT +5 INTERESTING by Anonymous Coward · · Score: 0

    which is why the axkit package is such a feature...

  62. QUIT REPLYING TO YOURSELF YOU FUCKING FAGGOT! by Anonymous Coward · · Score: 0

    gET bACK tO yOUR cOCKSUCKING!

  63. AI backed Maoists in Nepal by Anonymous Coward · · Score: 0

    As did the Belgian government - another brilliant idea from the 'watermelon' green party.

  64. Uhh, not quite. by gosand · · Score: 1
    It's similar enough to Microsoft Project. Gantt Charts have been a project management standard for almost 100 years.

    And if you think that all you need to effectively manage a project is some Gantt charts, then I have an EULA I'd like you to sign.

    I think what the parent poster was hoping for (as was I) was a Project Management system. Gantt charts alone don't cut it.

    --

    My beliefs do not require that you agree with them.

  65. Svetty Horsey? by Anonymous Coward · · Score: 0

    Svetty Horsey!

  66. Re:aaachooo by minus_273 · · Score: 1

    please be aware that not everything that happens / is happening in the world is on the new or is everything online. I speak from personal experience and my interaction with people from AI. take it for whats it worth, or dont. The BBC has a lot of good (though biased) stories about the conflict in nepal and how human right groups made it worse by intervening or sideing with one party or the other.

    --
    The war with islam is a war on the beast
    The war on terror is a war for peace
  67. Re:Not the only thing left out: it's for Java only by Bob+Uhl · · Score: 1
    What, exactly, do maven or ant buy which make does not provide? They are written in a slow, ugly, unpleasant language, yes. They use XML instead of decent flat text, yes. They lack the great library of tools which have grown up around make, yes. Why would I want this, again? I will grant that make's use of is an abomination, but other than that it's a damned good tool which does a damned good job.

    Idiot Java/XML heads constantly re-inventing the wheel.

  68. Re:Not the only thing left out: it's for Java only by radish · · Score: 1

    Idiot Java/XML heads constantly re-inventing the wheel.

    Idiot luddites refusing to see progress when it smacks them in the face.

    --

    ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

  69. In a few years, maybe by Anonymous Coward · · Score: 0

    The lead developer, Jason van Zyl, thinks that OS specific packaging of Java artifacts is pointless, and that there is no reason, ever, to rebuild an artifact from source.

    Give them a few years, and they'll probably come up with some sort of real package management system. They just need to go through the pains that all binary-only distribution systems have to go through. Atm, they seem to be destined for the CVS snapshot hell.

    The other question is how relevant Maven is going to be outside the Windows world anyway.

  70. Re:Not the only thing left out: it's for Java only by Bob+Uhl · · Score: 1
    Idiot luddites refusing to see progress when it smacks them in the face.

    What, then, is the progress? As I asked in my post, 'what, exactly, do maven or ant buy which make does not provide?' As I noted, they are written in an ugly language; they use an ugly syntax (XML has all the bad points of S-expressions and few of the good); they do not work with auto*. I did note that make has a bad point.

    I also looked at a few sites trying to get an answer. As far as I can see, switching to maven or ant buys me nothing but pain.

  71. Re:Not the only thing left out: it's for Java only by Anonymous Coward · · Score: 0

    Note: I am not an Java developer or Ant user.

    Try the 2nd paragraph of http://ant.apache.org/ for one answer.

    "Ugly language/syntax" is subjective. (Personally, I think makefiles and XML files are equally ugly, and don't even get me started on auto*.) Fortunately, with the tools available today (e.g. http://www.eclipse.org/), we have few excuses to manually edit these sorts of files. Therefore, "prettiness" is of little consequence.

    I don't know if there is a solution for auto* integration. We have to keep in mind that Ant was designed for use with Java, which has no need for such kludges.

  72. Re:Not the only thing left out: it's for Java only by greenrd · · Score: 2, Insightful
    Another downside to make: People often start with the false assumption that Makefiles are automatically cross-platform, and then find out that they aren't.

    Also, make/automake/autoconf/autoheader/... can be quite complicated and confusing. Whereas ant (and presumably maven) are pretty simple by comparison.