Follow Slashdot stories on Twitter

 


Forgot your password?
Close
typodupeerror
×
Programming Software Apache IT Technology

Apache Maven 1.0 Released 167

Posted by michael from the inspirational-naming dept.
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..."
This discussion has been archived. No new comments can be posted.

Apache Maven 1.0 Released More

Apache Maven 1.0 Released

Comments Filter:

  • Link to project (Score:5, Informative)

    by Inominate ( 412637 ) on Friday July 16, 2004 @03:54PM (#9721437)
    Why do stories like this so often leave out a link to the actual project?

    http://maven.apache.org/ [apache.org]

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

    • Aha. (Score:1, Troll)

      by Inominate ( 412637 )
      It's for karma whoring!

    • Re:Link to project (Score:2, Interesting)

      by strictnein ( 318940 ) *
      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...

      • Re:Link to project (Score:4, Informative)

        by radish ( 98371 ) on Friday July 16, 2004 @04:33PM (#9721800) Homepage
        Errr...it is it's own screenshot. Maven is used to build Maven, and the output is the site you see before you.

      • Screenshot (Score:5, Funny)

        by _xeno_ ( 155264 ) on Friday July 16, 2004 @04:41PM (#9721866) Homepage Journal
        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.)

      • Re:Link to project (Score:5, Informative)

        by legenx ( 751533 ) on Friday July 16, 2004 @04:47PM (#9721933)

        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.

        • Re:Link to project (Score:3, Interesting)

          by sbrown123 ( 229895 )

          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 proj
          • I use qmake [trolltech.com] 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 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 stu
          • Plan 9 provides mk [bell-labs.com], as a replacement for make. There are unix ports [swtch.com] available. Since this isn't really a `better make' story, I'll not post more, but the papers [bell-labs.com] and manual pages [bell-labs.com] (yes, actually used in Plan 9) are often interesting reading regardless.

    • Not the only thing left out: it's for Java only (Score:5, Informative)

      by Anonymous Coward on Friday July 16, 2004 @04:06PM (#9721556)
      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.

    • Re:Link to project (Score:5, Informative)

      by Anonymous Coward on Friday July 16, 2004 @04:12PM (#9721599)
      It's not a project management tool.

      It's a Java programming project management tool.

      There is a huge difference between the two things.
    • Why bother if nobody is gonna RTFA?

  • definition (Score:5, Interesting)

    by zogger ( 617870 ) on Friday July 16, 2004 @04:03PM (#9721523) Homepage Journal
    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 :(

    • Re:definition (Score:5, Funny)

      by MythMoth ( 73648 ) on Friday July 16, 2004 @04:09PM (#9721579) Homepage
      Let me clarify.

      It's a great big pain in the butt.

      • Re:definition (Score:5, Informative)

        by MythMoth ( 73648 ) on Friday July 16, 2004 @05:53PM (#9722540) Homepage
        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.

    • Re:definition (Score:5, Informative)

      by poot_rootbeer ( 188613 ) on Friday July 16, 2004 @04:16PM (#9721639)
      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.

      • Re:definition (Score:3, Insightful)

        by multipartmixed ( 163409 ) *
        > 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.

      • Re:definition (Score:3, Interesting)

        by Atzanteol ( 99067 )
        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...
        • 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.

        • Re:definition (Score:1, Interesting)

          by Anonymous Coward
          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.

        • Re:definition (Score:5, Informative)

          by M1FCJ ( 586251 ) on Friday July 16, 2004 @05:30PM (#9722362) Homepage
          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.

    • Hell, (Score:2, Interesting)

      by eril ( 759876 )
      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.

      • Right .... (Score:1, Funny)

        by Anonymous Coward
        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.
    • 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!)

  • Incredibly useful build tool (Score:5, Informative)

    by d-rock ( 113041 ) on Friday July 16, 2004 @04:04PM (#9721526) Homepage
    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

  • Maven Bile (Score:5, Informative)

    by Anonymous Coward on Friday July 16, 2004 @04:04PM (#9721532)
    The Bileblog has an alternative view [freeroller.net] on Maven.

    • Re:Maven Bile (Score:5, Interesting)

      by malloc ( 30902 ) on Friday July 16, 2004 @04:18PM (#9721656)
      That could win the best-FUD-of-the-year award. Full of scathing remarks, but nary an actual hard fact in sight.

      -Malloc
    • 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.

    • Re:Maven Bile (Score:3, Interesting)

      by bokmann ( 323771 )
      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

      • Re:Maven Bile (Score:1, Informative)

        by Anonymous Coward
        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

    • Re:Maven Bile (Score:5, Informative)

      by Knight2K ( 102749 ) on Friday July 16, 2004 @05:31PM (#9722374) Homepage
      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.

    • try the ACTUAL bile (Score:3, Informative)

      by BoxedFlame ( 231097 )
      Why Maven Sucks [jroller.com]

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

  • Java (Score:3, Informative)

    by yamla ( 136560 ) <chris@@@hypocrite...org> on Friday July 16, 2004 @04:10PM (#9721589)
    This is only for Java projects, it seems.
  • Hum, this headline caused me some confusion.

    In danish 'maven' is the word for stomach.

    Well, can't win them all :)
  • Codebusters?

  • Check out JAM for Maven (Score:5, Informative)

    by alphafoo ( 319930 ) <loren@boxbe.com> on Friday July 16, 2004 @04:28PM (#9721744) Homepage
    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 [javagen.com].

    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 [eclipse.org] setup.
    • 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" [perforce.com] 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.

  • Its a love it or hate it project (Score:3, Insightful)

    by Timesprout ( 579035 ) on Friday July 16, 2004 @04:30PM (#9721766)
    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
    • 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.

    • Re:Its a love it or hate it project (Score:5, Informative)

      by svetlin ( 223242 ) on Friday July 16, 2004 @07:37PM (#9723132)
      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 [apache.org].

      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
  • 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.
  • Maven may be "neat" to some, but it also has real issues [jroller.com]...

    • Re:Maven Great??? (Score:3, Insightful)

      by lorcha ( 464930 )
      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?

  • A different opinion (Score:5, Interesting)

    by joeykiller ( 119489 ) on Friday July 16, 2004 @05:03PM (#9722117) Journal
    Not everyone seems to be fond of Maven. This guy [jroller.com] 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.

  • Java as a system facility (Score:4, Interesting)

    by Brian Blessed ( 258910 ) on Friday July 16, 2004 @05:11PM (#9722183)
    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.
    • 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-
      • 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

    • 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 [apple.com]. 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?).

  • It a time saver (Score:1, Informative)

    by Anonymous Coward
    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.

  • My impressions of maven (Score:4, Informative)

    by scrytch ( 9198 ) <chuck@myrealbox.com> on Friday July 16, 2004 @06:41PM (#9722839)
    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.

  • It is a build tool . (Score:5, Insightful)

    by Anonymous Coward on Friday July 16, 2004 @06:55PM (#9722922)
    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.

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

    Uhm... what?
  • "Maven has a long history of pushing out beta after beta, "
    If only they had a good project management tool.
  • 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

  • Maven is badly designed (Score:1, Interesting)

    by Anonymous Coward
    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 t

Slashdot Top Deals

"Hello again, Peabody here..." -- Mister Peabody

Close