On Sun, Mar 23, 2003 at 06:27:03PM +1100, David Crossley wrote:
Jeff Turner wrote:
Stephan Michels wrote:
...
No, I mean not ignoring for the validation, I mean ignoring for the
documentation generation process.
Yes, should be possible by defining 'project.sitemap-dir' to point to
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=18131.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
]
+---+
[echo] Apache Cocoon 20030323 [1999-2003]
[echo]
+---+
[echo] Building with Apache Ant version 1.6alpha compiled
]
+---+
[echo] Apache Cocoon 20030323 [1999-2003]
[echo]
+---+
[echo] Building with Apache Ant version 1.6alpha compiled on March 23
]
+---+
[echo] Apache Cocoon 20030323 [1999-2003]
[echo]
+---+
[echo] Building with Apache Ant version 1.6alpha compiled on March 23
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-03-23/gump.html
Buildfile: build.xml
platform_props:
compile:
[mkdir] Created dir:
]
+---+
[echo] Apache Cocoon 20030323 [1999-2003]
[echo]
+---+
[echo] Building with Apache Ant version 1.6alpha compiled on March 23
]
+---+
[echo] Apache Cocoon 20030323 [1999-2003]
[echo]
+---+
[echo] Building with Apache Ant version 1.6alpha compiled on March
]
+---+
[echo] Apache Cocoon 20030323 [1999-2003]
[echo]
+---+
[echo] Building with Apache Ant version 1.6alpha compiled on March
On Sunday, March 23, 2003, at 02:59 AM, David Crossley wrote:
snip /
Stefano Mazzocchi wrote:
Diana Shannon wrote:
For example, current forrest build capability with cocoon's cvs
is only possible with Forrest CVS, not the last Forrest release.
This violates your building on sand philosophy.
I
Diana Shannon wrote:
All right. Since there is circular dependency between cocoon and
forrest, I would suggest we release cocoon 2.1 first, allow forrest to
release a new version based on 2.1 and at that point forrestize our
docs.
how does that sound?
But this circular dependency will always
Diana Shannon wrote:
snip/
I'm not saying it isn't working. I'm saying the **only** reason it works
now is because we are using a cvs-based version of an outside project,
not a released version. Stefano recently stated in:
I propose Andrew Savory as Cocoon committer. He has been
involved with Cocoon since mid-2000 and more intensely during
the past year. Browsing the email archives i see plenty of
discussion, bug reports, testing, and suggestions. This indicates
his commitment. Andrew is also keen on documentation
As I think most of the people here knows, Forrest is a Cocoon spin-off
project that focuses on static-snapshots of publishing-intensive web
sites with complex needs.
Cocoon now self-generates its own static website, but given the amount
of time/effort/energy that has gone into Forrest since it
Jeremy Quinn wrote:
snip/
OK
This still fails:
http://localhost:/samples/catalog/sdocbook-demo
org.apache.cocoon.ProcessingException: Failed to execute pipeline.:
java.io.FileNotFoundException:
/Users/jermq/Checkouts/Secure/cocoon-2.1/build/webapp/samples/catalog/
excalibur-event also depends on it, so I think this should be part of the
core ?
Volker
stefano 2003/03/23 02:41:01
Added: src/blocks/web3/lib util.concurrent-1.3.1.jar
Log:
moving Doug Lea's concurrent utility classes to the block that depends on
them
Revision Changes
I propose Geoff Howard as Cocoon committer. He has been
involved with Cocoon for the past year, providing lots of
useful discussion and bug report/fixing. He has submitted
many useful patches, for example with the file upload.
He gives tremendous assistance on cocoon-users, further
demonstrating
In the beginning, there was only one cocoon distribution, packaged with
two different packagers (zip for windows and tar.gz for unix and friends).
Then cocoon became very complex and we decided to create a binary
distribution to make things easier. Things were indeed easier for new
users to
On Sunday, March 23, 2003, at 08:55 AM, David Crossley wrote:
I propose Geoff Howard as Cocoon committer.
He also contributed an excellent tutorial on custom generators.
+1
Diana
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
On Sunday, March 23, 2003, at 08:38 AM, Stefano Mazzocchi wrote:
1) cocoon moves to forrest for its documentation production
+1
2) if so, cocoon does it before releasing 2.1
+1
3) if so, I'd like a 'fast-yet-potentially-disruptive' move rather
than a
On Sonntag, März 23, 2003, at 12:00 Uhr, Christopher Oliver wrote:
I modified this sample to use XMLForm to implement the Edit Account
page of this sample. To see this, first sign in and then click on My
Account.
XMLForm is very nice to use in flow scripts, because it automatically
populates
On Sonntag, März 23, 2003, at 12:00 Uhr, Christopher Oliver wrote:
I modified this sample to use XMLForm to implement the Edit Account
page of this sample. To see this, first sign in and then click on My
Account.
XMLForm is very nice to use in flow scripts, because it automatically
populates
]
+---+
[echo] Apache Cocoon 20030323 [1999-2003]
[echo]
+---+
[echo] Building with Apache Ant version
Stefano Mazzocchi wrote, On 23/03/2003 15.25:
...
So, in light of the good old triad
./configure; make; make install
I propose to ship Cocoon 2.1 *AS IS*, sort of a cleaned-up version of
our current CVS and improve a little the 'INSTALL.txt' doc that will
suggest you to do
$ ./build.sh
$
Stefano Mazzocchi wrote:
So, what do we do?
Good question.
a) Fix GUMP so that it can take stuff from a branch.
b) Include a Cocoon owned stub.
c) Do nothing.
In either case, check
http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAvalonization
before it goes stale.
Send nag mails to Jeremias who
Stefano Mazzocchi wrote, On 23/03/2003 14.38:
...
This said, here are the actions you should vote:
WARNING: being a Forrest dev, I'm baised ;-)
1) cocoon moves to forrest for its documentation production
Yeah! :-D
+1
2) if so, cocoon does it before releasing 2.1
Also +1
3) if so, I'd like a
David Crossley wrote:
I propose Andrew Savory as Cocoon committer.
Here is my obvious +1
Knowing Andrew (and David Casal) IRL I know how much they and their
company are committed with Cocoon, so this is my big +1, and the warmest
welcome aboard!
--
Gianugo Rabellino
Pro-netics s.r.l.
David Crossley wrote:
I propose Geoff Howard as Cocoon committer.
Here is my +1
+1.
Ciao,
--
Gianugo Rabellino
Pro-netics s.r.l.
http://www.pro-netics.com
Well I am just a user... But you hit the nail right on the head there. I had
cocoon up and running within minutes the first time I found it, but was
extremely frustrated for months afterward, because I could load the samples
page... and SEE what it could do, but not be able to implement for
On Sunday, March 23, 2003, at 08:22 AM, David Crossley wrote:
I propose Andrew Savory as Cocoon committer. He has been
involved with Cocoon since mid-2000 and more intensely during
the past year.
+1. I was lucky to meet him in person and can confirm his first-rate
ideas and experience. He's
snip/
1) cocoon moves to forrest for its documentation production
+1
2) if so, cocoon does it before releasing 2.1
+1
3) if so, I'd like a 'fast-yet-potentially-disruptive' move rather
than a 'slow-yet-carefully-planned-not-to-disrupt-anything' one.
+1
i think forrest has a lot of pros
from me +1
from me +1
On Mon, Mar 24, 2003 at 12:22:36AM +1100, David Crossley wrote:
I propose Andrew Savory as Cocoon committer.
+1, welcome
--Jeff
--David Crossley
On Mon, Mar 24, 2003 at 12:55:19AM +1100, David Crossley wrote:
I propose Geoff Howard as Cocoon committer. He has been
involved with Cocoon for the past year, providing lots of
useful discussion and bug report/fixing. He has submitted
many useful patches, for example with the file upload.
He
On Monday 24 March 2003 02:08, Nicola Ken Barozzi wrote:
Stefano Mazzocchi wrote, On 23/03/2003 15.25:
What do you think?
+1 for the source distro.
I agree, except...
As for the binary distro, we simply never did one really. What I'd like
to see is
cocoon-full.war
no need, IMHO.
Stefano Mazzocchi wrote:
snip/
This said, here are the actions you should vote:
1) cocoon moves to forrest for its documentation production
+1
2) if so, cocoon does it before releasing 2.1
+1
3) if so, I'd like a 'fast-yet-potentially-disruptive' move rather
than a
In order to get one little step closer to the 'new' document
infrastructure, many of us seek clarity whether we should move docs to a
separate CVS module or not. The benefits and downfalls are largely
known, so let's vote on this and get this issue cleared.
My own personal bias: don't forget
Le Dimanche, 23 mars 2003, à 14:20 Europe/Zurich, David Crossley a
écrit :
If the mantra only use released version of a product was
applied by Forrest then we would not be doing very well.
We now need, and probably always will need, a recent Cocoon head.
Perhaps we can relax this rule for
Le Dimanche, 23 mars 2003, à 14:55 Europe/Zurich, David Crossley a
écrit :
I propose Geoff Howard as Cocoon committer.
+1 here.
-Bertrand
Le Dimanche, 23 mars 2003, à 14:22 Europe/Zurich, David Crossley a
écrit :
I propose Andrew Savory as Cocoon committer
here's my
+1
-Bertrand
David Crossley wrote, On 23/03/2003 14.55:
I propose Geoff Howard as Cocoon committer.
+1
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
David Crossley wrote, On 23/03/2003 14.22:
I propose Andrew Savory as Cocoon committer.
+1
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
Le Dimanche, 23 mars 2003, à 15:25 Europe/Zurich, Stefano Mazzocchi a
écrit :
...
Before you jump up and down and scream no, no, binaries are easier
for our users, get off your
life-without-a-compiler-windows-inflicted-mindset and think that every
JDK comes with a compiler.
Technically, I'm
Le Dimanche, 23 mars 2003, à 14:38 Europe/Zurich, Stefano Mazzocchi a
écrit :
...This said, here are the actions you should vote:
1) cocoon moves to forrest for its documentation production
+1
2) if so, cocoon does it before releasing 2.1
+1
3) if so, I'd like a
On Sun, 23 Mar 2003, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
All right. I think I found out the problem: it seems that the gump
descriptor for jakarta-slide is incorrect and doesn't expose all the
jars that we need and we depend on.
Quite possible. Slide used to be unbuildable by Gump for
47 matches
Mail list logo
