• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: maven.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: maven.


  • Subject: Re: maven.
  • From: Mike Schrag <email@hidden>
  • Date: Fri, 3 Apr 2009 22:43:57 -0400

That all depends on what you mean by out of the box. Both build systems rely on WebObjects being installed.
Beyond that what out of the box are you referring to?
I consider WOLips the product I deliver, so I mean WOLips out-of-the- box.

Even now on the mailing list there's constant questions about how do achieve things with the current build process. I'm not suggesting this is your fault, but it's not all plain sailing 'tis all I'm saying.
SSDD/War builds, sucky (but admittedly essentially never touched) ... Inter-project build dependencies, sucky. #1 I'm guessing Maven doesn't have much to offer without custom coding, either, though, #2 almost certainly Maven addresses. I'm not sure what other "constant questions" there are. And I do take the blame for anything that sucks that I touched :)

Creating a simple project is easy in both systems is my suggestion. Adding project dependencies IMHO is easier with maven.
Granted, the onus is on us to do better with the wiki.
IMO, the simple project is not as simple for WO people to use Maven. Not that it can't be, but it just isn't now.

I want people to launch WOLips and things just work.
Sure. The reason why this doesn't currently work out of the box for maven-based apps is to do with WO's need for bundles. We (the maven dudes) are already talking through this. Should be simple.
I hope it gets great and I'm compelled to switch.

Still now in a shared environment it relies on users systems, intranet build systems having the same installed frameworks rather than centralised and auto-downloaded etc. What if you want to roll back to a specific version of wonder etc? Does that happen automatically on every system by a simple declaration of a property? It's easy for me to install a central release of wonder, for example, update the master pom with that version, commit to svn and everyone else gets it by virtue of an svn up.
I've always said that Maven supports dependency management that the others don't. I've never said Maven is *useless*, rather that, for the problems I have, it seems far to complex. That said, I have never felt like dependencies was really THAT big of a deal for me. We have a set of dependencies we rely on and those are in frameworks. It's not perfect. It has flaws. But it's easy. And when something goes wrong, it's pretty easy to fix. I've never rolled back a version of Wonder, but then having commit access maybe makes that an easier problem to solve :) I would like to have autobuilding dependencies and project dependencies that dynamically build, yes, but do I want to trade that for Maven ...... still not feeling it.
You haven't described the problem you're trying to solve... dependencies are easy in both systems (though I believe it's easier in maven - but that's besides the point).
I think Maven clearly beats anything we have to offer for dependency management.

You haven't started this whole thread for curiosities sake. Let's, for arguments sake, assume you've started working on a project that's currently using maven and that this is the reason for your posts and you're perhaps considering whether or not to migrate said projects back from maven to ant ... I want to know why.
Honestly, it's purely curiosities' sake. Yes, I have a project I've started working on that does in fact use Maven, but it is what it is and it's not going to change whether I want it to or not. What I want to know is whether I should migrate my projects from ant TO maven, I really do have genuine intentions here. People who use WebObjects tend to swear by it. People who never have often tend to disparage it. It seems to me that Maven is a similar technology in terms of fandom and ... hate..dom? The people who use and love Maven aren't dumb, they clearly found something that made their lives better. I don't really think I'll be able to make a fair judgment without actually trying to use it for real, though, I'm just trying to decide for myself whether the payoff is worth the investment is all.

What problem are you having?
Is this open-ended or specifically with Maven :)

ms

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: maven.
      • From: Lachlan Deck <email@hidden>
References: 
 >maven. (From: Mike Schrag <email@hidden>)
 >Re: maven. (From: Henrique Prange <email@hidden>)
 >Re: maven. (From: Mike Schrag <email@hidden>)
 >Re: maven. (From: Lachlan Deck <email@hidden>)
 >Re: maven. (From: Mike Schrag <email@hidden>)
 >Re: maven. (From: Lachlan Deck <email@hidden>)

  • Prev by Date: Re: maven.
  • Next by Date: Re: maven.
  • Previous by thread: Re: maven.
  • Next by thread: Re: maven.
  • Index(es):
    • Date
    • Thread