You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Jesse Kuhnert <jk...@gmail.com> on 2008/02/12 16:58:07 UTC
f-ed by maven again...
Just a warning that something funky seems to have happened lately as
we've lost the majority of documentation for anything not on the main
Tapestry 4.1 site. (ie core / contrib / annotations / etc)
You can see this if you click on "Tapestry Core / Contrib" from the
left hand menu on the 4.1 site at
http://tapestry.apache.org/tapestry4.1/.
I'm not sure what to do about this right now but it seems like it's
probably concerning enough that I may be forced to take drastic action
to get it fixed.
F-ing asshole maven developers. ....I swear they seem so f-ing
retarded sometimes.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Jesse Kuhnert <jk...@gmail.com>.
...............................seems to be fixable by reverting site
plugin to beta-5. Hooray for gross incompetence.
maven fail
(is funnier if you've seen that web site about different kinds of failures)
On Tue, Feb 12, 2008 at 10:58 AM, Jesse Kuhnert <jk...@gmail.com> wrote:
> Just a warning that something funky seems to have happened lately as
> we've lost the majority of documentation for anything not on the main
> Tapestry 4.1 site. (ie core / contrib / annotations / etc)
>
> You can see this if you click on "Tapestry Core / Contrib" from the
> left hand menu on the 4.1 site at
> http://tapestry.apache.org/tapestry4.1/.
>
> I'm not sure what to do about this right now but it seems like it's
> probably concerning enough that I may be forced to take drastic action
> to get it fixed.
>
> F-ing asshole maven developers. ....I swear they seem so f-ing
> retarded sometimes.
>
> --
> Jesse Kuhnert
> Tapestry / OGNL / Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Christian Edward Gruber <ch...@gmail.com>.
On 12-Feb-08, at 14:21 , Howard Lewis Ship wrote:
> 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.
True. Probably the reason I did gravitate towards maven (and am
likely to remain there) is that I kept re-inventing the same lifecycle
over and over. I've built inter-project dependencies into an ant
build, common 3rd party libs, etc. Maven was the first one to actually
cast that lifecycle into the standard mode, to handle dependency
through metadata, support centralized artifact management, and allowed
for easier project refactoring into much smaller (and more testable,
isolated units (modules). Probably I'm stubborn too because I spent
so long working wtih the OpenBSD 3rd party ports system which has a
sane default lifecycle. You're right, I could probably build my own
with ant/whatever. Heck, I could do it with shell scripts if it came
to that. but now that I'm used to maven, 9 times out of 10 it's
easier for me to constrain/adapt maven than to build it all over
again. Maybe it's as simple as I like what maven could/should be
enough that I merely haven't given up on it/them yet. But I continue
to be astounded at how much Maven seems to have interfered with your
lives when I've just not had that much of a problem with it.
Anyway, your guys' project, your guys' build options. Just please
publish maven artifacts and metadata and I certainly won't care what
you use to build it.
Christian.
P.S. I'm actually going to drop this now - this got casual and chit-
chatty, but this is a dev list, not a maven user list. -cg.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by David Bergman <Da...@remoteproximity.com>.
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
> <fe...@alum.mit.edu> 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
>>> <ch...@gmail.com> 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: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
> --
> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Howard Lewis Ship <hl...@gmail.com>.
On Feb 12, 2008 11:45 AM, Jesse Kuhnert <jk...@gmail.com> 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
Thanks, Jesse, I do try to do all my work with the end developer in mind.
>
>
> On Tue, Feb 12, 2008 at 2:36 PM, Fernando Padilla <fe...@alum.mit.edu> 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..
> >
There will be a build for Tapestry but it won't be a product. It will
use the appropriate tools (Ant, Gant, Buildr, whatever) to build and
test the code, generate the docs and reports, and package it all up
for deployment via Maven.
Maven in theory makes it super easy for people to build from source,
and that's a good thing ... but the Bamboo CI server and nightly
snapshot repository makes that much less of an issue. The people
interested in building from
source will still figure it out and everyone else can just point Ivy
or Maven at the right repository and version.
> > 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
> > > <ch...@gmail.com> 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: dev-unsubscribe@tapestry.apache.org
> > >> For additional commands, e-mail: dev-help@tapestry.apache.org
> > >>
> > >>
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
>
> --
> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Jesse Kuhnert <jk...@gmail.com>.
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 <fe...@alum.mit.edu> 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
> > <ch...@gmail.com> 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: dev-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>
> >>
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Fernando Padilla <fe...@alum.mit.edu>.
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
> <ch...@gmail.com> 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: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Howard Lewis Ship <hl...@gmail.com>.
On Feb 12, 2008 11:16 AM, Christian Edward Gruber
<ch...@gmail.com> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Jesse Kuhnert <jk...@gmail.com>.
Yeah....that is the sad part. Finding a suitable replacement.
Makes it even easier to hate it this way.
On Tue, Feb 12, 2008 at 2:16 PM, Christian Edward Gruber
<ch...@gmail.com> wrote:
<snipped>
>> 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.
>
> Christian.
</snipped>
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Christian Edward Gruber <ch...@gmail.com>.
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.
Christian.
On 12-Feb-08, at 13:33 , Jesse Kuhnert wrote:
> I know what will make it stop though.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Jesse Kuhnert <jk...@gmail.com>.
Hehe...Nice try. ;)
Tell that to the books and articles page here:
http://tapestry.apache.org/articles.html
I tried every single released site plugin version available to get my
image style attributes to stick without success. It seems to have
recently been fixed "magically" - but locking down versions doesn't do
much for you either a lot of the time.
I know what will make it stop though.
On Tue, Feb 12, 2008 at 1:26 PM, Hilco Wijbenga
<hi...@gmail.com> wrote:
> On Feb 12, 2008 8:44 AM, Jesse Kuhnert <jk...@gmail.com> wrote:
> > They don't do any reasonable amount of testing at all. I used a
> > released and theoretically stable plugin (is in the core ibiblio repo)
> > and it just flat out didn't work.
>
> Whereas I don't disagree with you that the plugins (especially,
> Maven's own) are not as stable as I'd like them to be ... if you don't
> lock down your plugin versions guaranteeing a reproducible build, then
> you're just asking for it. Maven isn't perfect but I don't think you
> should blame it for doing strange things when given an inherently
> unreproducible build. Lock down your versions.
>
> I completely understand your frustration but until you lock down your
> plugin versions, don't blame Maven.
>
> (Maybe they release broken plugins just to make sure you lock down
> your versions. ;-) :-D )
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Hilco Wijbenga <hi...@gmail.com>.
On Feb 12, 2008 8:44 AM, Jesse Kuhnert <jk...@gmail.com> wrote:
> They don't do any reasonable amount of testing at all. I used a
> released and theoretically stable plugin (is in the core ibiblio repo)
> and it just flat out didn't work.
Whereas I don't disagree with you that the plugins (especially,
Maven's own) are not as stable as I'd like them to be ... if you don't
lock down your plugin versions guaranteeing a reproducible build, then
you're just asking for it. Maven isn't perfect but I don't think you
should blame it for doing strange things when given an inherently
unreproducible build. Lock down your versions.
I completely understand your frustration but until you lock down your
plugin versions, don't blame Maven.
(Maybe they release broken plugins just to make sure you lock down
your versions. ;-) :-D )
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Jesse Kuhnert <jk...@gmail.com>.
Yeah, that sounds reasonable in theory but I've seen these nice guys
do their thing first hand while contributing code back to the project.
They don't do any reasonable amount of testing at all. I used a
released and theoretically stable plugin (is in the core ibiblio repo)
and it just flat out didn't work.
They did the same kind of stuff with surefire too. (the current
theoretical stable release of that is a huge pile of doo-doo btw, it
does execute with the latest testng versions but has also reverted
back to creating unwanted test-output directories all over the place
as well as creating a single "Command Line Suite.txt" output report
with no incremental progress indicator for which test is being run)
Bah.
On Tue, Feb 12, 2008 at 11:37 AM, Christian Edward Gruber
<ch...@gmail.com> wrote:
> This very issue is at the core of current design decisions for both
> Maven 2.1 and updates along the 2.0.x branch. They're pretty close to
> finding a decent way to stabilize plugin sets. I suspect by next
> release of 2.0.x there will be a "default set" of plugins for that
> version of maven that you can override, but unless you do, you'll get
> that set of working plugins.
>
> And for the record, they are decent people trying very hard to solve a
> variety of problems with a very diverse set of users with vastly
> different priorities. This is a community, and some respectful
> collegiality is not out of line here. They may seem retarded to you,
> but I've heard the same thing from jerks I've worked with who bitch
> and complain about how flakey Tapestry is and how they chose web-works
> instead because of it. This would all go a lot better if people
> stopped bitching and consulted with each other and/or contributed code
> (and yes, I've contributed patches, not to this project, but to
> continuum, wotonomy, openbsd, and others). Your stress is totally
> valid, and I agree that plugin sets should be stable. On the other
> hand, however, if you lock down your plugins as per all the best
> practices discussed on the Maven users list, you would also obviate
> this problem until they have it resolved in the default tool behaviour.
>
> Christian.
>
>
>
>
> On 12-Feb-08, at 10:58 , Jesse Kuhnert wrote:
>
> > Just a warning that something funky seems to have happened lately as
> > we've lost the majority of documentation for anything not on the main
> > Tapestry 4.1 site. (ie core / contrib / annotations / etc)
> >
> > You can see this if you click on "Tapestry Core / Contrib" from the
> > left hand menu on the 4.1 site at
> > http://tapestry.apache.org/tapestry4.1/.
> >
> > I'm not sure what to do about this right now but it seems like it's
> > probably concerning enough that I may be forced to take drastic action
> > to get it fixed.
> >
> > F-ing asshole maven developers. ....I swear they seem so f-ing
> > retarded sometimes.
> >
> > --
> > 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: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: f-ed by maven again...
Posted by Christian Edward Gruber <ch...@gmail.com>.
This very issue is at the core of current design decisions for both
Maven 2.1 and updates along the 2.0.x branch. They're pretty close to
finding a decent way to stabilize plugin sets. I suspect by next
release of 2.0.x there will be a "default set" of plugins for that
version of maven that you can override, but unless you do, you'll get
that set of working plugins.
And for the record, they are decent people trying very hard to solve a
variety of problems with a very diverse set of users with vastly
different priorities. This is a community, and some respectful
collegiality is not out of line here. They may seem retarded to you,
but I've heard the same thing from jerks I've worked with who bitch
and complain about how flakey Tapestry is and how they chose web-works
instead because of it. This would all go a lot better if people
stopped bitching and consulted with each other and/or contributed code
(and yes, I've contributed patches, not to this project, but to
continuum, wotonomy, openbsd, and others). Your stress is totally
valid, and I agree that plugin sets should be stable. On the other
hand, however, if you lock down your plugins as per all the best
practices discussed on the Maven users list, you would also obviate
this problem until they have it resolved in the default tool behaviour.
Christian.
On 12-Feb-08, at 10:58 , Jesse Kuhnert wrote:
> Just a warning that something funky seems to have happened lately as
> we've lost the majority of documentation for anything not on the main
> Tapestry 4.1 site. (ie core / contrib / annotations / etc)
>
> You can see this if you click on "Tapestry Core / Contrib" from the
> left hand menu on the 4.1 site at
> http://tapestry.apache.org/tapestry4.1/.
>
> I'm not sure what to do about this right now but it seems like it's
> probably concerning enough that I may be forced to take drastic action
> to get it fixed.
>
> F-ing asshole maven developers. ....I swear they seem so f-ing
> retarded sometimes.
>
> --
> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org