Stefan Pietschmann wrote:
Hmm, i'm not really into this, so it is as simple as exchanging the
XMLSerializer with the 2.1.5 version before building, or are there other
dependencies?
Cheers,
Stefan
I went and did diffs on XMLSerializer and its base classes. Only
AbstractTextSerializer changed
Ralph Goers wrote:
URDINA Michal wrote:
Thanx!
Your PageLabels seem like great enhancement to the portal engine.
Need to look closer but seems like caching of portlet content will be
breeze with pagelinks in use.
But there is one issue remaining. I am afraid that links don't work
on first
Bertrand Delacretaz wrote:
...
Advantages:
...
I agree with your motivation. I would also like to add that when we have
introduced a separate formating layer and enforced side effect free
templates, the conceptual difference between transforming XML input in a
transformer and reading from, e.g.
Le 6 déc. 04, à 10:10, Daniel Fagerstrom a écrit :
big-snip cause=fully agree/
...BTW: I'm becoming more and more worried about the attribute
template sytax that you used in your examples ;)
I hope the syntax in my examples is so bad that people just dismiss it
and focus on the rest of the story
Automated Cocoon Unit tests failed!
Full log file if this unit test run is available here:
http://nagoya.apache.org/~vadim/cocoon-test-log-20041206.log
Last messages from the log file:
==
[foreach] reader-mime-type.xml:39
Stefan Pietschmann wrote:
Hmm, i'm not really into this, so it is as simple as exchanging the
XMLSerializer with the 2.1.5 version before building, or are there other
dependencies?
We have two different XML serializers. IIRC we changed
the the default implementation recently. All you need
to do is
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32083.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32083.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
I have the same problem.Using tab is to make xml file look nice.
- Original Message -
From: Torsten Curdt [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, December 06, 2004 5:54 PM
Subject: Re: AW: XMLSerializer replaces tabs with #9;
Stefan Pietschmann wrote:
Hmm, i'm not
I have the same problem.Using tab is to make xml file look nice.
Well ...no problem using spaces for that over here ;-)
...even makes them look nice in every editor
cheers
--
Torsten
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32541.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Reinhard Poetz wrote:
IIRC we aggreed that we like the current syntax of JXTemplate.
Exception: We deprecate the #{} notation in favour of ${xpath:}.
If nobody said this already (I have 150 or so mails to go ...), more than one EL
per template is clear FS to me. I'd be in favor of specifying
Le 6 déc. 04, à 15:07, Vadim Gritsenko a écrit :
Reinhard Poetz wrote:
IIRC we aggreed that we like the current syntax of JXTemplate.
Exception: We deprecate the #{} notation in favour of ${xpath:}.
If nobody said this already (I have 150 or so mails to go ...), more
than one EL per template
On Dec 6, 2004, at 8:14 AM, Bertrand Delacretaz wrote:
Le 6 déc. 04, à 15:07, Vadim Gritsenko a écrit :
Reinhard Poetz wrote:
IIRC we aggreed that we like the current syntax of JXTemplate.
Exception: We deprecate the #{} notation in favour of ${xpath:}.
If nobody said this already (I have 150
Le 6 déc. 04, à 15:41, Glen Ezkovich a écrit :
On Dec 6, 2004, at 8:14 AM, Bertrand Delacretaz wrote:
Le 6 déc. 04, à 15:07, Vadim Gritsenko a écrit :
Reinhard Poetz wrote:
IIRC we aggreed that we like the current syntax of JXTemplate.
Exception: We deprecate the #{} notation in favour of
Daniel Fagerstrom wrote:
Bertrand Delacretaz wrote:
Le 6 déc. 04, à 15:41, Glen Ezkovich a écrit :
On Dec 6, 2004, at 8:14 AM, Bertrand Delacretaz wrote:
Le 6 déc. 04, à 15:07, Vadim Gritsenko a écrit :
Reinhard Poetz wrote:
IIRC we aggreed that we like the current syntax of JXTemplate.
On Dec 6, 2004, at 8:49 AM, Bertrand Delacretaz wrote:
Le 6 déc. 04, à 15:41, Glen Ezkovich a écrit :
On Dec 6, 2004, at 8:14 AM, Bertrand Delacretaz wrote:
Le 6 déc. 04, à 15:07, Vadim Gritsenko a écrit :
Reinhard Poetz wrote:
IIRC we aggreed that we like the current syntax of JXTemplate.
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
IIRC we aggreed that we like the current syntax of JXTemplate.
Exception: We deprecate the #{} notation in favour of ${xpath:}.
If nobody said this already (I have 150 or so mails to go ...),
Yeah, cocoon-dev has gone crazy
On Dec 6, 2004, at 9:00 AM, Sylvain Wallez wrote:
Reinhard Poetz wrote:
Yeah, cocoon-dev has gone crazy during the week-end :-)
more than one EL per template is clear FS to me. I'd be in favor of
specifying EL at the TemplateGenerator declaration time, and would
not go more granular than this.
In case you are wondering, I just randomly chose NET. It stands for Never
Ending Topic.
At the risk of raising Stefano's alarm, what is so wrong with creating a
general template transformer as well as a generator that support pluggable
expression languages. That isn't really much different than
On Monday 06 December 2004 23:00, Sylvain Wallez wrote:
In that case, a single EL is just painful.
Furthermore, specifying the language in the component declaration
doesn't help readability nor reuse of templates between projects.
Is it only me? I like Java a lot, and how come I can't
Antonio Gallardo wrote:
Hi:
Seems like the quartz lib changed the interface: DriverDelegate. I tried
to find inside our shipped quartz*.jar the new method and it does not
exists.
What to do? A workaround is to use in the project block the quartz shipped
with cocoon.
How about contacted them and
Torsten Curdt wrote:
Stefan Pietschmann wrote:
Hmm, i'm not really into this, so it is as simple as exchanging the
XMLSerializer with the 2.1.5 version before building, or are there other
dependencies?
We have two different XML serializers. IIRC we changed
the the default implementation recently.
Bertrand Delacretaz wrote:
Le 6 déc. 04, à 15:57, Daniel Fagerstrom a écrit :
...What about being able to mix Groovy's XML sytax with the the
ordinary one, wouldn't that be nice ;)
(you just forgot to add the sound of Stefano's FS detector exploding in
the background)
ROTFL
I love you guys :-)
So the question remains: when using tabs (and I do use them cause they're
used by default in XMLSpy and I cannot convert all my xml files to
whitespaces) - is it the intended behavior of the (new implementation of
the) XMLSerializer to replace all of them with the #9; entity?
Stefan
Hi Torsten,
I tried replacing
xml-serializer
class=org.apache.cocoon.components.sax.XMLByteStreamCompiler
logger=core.xml-serializer pool-grow=4 pool-max=32 pool-min=8/
with
xml-serializer class=org.apache.cocoon.components.sax.XMLSerializer
logger=core.xml-serializer pool-grow=4 pool-max=32
Stefan Pietschmann wrote:
So the question remains: when using tabs (and I do use them cause they're
used by default in XMLSpy and I cannot convert all my xml files to
whitespaces) - is it the intended behavior of the (new implementation of
the) XMLSerializer to replace all of them with the #9;
I tried replacing
xml-serializer
class=org.apache.cocoon.components.sax.XMLByteStreamCompiler
logger=core.xml-serializer pool-grow=4 pool-max=32 pool-min=8/
with
xml-serializer class=org.apache.cocoon.components.sax.XMLSerializer
logger=core.xml-serializer pool-grow=4 pool-max=32 pool-min=8/
Niclas Hedhman wrote:
On Monday 06 December 2004 23:00, Sylvain Wallez wrote:
In that case, a single EL is just painful.
Furthermore, specifying the language in the component declaration
doesn't help readability nor reuse of templates between projects.
Is it only me? I like Java a lot, and
Glen Ezkovich wrote:
On Dec 6, 2004, at 9:00 AM, Sylvain Wallez wrote:
Reinhard Poetz wrote:
Yeah, cocoon-dev has gone crazy during the week-end :-)
more than one EL per template is clear FS to me. I'd be in favor of
specifying EL at the TemplateGenerator declaration time, and would
not go
FYI, my default sitemap has:
map:serializer logger=sitemap.serializer.xml mime-type=text/xml
name=xml src=org.apache.cocoon.serialization.XMLSerializer/
and
map:serializer logger=sitemap.serializer.exml
mime-type=text/xml name=exml
Micah Dubinko wrote:
FYI, my default sitemap has:
map:serializer logger=sitemap.serializer.xml mime-type=text/xml
name=xml src=org.apache.cocoon.serialization.XMLSerializer/
and
map:serializer logger=sitemap.serializer.exml mime-type=text/xml
name=exml
On Dec 6, 2004, at 3:32 PM, Sylvain Wallez wrote:
Hmmm... why does this happen? It seems that the java could be
injected by by one component and the XML by another.
Not always, e.g. when you have an XML document and objects describing
its metadata which are both managed by a flowscript.
I did
Bertrand Delacretaz wrote:
Le 5 déc. 04, à 06:14, Stefano Mazzocchi a écrit :
Bertrand Delacretaz wrote:
...That's what I mean - having a transformer that can use the same
template syntax as used in the generator, so that the template
language can be used for both the generation and
Torsten Curdt wrote:
...at least in Germany we celebrate the 6th of Dec
with little presents.
Well, I finished my little present for you guys just in
time (about an hour ago). Ladies and gentleman:
...we have auto-compiling javaflow!!
My idea was to build a little nikolaus-flow application.
...but
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
...
Furthermore, specifying the language in the component declaration
doesn't help readability nor reuse of templates between projects.
If you don't see any better way out, I'd go as far as allowing to
choose EL in template
Daniel Fagerstrom wrote:
Just a reminder; before you guys start implementing one or another template
language, could we have [VOTE] for one of the variants, have [PROPOSAL], or at
least [SUMMARY]? :)
Here, I just want to comment that I find way more intuitive and user friendly
following
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30084.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30084.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
On Tue, 2004-12-07 at 00:45 +0100, Jonas Ekstedt wrote:
On Mon, 2004-12-06 at 22:32 +0100, Sylvain Wallez wrote:
Glen Ezkovich wrote:
On Dec 6, 2004, at 9:00 AM, Sylvain Wallez wrote:
Reinhard Poetz wrote:
Yeah, cocoon-dev has gone crazy during the week-end :-)
Torsten Curdt wrote:
I'll peek around in [org.apache.cocoon.serialization.XMLSerializer]
to see if I can figure out what's going on.
Better spend the time in fixing the last
few issues in
[org.apache.cocoon.components.serializers.XMLSerializer]. ...that means
(again) our homegrown one is
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-xsp *no longer* has an issue.
The current state of this project is
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-session-fw *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-batik *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-chaperon *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-databases *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-hsqldb *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-taglib *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-html *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-itext *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-jfor *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-linkrewriter *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-velocity *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-midi *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-paranoid *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-profiler *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-python *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-serializers *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-slop *no longer* has an issue.
The current state of this project
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-template has an issue affecting its community integration.
This
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-web3 *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-woody *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-forms *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-authentication-fw *no longer* has an issue.
The current state of
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-bsf *no longer* has an issue.
The current state of this project is
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-deli *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-jms *no longer* has an issue.
The current state of this project is
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-portal *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-linotype *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-naming *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-portal-fw *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-qdox *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-stx *no longer* has an issue.
The current state of this project is
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-asciiart *no longer* has an issue.
The current state of this
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-cron has an issue affecting its community integration.
This issue
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-faces *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-lucene *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-querybean *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-axis *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-fop *no longer* has an issue.
The current state of this project is
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-proxy *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-tour *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-apples *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-jsp *no longer* has an issue.
The current state of this project is
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-eventcache *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-repository *no longer* has an issue.
The current state of this
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30084.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32083.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32083.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Le 7 déc. 04, à 00:43, Torsten Curdt a écrit :
...we have auto-compiling javaflow!!
Wow - thanks Torsten, looking forward to testing this!
-Bertrand
smime.p7s
Description: S/MIME cryptographic signature
Torsten Curdt wrote:
...at least in Germany we celebrate the 6th of Dec
with little presents.
Well, I finished my little present for you guys just in
time (about an hour ago). Ladies and gentleman:
...we have auto-compiling javaflow!!
What on earth can we give you as a return gift?
Community
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-template has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-cron has an issue affecting its community integration.
This issue
93 matches
Mail list logo
