On 30.01.2009 18:04, Andy Stevens wrote:
I uploaded
https://issues.apache.org/jira/browse/COCOON-1887 2 1/2 years ago and
it's still waiting, even though it's a relatively trivial change and
only about half a dozen lines of code if you ignore the comments and
unit test :-(
Hey Andy,
this
2009/2/23 Joerg Heinicke joerg.heini...@gmx.de:
Hey Andy,
this particular patch has been applied.
Thanks,
Joerg
That's great; thanks.
Andy.
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional
On 30.01.2009 18:04, Andy Stevens wrote:
Nobody said 2.1 is dead, it is clearly (IMHO) in maintenance mode.
Sounds good in theory, but the big assumption is that submitted
patches might actually be applied. I uploaded
https://issues.apache.org/jira/browse/COCOON-1887 2 1/2 years ago and
it's
Andreas
No; I did not say that I thought 2.1 *was* unsupported, just that
I hoped it would not be. Believe me, I do really appreciate the
generous effort and commitment from the experts that helps out
those of who do not get all the nuances as quickly.
I also did not take any offence - the
Klortho schrieb:
dhohls wrote:
That's a little harsh - although my impression is that C2.2 is
perhaps a step sideways in terms of how many things are
done... but that's just an impression from reading all the
mailing list QA. So far, I have not needed to take the plunge.
Yes, you're
Andreas
Do you want the short reply or the long reply :)
Short:
There needs to be room in the Cocoon universe for 2.1 users as
well as 2.2 users.
Long:
This is the classic issue isn't it!? Certainly we are beset by the
culture of the new at present; where new == better - be it
cellphones,
Hi Derek,
Derek Hohls schrieb:
[…]
I agree from a *marketing* perspective that putting buzzwords
on your site is a way to attract new users - especially those who
might otherwise be going to .NET or Ruby-on-Rails - not that I mean
to imply the developers are doing this for that reason
Hi,
For us, as a project depending on Cocoon, it is crucial that Cocoon
doesn't cling to dead (as in language) concepts and frameworks as XSP
and Avalon, however proven and stable they may be. To attract new
community members, it's very important to keep looking beyond one's own
nose and
Hi Klortho,
What happened to the really nice exception pages? Is there any way
I can
get them back?
Have you looked at
http://cocoon.apache.org/2.2/core-modules/core/2.2/1379_1_1.html
?
-
To unsubscribe, e-mail:
It's not only about taking the road less traveled ... certainly not if you
get the impression that it seems to be going the wrong way.
I am convinced that a lot of cocoon users were convinced that cocoon was
powerful useful ... until 2.2
We all know Cocoon has a rather steep learning curve, but
Hi all,
I sometimes feel there is unfortunately no constructive debate about
this topic (2.1 vs 2.2). And as you say, Bart, blaming people who remain
unsatisfied with 2.2 seems to be the answer though it's a bit easy.
For example, I have a lot of Cocoon apps with many XSP and Cocoon 2.2
On Fri, Jan 30, 2009 at 4:41 PM, DAVIGNON Andre - CETE
NP/DIODé/PANDOC andre.davig...@developpement-durable.gouv.fr wrote:
...I have a lot of Cocoon apps with many XSP and Cocoon 2.2 does
not support XSP. I don't know what to do with this apps in the future when
2.1 is no longer supported
Klortho pisze:
Well, thanks much for the suggestion, but it didn't work. I did some
experimenting, and tried pulling this out of a 2.1 sitemap and inserting it
at the top of my new sitemap:
map:components
map:generators default=file
map:generator name=exception
Grzegorz Kossakowski pisze:
AFAIR this is a fix for this regression. It has been incorporated in released
version yet, unfortunately.
Should be:
It has been NOT incorporated in released version yet, unfortunately.
--
Grzegorz Kossakowski
2009/1/30 Bertrand Delacretaz bdelacre...@apache.org:
On Fri, Jan 30, 2009 at 4:41 PM, DAVIGNON Andre - CETE
NP/DIODé/PANDOC andre.davig...@developpement-durable.gouv.fr wrote:
2.1 can stay supported as long as people support it ;-)
Former colleagues of mine are still maintaining 2.1 apps
I for one think that when releasing a new version, a lot of deference should
be given to the newbie. Don't make it harder to get started using.
Dropping old deprecated features might be fine, but 2.1, in addition to the
nice exception pages, had a very nice welcome page with lots of links to
Hi, I'm revisiting Cocoon after a long hiatus, and getting started with maven
and C2.2.
The first thing I've noticed is that the really nice exception pages are
completely gone. Now, if I have a problem in my sitemap or in an XSLT, for
example, all I can see is the stack trace in the console
: Klortho [mailto:voldr...@gmail.com]
Sent: donderdag 29 januari 2009 22:57
To: users@cocoon.apache.org
Subject: Getting started with C2.2 -- where's the exception information?
Hi, I'm revisiting Cocoon after a long hiatus, and getting started with
maven
and C2.2.
The first thing I've noticed
Robby Pelssers-2 wrote:
Try adding
map:handle-errors
map:generate type=exception/
map:serialize type=xml/
/map:handle-errors
To the pipeline.
Well, thanks much for the suggestion, but it didn't work. I did some
experimenting, and tried
That's a little harsh - although my impression is that C2.2 is
perhaps a step sideways in terms of how many things are
done... but that's just an impression from reading all the
mailing list QA. So far, I have not needed to take the plunge.
On 2009/01/30 at 01:51, in message
dhohls wrote:
That's a little harsh - although my impression is that C2.2 is
perhaps a step sideways in terms of how many things are
done... but that's just an impression from reading all the
mailing list QA. So far, I have not needed to take the plunge.
Yes, you're right ... too
You may be correct; but I have never felt that Cocoon was
striving for acceptance. It simply is what it is; and you either
find it incredibly powerful and useful ... or become a mainstream
php/ruby developer. If you are here, its because you have taken
the road (development route?!) less
22 matches
Mail list logo
