On Friday 14 March 2003 22:01, Nicola Ken Barozzi wrote:
Stefano Mazzocchi wrote, On 14/03/2003 14.49:
But I would like to be able to build cocoon without them and prevent
people with the ability to use them to solve their problems. Just like
Carsten wants to do with the flow or XSP.
Niclas Hedhman wrote, On 15/03/2003 9.25:
On Friday 14 March 2003 22:01, Nicola Ken Barozzi wrote:
Stefano Mazzocchi wrote, On 14/03/2003 14.49:
But I would like to be able to build cocoon without them and prevent
people with the ability to use them to solve their problems. Just like
Carsten
Niclas Hedhman wrote, On 15/03/2003 9.25:
On Friday 14 March 2003 22:01, Nicola Ken Barozzi wrote:
Stefano Mazzocchi wrote, On 14/03/2003 14.49:
But I would like to be able to build cocoon without them and prevent
people with the ability to use them to solve their problems. Just like
Carsten
On Saturday 15 March 2003 17:37, Nicola Ken Barozzi wrote:
Niclas Hedhman wrote, On 15/03/2003 9.25:
On Friday 14 March 2003 22:01, Nicola Ken Barozzi wrote:
Stefano Mazzocchi wrote, On 14/03/2003 14.49:
But I would like to be able to build cocoon without them and prevent
people with the
Niclas Hedhman wrote, On 15/03/2003 11.01:
On Saturday 15 March 2003 17:37, Nicola Ken Barozzi wrote:
...
Any suggestion on what you would want to have to create your customized
version of Cocoon given the above point?
Well, I am not in that position, just came yo think about the possibility...
explicitely asking for opinions over here
Original Message
Subject: Re: [heads-up] wiki abuse: your advice please
Date: Sat, 15 Mar 2003 11:48:15 +0100
From: Steven Noels [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Organization: Outerthought
To: [EMAIL PROTECTED]
References:
hi,
Today one of the blocks is broken. I tried to get around
it as usual by un-commenting the line in local.blocks.properties
to no avail.
i made a CVS update, and had no problem running build webapp,
i even tried setting in local.block.properties all
entries from
#exclude.block.XXX=true to
On Saturday 15 March 2003 18:29, Matt Sergeant wrote:
On Friday, Mar 14, 2003, at 13:46 Europe/London, Steven Noels wrote:
while briefly checking the Wiki, I was confronted with some apparent
abuse: people uploading attachments which don't have much to do with
Cocoon (possibly just making
Berin Loritsch wrote:
Now, more good news:
On March 18, 2003 Avalon will be releasing a new set of Excalibur
components (as part of our continuing effort stated above). You will
have a new version of ECM and its dependencies. ECM now has a
big jar option which merges ECM's Avalon dependencies
Jeff Ramsdale wrote:
With recent updates of Cocoon 2.1-dev from CVS I haven't been able to get
the embedded Jetty to start up (Windows ME, j2sdk1.4.0). Turning echo on I
discovered 2 endless loops in cocoon.bat. Initially there were duplicate
gotPort and gotWebapp labels; I changed the duplicate
Andreas Hochsteger wrote:
Hi everybody!
I wonder if anybody ever looked at jelly:
http://jakarta.apache.org/commons/sandbox/jelly/
I found a hint to it in the Wyona/Lenya users mailing list.
It consists of an XML syntax and a tool wich interprets the XML documents and
it seems to be similar to
Niclas Hedhman wrote:
On Friday 14 March 2003 22:01, Nicola Ken Barozzi wrote:
Stefano Mazzocchi wrote, On 14/03/2003 14.49:
But I would like to be able to build cocoon without them and prevent
people with the ability to use them to solve their problems. Just like
Carsten wants to do with the
Bernhard Huber wrote:
hi,
Today one of the blocks is broken. I tried to get around
it as usual by un-commenting the line in local.blocks.properties
to no avail.
i made a CVS update, and had no problem running build webapp,
i even tried setting in local.block.properties all
entries from
On Friday, March 14, 2003, at 08:16 PM, David Crossley wrote:
However, this raises an issue. I presume that considering
Cocoon is now a top-level project, that all reference to
the Cocoon project should be removed from xml.apache.org
That will be tricky because the xml-site CVS module
contains
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17930.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
snip/
I would personally dislike this option because Jelly is rewriting a
programming language using a markup language syntax, which is, IMHO, a
very bad thing to do.
Well, disliking Jelly on the ServerSide I think Jelly-Swing on the
client-side
would be a quite interesting option.
Not using a
From: Matt Sergeant [mailto:[EMAIL PROTECTED]
On Friday, Mar 14, 2003, at 13:46 Europe/London, Steven Noels wrote:
while briefly checking the Wiki, I was confronted with some apparent
abuse: people uploading attachments which don't have much
to do with
Cocoon (possibly just making
Bernhard Huber wrote:
snip/
I would personally dislike this option because Jelly is rewriting a
programming language using a markup language syntax, which is, IMHO, a
very bad thing to do.
Well, disliking Jelly on the ServerSide I think Jelly-Swing on the
client-side
would be a quite
OK, it looks like Cocoon's core well on its way to reliably compiling
every day with Gump. Lately Avalon has gotten a reappreciation of the
importance of backwards compatibility. This is very very good.
Progress towards compiling cocoon's blocks is held up due to the fact
that the indicated
Christopher Oliver wrote:
Here's a summary of some of the recent issues with the Flow for discussion:
1) Storing the flow context object and continuation in environment
attributes:
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=104673257019781w=2
This seems easy to fix. But I personally
Good news, everyone!
For the first time in the history of Gump, we were able to run clean
last night.
Now we have a problem: the block builds expect a cocoon jar, but before
packaging we have to compile the blocks because they patch the role file
which is included into the package.
We have a
Sam Ruby wrote:
I've prep'ed cocoondev.org, and am nearly ready to try a full build.
Preping involved installing the necessary packages [1], tailoring some
of the paths in nagoya.xml to produce cocoondev.xml, and determining the
appropriate value for JAVA_HOME. I've done some limited testing,
Stefano Mazzocchi wrote, On 15/03/2003 17.31:
Good news, everyone!
For the first time in the history of Gump, we were able to run clean
last night.
Now we have a problem: the block builds expect a cocoon jar, but before
packaging we have to compile the blocks because they patch the role file
Duh, I've used command switches before in DOS! I guess I just didn't
recognize THOSE switches, (not have moved to NT or XP yet) so I was thrown
off. My bad! Fix works just fine.
I had another question I forgot to address in my original message. When
starting up Jetty with cocoon.bat a message is
Jeff Ramsdale wrote:
Duh, I've used command switches before in DOS! I guess I just didn't
recognize THOSE switches, (not have moved to NT or XP yet) so I was thrown
off. My bad! Fix works just fine.
Glad to hear that.
I had another question I forgot to address in my original message. When
Nicola Ken Barozzi wrote:
The better hacky solution: in the package target add a new 'blocks
build' target that just runs the xconftool:
!-- like the old package target --
target name=full-package depends=package, blocks/
...
!-- package the core (new) --
target name=package-core
On Saturday 15 March 2003 13:56, Stefano Mazzocchi wrote:
Andreas Hochsteger wrote:
Hi everybody!
I wonder if anybody ever looked at jelly:
http://jakarta.apache.org/commons/sandbox/jelly/
I found a hint to it in the Wyona/Lenya users mailing list.
It consists of an XML syntax and a
Congratulations.
Stefano, what is your current guestimate for the 2.1 arrival date?
Does it depends on the completion of the transfer to the new domain?
-=Ivelin=-
ivelin wrote:
Congratulations.
Stefano, what is your current guestimate for the 2.1 arrival date?
I honestly don't know.
Does it depends on the completion of the transfer to the new domain?
Yes, for one.
I'll follow up with a specific email on that.
Stefano.
I would like to see Cocoon released as soon as possible, but not sooner.
There are a few things to do before we can release and there are two realms:
1) internal - things inside the distribution
- flow
- finish polishing the object model
- provide a block-like method for
I usually just lurk...
- write a block-like modular system in the build for
- flow
- xsp
- actions (yet to be agreed upon)
- instrumentation (yet to be understood how)
Can't this wait until a 2.1 point release? It is a major change but doesn't
Steven Noels wrote:
Once this is accomplished, I'll look into two things: publishing the
results and moving the data to a location where everybody with the
ability to log onto cocoondev can do updates and builds of any and all
individual projects in between nightly runs. I fully expect people
On 15/3/03 21:54, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
- flow
- finish polishing the object model
Working on getting the IDL polished and improved... Sorry for being absent
this week, but had some issues and work and my dad's visiting me for the
first time in 4 years! (family
On 15/3/03 14:37, Bernhard Huber [EMAIL PROTECTED] wrote:
snip/
I would personally dislike this option because Jelly is rewriting a
programming language using a markup language syntax, which is, IMHO, a
very bad thing to do.
Well, disliking Jelly on the ServerSide I think Jelly-Swing
On 15/3/03 16:31, Steven Noels [EMAIL PROTECTED] wrote:
Before I do a full build, I would like to note a few things and ask a
few questions. Execution of a number of builds involve testing. Some
builds require Xvfb in order to work. I notice that there is an
instance of this process
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17671.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=17671.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Diana Shannon wrote:
David Crossley wrote:
snip/
However, this raises an issue. I presume that considering
Cocoon is now a top-level project, that all reference to
the Cocoon project should be removed from xml.apache.org
That will be tricky because the xml-site CVS module
contains
Bernhard Huber wrote:
David Crossley wrote:
Today one of the blocks is broken. I tried to get around
it as usual by un-commenting the line in local.blocks.properties
to no avail.
i made a CVS update, and had no problem running build webapp,
i even tried setting in local.block.properties
On Sat, Mar 15, 2003 at 06:09:44PM -0500, Tim Myers wrote:
I usually just lurk...
- write a block-like modular system in the build for
- flow
- xsp
- actions (yet to be agreed upon)
- instrumentation (yet to be understood how)
Can't this wait
Sam Ruby wrote:
Ultimately, we'll have to discuss what groups people are assigned to and
whether or not /etc/bashrc should be modified so that umask is set to
002 for everybody. What we need to ensure is that there is no problem
with permissions of files that people create.
umask isn't
On Friday, Mar 14, 2003, at 13:46 Europe/London, Steven Noels wrote:
while briefly checking the Wiki, I was confronted with some apparent
abuse: people uploading attachments which don't have much to do with
Cocoon (possibly just making benefit of the bandwidth we are
sponsoring), people
42 matches
Mail list logo
