An advice: Jesse, maybe you should wait with further comments till you
have gathered properly working versions of plugins (again); I know how
it is in "the heat of the moment." Then again, the Maven guys could
very well suck, objectively, but I think a sound discussion about that
- and about how to either improve their code base/methodologies and/or
skip using Maven altogether - can only take place when the lost sleep
is forgotten :-)
/David
On Feb 12, 2008, at 2:45 PM, Jesse Kuhnert wrote:
I like Howard because his genuine care for developers always shows
through the API's he creates. It'd be nice if more developers did
this but that's just how it is....lots of people suck =p
On Tue, Feb 12, 2008 at 2:36 PM, Fernando Padilla
<[EMAIL PROTECTED]> wrote:
Maybe there is an 80/20 rule at play here, but I've always been
pretty
happy with maven. But I suppose I'm not pushing the envelope that
much,
and maven is probably a god-send for most projects. :)
Funny I just drew a parallel to Maven and IoC systems like Spring:
Industry standards that Howard hates and wants to avoid. :) :)
Guess I
won't be surprised if we see a Tapestry Build coming along.. :) :)
for
better or for worse..
but I guess I'm glad for Howard's trail blazing attitudes or we would
still be using things like Struts :)
fernando
Howard Lewis Ship wrote:
On Feb 12, 2008 11:16 AM, Christian Edward Gruber
<[EMAIL PROTECTED]> wrote:
True. You can always stop using maven. My problem with that
(purely
in my own experience) is that it replace the gawd-aweful 50K-
worth-of-
ant-scripts/make-files I've inherited. The notion of a stable
lifecycle (even if I have to do more work to lock down the plugins)
ends up being more than worth it. But that's my own situation.
Your
mileage may vary. Given that they're working out some issues at
the
core, I guess the next step after that is to work out quality in
the
plugins themselves.
Anyway, I guess this has really strayed OT. Sorry. It's just
after
having built build system after build system in *make/jam/ant, and
seen the crap that ends up accumulating in corporate builds at my
clients, Maven still seems the cleanest way to get to
reproducible AND
manageable builds. Sad though that may sound.
I've had my fill of Maven and am anxious to move away from it.
Creating a good build is a difficult challenge for most
developers. I
think the majority of devs who take a crack at a build system are
handicapped by not knowing what they don't know.
An experienced dev can leverage the Maven Ant tools or Ivy and
create
a better bulid than Maven and that's the direction I intend to go in
the future.
Christian.
On 12-Feb-08, at 13:33 , Jesse Kuhnert wrote:
I know what will make it stop though.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
