Konstantin Piroumian wrote:
From: "Berin Loritsch" <[EMAIL PROTECTED]>
From what I can gather, Cocoon uses all of these components
from Avalon:
CLI
Collections
Concurrent
i18n
i18n stuff from Avalon was moved to Cocoon and now there are no references
to anything in Avalon i18n package.
AFAIK
From: "Berin Loritsch" <[EMAIL PROTECTED]>
>
> From what I can gather, Cocoon uses all of these components
> from Avalon:
>
> CLI
> Collections
> Concurrent
> i18n
i18n stuff from Avalon was moved to Cocoon and now there are no references
to anything in Avalon i18n package.
AFAIK, the original s
Over in Avalon land, we are wanting to coordinate the releases
of the Avalon technologies. We recently released LogKit 1.2
(available at http://avalon.apache.org/bindownload.cgi), and
very soon we will be releasing Framework 4.1.4.
Next on the agenda is the Excalibur stuff. We will focus
On Tuesday 28 January 2003 04:09, Stefano Mazzocchi wrote:
> Niclas Hedhman wrote:
> > Where do I send the 30GB worth of RAID hard drives?
>
> hardware is only 0.01% of the problem, Niclas. Politics and human
> dynamics account for the remaining 99.99% and you can't fix that sending
> us something
Niclas Hedhman wrote:
On Saturday 25 January 2003 21:42, Stefano Mazzocchi wrote:
Generally speaking, I agree. Especially if they could not be reproduced
from CVS. Moreover, all releases should be available and not only the
set we have now (see in this thread). But given limited
hardware, I
--On Saturday, January 25, 2003 2:42 PM +0100 Stefano Mazzocchi
<[EMAIL PROTECTED]> wrote:
those are not minor releases. Those are "releases", a release is
something that you might build your stuff upon. It's a contract.
Books, for example, use these contracts for years
On Saturday 25 January 2003 21:42, Stefano Mazzocchi wrote:
> > Generally speaking, I agree. Especially if they could not be reproduced
> > from CVS. Moreover, all releases should be available and not only the
> > set we have now (see in this thread). But given limited
> >
Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
Vadim Gritsenko wrote:
All:
Is it ok if I remove old Cocoon releases from the xml.apache.org?
To be precise:
cocoon-1.7.x
cocoon-1.8
cocoon-2.0
cocoon-2.0.1
cocoon-2.0.2
cocoon-2.0.3
-1, Brian asked for space conservatism, but that doesn&#
Steven Noels wrote:
Vadim Gritsenko wrote:
Generally speaking, I agree. Especially if they could not be
reproduced from CVS. Moreover, all releases should be available and
not only the set we have now (see in this thread). But given
limited hardware, I think it's ok to archive
Vadim Gritsenko wrote:
Generally speaking, I agree. Especially if they could not be reproduced
from CVS. Moreover, all releases should be available and not only the
set we have now (see in this thread). But given limited
hardware, I think it's ok to archive it on another machine
fficial distribution
> directory.
Stefano has a strong legacy about URL link deterioration, which, IHHO, is a
bigger menance to the web than anything else. Dying links are a real problem,
and if we as a community are advocating technologies and methods to preserve
all links, this matter shou
Stefano Mazzocchi wrote:
Vadim Gritsenko wrote:
All:
Is it ok if I remove old Cocoon releases from the xml.apache.org?
To be precise:
cocoon-1.7.x
cocoon-1.8
cocoon-2.0
cocoon-2.0.1
cocoon-2.0.2
cocoon-2.0.3
-1, Brian asked for space conservatism, but that doesn't mean to
destro
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
Steven Noels wrote:
Vadim Gritsenko wrote:
Suggestions? Steven? ;-)
tonight (gmt+1)
target: www.cocoondev.org/...?
www.cocoondev.org/dist/ ?
www.cocoondev.org/dist/cocoon/ ?
:)
history.cocoondev.org ?
I remain against removing any
Vadim Gritsenko wrote:
All:
Is it ok if I remove old Cocoon releases from the xml.apache.org?
To be precise:
cocoon-1.7.x
cocoon-1.8
cocoon-2.0
cocoon-2.0.1
cocoon-2.0.2
cocoon-2.0.3
-1, Brian asked for space conservatism, but that doesn't mean to destroy
the history of this project
Vadim Gritsenko wrote:
I meant GMT-5.
(blush)
Vadim
We know you are late ;-D
--
Steven Noelshttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog athttp://blogs.cocoondev.org/stevenn/
stevenn at outert
Vadim Gritsenko wrote:
Steven Noels wrote:
Vadim Gritsenko wrote:
What's the new URL? I'd like to reflect this in the README / HEADER.
history.cocoondev.org, please cross-check (I copied the .htaccess
files across, but they do obnoxious things - might as well drop them)
Cool! Files ar
Steven Noels wrote:
Vadim Gritsenko wrote:
What's the new URL? I'd like to reflect this in the README / HEADER.
history.cocoondev.org, please cross-check (I copied the .htaccess
files across, but they do obnoxious things - might as well drop them)
Cool! Files are there, the rest (like coc
Vadim Gritsenko wrote:
What's the new URL? I'd like to reflect this in the README / HEADER.
history.cocoondev.org, please cross-check (I copied the .htaccess files
across, but they do obnoxious things - might as well drop them)
--
Steven Noelshttp://outerthought.o
Steven Noels wrote:
Vadim Gritsenko wrote:
All:
Is it ok if I remove old Cocoon releases from the xml.apache.org?
To be precise:
cocoon-1.7.x
cocoon-1.8
cocoon-2.0
cocoon-2.0.1
cocoon-2.0.2
cocoon-2.0.3
IMO, I would not maintain copies of betas and RCs - so I won't copy
Vadim Gritsenko wrote:
All:
Is it ok if I remove old Cocoon releases from the xml.apache.org?
To be precise:
cocoon-1.7.x
cocoon-1.8
cocoon-2.0
cocoon-2.0.1
cocoon-2.0.2
cocoon-2.0.3
IMO, I would not maintain copies of betas and RCs - so I won't copy
http://xml.apache.org/cocoon/dis
Pier Fumagalli wrote:
I assume that aoindustries is where cocoondev is hosted right?
exactly
outerthought.net, where the previous wiki was hosted, was piggybacking
on our office connectivity (which is free & fast, but comes with no SLA)
I think we are doing the community a better service wit
"Steven Noels" <[EMAIL PROTECTED]> wrote:
> Pier Fumagalli wrote:
>
>> (In the light of recent experiences)... Got BACKUP? (DLT/DAT/Something?)
>
> http://www.aoindustries.com/servlet/com.aoindustries.website.Backup
> http://www.aoindustries.com/servlet/com.aoindustries.website.AOSecurity
> and
Pier Fumagalli wrote:
(In the light of recent experiences)... Got BACKUP? (DLT/DAT/Something?)
http://www.aoindustries.com/servlet/com.aoindustries.website.Backup
http://www.aoindustries.com/servlet/com.aoindustries.website.AOSecurity
and
http://www.aoindustries.com/servlet/com.aoindustries.we
"Sylvain Wallez" <[EMAIL PROTECTED]> wrote:
> Vadim Gritsenko wrote:
>
>> www.cocoondev.org/dist/ ?
>> www.cocoondev.org/dist/cocoon/ ?
>> :)
>
> history.cocoondev.org ?
(In the light of recent experiences)... Got BACKUP? (DLT/DAT/Something?)
Pier
> From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]]
> Sylvain Wallez wrote:
> > Vadim Gritsenko wrote:
> >> Steven Noels wrote:
> >>> Vadim Gritsenko wrote:
> Suggestions? Steven? ;-)
> >>>
> >>> tonight (gmt+1)
> >>>
> >>> target: www.cocoondev.org/...?
> >> www.cocoondev.org/dist/ ?
> >> www
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
Steven Noels wrote:
Vadim Gritsenko wrote:
Suggestions? Steven? ;-)
tonight (gmt+1)
target: www.cocoondev.org/...?
www.cocoondev.org/dist/ ?
www.cocoondev.org/dist/cocoon/ ?
:)
history.cocoondev.org ?
+1, Excellent choice!
Vadi
Vadim Gritsenko wrote:
Steven Noels wrote:
Vadim Gritsenko wrote:
Suggestions? Steven? ;-)
tonight (gmt+1)
target: www.cocoondev.org/...?
www.cocoondev.org/dist/ ?
www.cocoondev.org/dist/cocoon/ ?
:)
history.cocoondev.org ?
Sylvain
--
Sylvain Wallez
Steven Noels wrote:
Vadim Gritsenko wrote:
Suggestions? Steven? ;-)
tonight (gmt+1)
target: www.cocoondev.org/...?
www.cocoondev.org/dist/ ?
www.cocoondev.org/dist/cocoon/ ?
:)
Let me know when copy is ready (and URL) and I'll update download page
on xml.apache.org/cocoon/dist/
Vadim
Vadim Gritsenko wrote:
Suggestions? Steven? ;-)
tonight (gmt+1)
target: www.cocoondev.org/...?
--
Steven Noelshttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog athttp://blogs.cocoondev.org/stevenn/
Christian Haul wrote:
On 23.Jan.2003 -- 03:24 PM, Sylvain Wallez wrote:
Vadim Gritsenko wrote:
All:
Is it ok if I remove old Cocoon releases from the xml.apache.org?
To be precise:
cocoon-1.7.x
cocoon-1.8
cocoon-2.0
cocoon-2.0.1
cocoon-2.0.2
cocoon-2.0.3
Before removing
On Thu, 23 Jan 2003, Vadim Gritsenko wrote:
> Is it ok if I remove old Cocoon releases from the xml.apache.org?
> To be precise:
>
> cocoon-1.7.x
> cocoon-1.8
> cocoon-2.0
> cocoon-2.0.1
> cocoon-2.0.2
> cocoon-2.0.3
Hrm ... are some of these (2.0?) referenced by
On 23.Jan.2003 -- 03:24 PM, Sylvain Wallez wrote:
> Vadim Gritsenko wrote:
>
> >All:
> >
> >Is it ok if I remove old Cocoon releases from the xml.apache.org?
> >To be precise:
> >
> >cocoon-1.7.x
> >cocoon-1.8
> >cocoon-2.0
> >cocoon-2
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
All:
Is it ok if I remove old Cocoon releases from the xml.apache.org?
To be precise:
cocoon-1.7.x
cocoon-1.8
cocoon-2.0
cocoon-2.0.1
cocoon-2.0.2
cocoon-2.0.3
Before removing anything, we must find a place to archive these old
versions. We
Vadim Gritsenko wrote:
All:
Is it ok if I remove old Cocoon releases from the xml.apache.org?
To be precise:
cocoon-1.7.x
cocoon-1.8
cocoon-2.0
cocoon-2.0.1
cocoon-2.0.2
cocoon-2.0.3
Before removing anything, we must find a place to archive these old
versions. We cannot loose them
All:
Is it ok if I remove old Cocoon releases from the xml.apache.org?
To be precise:
cocoon-1.7.x
cocoon-1.8
cocoon-2.0
cocoon-2.0.1
cocoon-2.0.2
cocoon-2.0.3
Vadim
Original Message
Subject: need some more web space conservatism again
Date: Wed, 22 Jan 2003 18:02:49 -0800
leo leonid wrote:
Hi,
...
SearchGenerator: Maybe Vadim could give a hint in the docs how to use the
new element mentioned only in changes.xml and probably
incorrect in the DTD listed in search-generator.html in the docs. (What is
the parent element of field?).
Leo,
See SearchGenerator.
From: "leo leonid" <[EMAIL PROTECTED]>
>
> Hi,
> I'd like to send you some modest wishes concerning the upcoming 2.0.4
> release.
>
> Input Modules: I'm very happy with the Input Modules of 2.0.4-dev and like
> to see them in the release, too.
I've remind me to commit the new SystemPropertyModule
Ok,
from all the responses it seems that next week is not the best date
for 2.0.4. - As I won't be in the office to do the release
from 25th to the 29th of November, I would suggest to move the
date to the 4th of December.
This should give everyone more time to send patches ;) for
feature wishes
Hi,
I'd like to send you some modest wishes concerning the upcoming 2.0.4
release.
Input Modules: Im very happy with the Input Modules of 2.0.4-dev and like
to see them in the release, too.
i18n: Maybe Konstantin could apply the patch that you can set the locale
within the sitemap
(I know he h
n't
> stop them, since it so easy to download it and try
>
Hmm, I don't agree with you here, usually alpha releases should only
be used to sneak into something but not for producing a solution on top
of it.
But I guess in the case of Cocoon this might be a little bit
different - a
L PROTECTED]
> -Messaggio originale-
> Da: Carsten Ziegeler [mailto:cziegeler@;s-und-n.de]
> Inviato: giovedì 14 novembre 2002 13.57
> A: [EMAIL PROTECTED]
> Oggetto: RE: Releases
>
>
> Using an alpha version means acception a risk in using this software.
> It s
: Tuesday, November 12, 2002 6:44 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Releases
>
>
> What about the missed features that still are not working as:
>
> , cocoon protocol with request params and similars.
>
> Anyway I think will be fine to write a little doc about what is
El Lunes, 11 de Noviembre de 2002 23:58, Joerg Heinicke escribió:
> Antonio Gallardo Rivera wrote:
> > What about the missed features that still are not working as:
> >
> > , cocoon protocol with request params and similars.
> >
> > Anyway I think will be fine to write a little doc about what is no
Antonio Gallardo Rivera wrote:
What about the missed features that still are not working as:
, cocoon protocol with request params and similars.
Anyway I think will be fine to write a little doc about what is not working in
the alpha release. Many newbies will like to try this new features and
I would suggest the 21st of November for a release date.
> Any objections or problems?
>
> And if we are talking about releases what do you think of
> a 2.1alpha release on the same date? I know that some things
> are not working/finished but it's an alpha releae anyway.
>
> I
- Original Message -
From: "Carsten Ziegeler" <[EMAIL PROTECTED]>
To: "Cocoon-Dev" <[EMAIL PROTECTED]>
Sent: Monday, November 11, 2002 12:23 PM
Subject: Releases
> Hi Team,
>
> I had some busy weeks without much time for Cocoon - but I see
&g
Jar file ~lib/batik-all-1.5b2.jar seems to be built incorrectly. At least, even attempting just to view it by way of "jar tvf batik-all-1.5b2.jar" producess an exception. I think it was rebuilt using winzip and not jar: perhaps doesn't have a manifest file now.
A repaired version can be download a
od testing before the
release.
+1
And if we are talking about releases what do you think of
a 2.1alpha release on the same date? I know that some things
are not working/finished but it's an alpha releae anyway.
In Apache wording, an alpha version means something functional but
whose
or the job
mentioned above. So what about targeting the end of november ? This will
give everybody enough time to check in their last updates and have a
sufficient delay for code freeze and good testing before the release.
+1
And if we are talking about releases what do you think of
a 2.1alpha release o
Carsten Ziegeler wrote:
Hi Team,
I had some busy weeks without much time for Cocoon - but I see
some light, so there are some chances for a new release.
So did I, but in my case it was a full year of total darkness. Now looks
like I can finally breathe some fresh new air and devote time to C
ber ? This will
give everybody enough time to check in their last updates and have a
sufficient delay for code freeze and good testing before the release.
And if we are talking about releases what do you think of
a 2.1alpha release on the same date? I know that some things
are not working/finished b
Port JISP upgrade & fixes from 2.1 to 2.0.4
What do you think?
Vadim
I have the perception that we can make a 2.0.4 release without
problems, is this right?
If so, I would suggest the 21st of November for a release date.
Any objections or problems?
And if we are talking about releases wh
objections or problems?
And if we are talking about releases what do you think of
a 2.1alpha release on the same date? I know that some things
are not working/finished but it's an alpha releae anyway.
I think with these release we show that we are "back on track".
(And it will lead us to a r
Stefano Mazzocchi wrote:
>
> >> And if we are already talking about releases, what do we have to do
> >> for 2.1? It seems that many things are nearly finished, so we can
> >> start to think of a beta phase. I would propose the 15th of July for
> >>
Sylvain Wallez wrote:
+1 for 2.0.3 as soon as possible. I don't have issues with that.
> >> And if we are already talking about releases, what do we have to do
> >> for 2.1? It seems that many things are nearly finished, so we can
> >> start to think of a beta ph
Jens Lorenz wrote:
> From: "Carsten Ziegeler" <[EMAIL PROTECTED]>
>>The component uses the java.net.URL getPath() method which is not
>>available in 1.2.
>
>
> Which can be easily overcome by doing something like:
>
> java.net.URL url = ...;
> String path = url.getFile().substring(0,url.getFi
- Original Message -
From: "Carsten Ziegeler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 12, 2002 10:40 AM
Subject: RE: Planning the releases
>
> Nicola Ken Barozzi wrote:
> >
> > Carsten Ziegeler wrote:
> > >
Ivelin Ivanov wrote:
>
> Are Cocoon blocks in or out from 2.1 ?
>
Currently they are out as (AFAIK) noone has started working on it.
But if someone is able to make a concept *and* implement it by
the 15th of July (or the release date of the beta 1) they can
be in.
Personally, I think we should
gt; open issues, do them and release (sounds simple, doesn't it?)
>
> As I'm next week on vacation near Paris :) what do you think of
> the 1st of July as a release date for 2.0.3?
>
> And if we are already talking about releases, what do we have
> to do for 2.1? It seems tha
On Wednesday 12 June 2002 06:08 am, Davanum Srinivas wrote:
> July 1 for C2.0.3
> July 15 for C2.1 beta 1
+1 to both.
-pete
--
peter royal -> [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional command
Vadim Gritsenko wrote:
>
> > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
> >
> >
> > Vadim Gritsenko wrote:
> > >
> > >
> > > This is the most discussed issue on the user list, it must be fixed
> > > before release. Can we have now Excalibur which works with 1.3 *and*
> > > 1.4?
> > >
>
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
>
>
> Vadim Gritsenko wrote:
> >
> >
> > This is the most discussed issue on the user list, it must be fixed
> > before release. Can we have now Excalibur which works with 1.3 *and*
> > 1.4?
> >
> What is needed for it?
>
> The current excali
Vadim Gritsenko wrote:
>
>
> This is the most discussed issue on the user list, it must be fixed
> before release. Can we have now Excalibur which works with 1.3 *and*
> 1.4?
>
What is needed for it?
The current excalibur is compiled with jdk 1.4
in 1.2 compatible mode. For me this works on
f time :-/
> > What was the code snippet that was giving problems with 1.2?
> >
> >> As I'm next week on vacation near Paris :) what do you think of
> >> the 1st of July as a release date for 2.0.3?
> >
> >
> > +1
+1 provided issue above is
eek on vacation near Paris :) what do you think of
> > the 1st of July as a release date for 2.0.3?
>
> +1
>
> > And if we are already talking about releases, what do we have
> > to do for 2.1? It seems that many things are nearly finished, so
> > we can start
peu francais...but a french guide (who's also paying),
well, why not :)
> >> And if we are already talking about releases, what do we have to do
> >> for 2.1? It seems that many things are nearly finished, so we can
> >> start to think of a beta phase. I would propos
should collect the
> open issues, do them and release (sounds simple, doesn't it?)
>
> As I'm next week on vacation near Paris :) what do you think of
> the 1st of July as a release date for 2.0.3?
+1
> And if we are already talking about releases, what do we have
>
et, lack of time :-/
> What was the code snippet that was giving problems with 1.2?
>
>> As I'm next week on vacation near Paris :) what do you think of
>> the 1st of July as a release date for 2.0.3?
>
>
> +1
+1 also. Want a french guide for your vacation ? ;)
&
yet, lack of time :-/
> What was the code snippet that was giving problems with 1.2?
>
The component uses the java.net.URL getPath() method which is not
available in 1.2.
> > As I'm next week on vacation near Paris :) what do you think of
> > the 1st of July as a release date f
xt week on vacation near Paris :) what do you think of
> the 1st of July as a release date for 2.0.3?
+1
> And if we are already talking about releases, what do we have
> to do for 2.1? It seems that many things are nearly finished, so
> we can start to think of a beta phase. I would
;t it?)
As I'm next week on vacation near Paris :) what do you think of
the 1st of July as a release date for 2.0.3?
And if we are already talking about releases, what do we have
to do for 2.1? It seems that many things are nearly finished, so
we can start to think of a beta phase. I would
pro
Carsten Ziegeler wrote:
> wow - we did a beta 1 release and all of us survived...
Nice job!
> - Remove the X/CIncludeSAXConnector and use the corresponding
> transformers instead.
Sigh. I spent many hours trying to get includes working in my pages,
fixing them many times. If you are going
Giacomo Pati a écrit :
>
>
> I have still the proposal and samples from Michael Homeijer concerning C2 act as
> a SOAP client and server which is something that is really interesting to me. As
> it is nothing that would change interfaces I'd like to integrate it into 2.0.
> Any comments about
>>
> get back after my holiday :-)).
Lucky you ;) have nice holidays.
<<
Thanks! Just don't give Carsten too much to do - so that he can get on with
some proper work :-))
Matthew
--
Open Source Group sunShine - Lighting up e:Business
===
Quoting Matthew Langham <[EMAIL PROTECTED]>:
> >>
> I have still the proposal and samples from Michael Homeijer concerning
> C2
> act as
> a SOAP client and server which is something that is really interesting
> to
> me. As
> it is nothing that would change interfaces I'd like to integrate it int
ag, 8. Juni 2001 10:03
> An: [EMAIL PROTECTED]
> Betreff: [C2]: Preparing the next releases
>
>
> Hi,
>
> wow - we did a beta 1 release and all of us survived...
> I promise that the next release of C2 will be with less
> problems.
>
> To keep on this great project,
+1 from me for integrating SOAP code+samples into 2.0 itself.
Thanks,
dims
--- Matthew Langham <[EMAIL PROTECTED]> wrote:
> >>
> I have still the proposal and samples from Michael Homeijer concerning C2
> act as
> a SOAP client and server which is something that is really interesting to
> me. As
>>
I have still the proposal and samples from Michael Homeijer concerning C2
act as
a SOAP client and server which is something that is really interesting to
me. As
it is nothing that would change interfaces I'd like to integrate it into
2.0.
Any comments about it?
<<
+1 for that.
We would like to
> -Ursprüngliche Nachricht-
> Von: Giacomo Pati [mailto:[EMAIL PROTECTED]]
> Gesendet: Freitag, 8. Juni 2001 12:13
> An: [EMAIL PROTECTED]
> Betreff: Re: [C2]: Preparing the next releases
>
>
> Quoting Carsten Ziegeler <[EMAIL PROTECTED]>:
>
> > Hi
Quoting Carsten Ziegeler <[EMAIL PROTECTED]>:
> Hi,
>
> wow - we did a beta 1 release and all of us survived...
> I promise that the next release of C2 will be with less
> problems.
Propabbly we all learn by doing :)
> To keep on this great project, I think we should make
> a simple plan for
Hi,
wow - we did a beta 1 release and all of us survived...
I promise that the next release of C2 will be with less
problems.
To keep on this great project, I think we should make
a simple plan for the next beta and the release:
We should collect the things to be done for the release and
try t
81 matches
Mail list logo
