You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Berin Loritsch <bl...@apache.org> on 2001/06/14 18:16:40 UTC

Automagic Announcement Generation

I added the automagic announcement generation from the Avalon
project.  This does require a little care and feeding, though.

One thing that was forgotten during the Beta 1 release of
Cocoon was to adjust the Change logs so that the last release
was permanently marked as:

<release version="2.0b1" date="June 3, 2001">

This is something that has been forgotten to be done between
every version number for the change log.  As a result, it is
_very_ difficult to figure out what changes and updates happened
when.

I propose that we do not use the automatic filtering on the
change.xml file, and we hand code the versions for the releases
in the file.  This will force the average developer to realize
(hopefully) that my change is in version 2.0b1-dev (will be
2.0b2).

Please, be careful with the change log.  It is a good tool if
maintained correctly.

Also, is our TODO list up to date?

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

Re: Automagic Announcement Generation

Posted by giacomo <gi...@apache.org>.
On Thu, 14 Jun 2001, Berin Loritsch wrote:

> I added the automagic announcement generation from the Avalon
> project.  This does require a little care and feeding, though.
>
> One thing that was forgotten during the Beta 1 release of
> Cocoon was to adjust the Change logs so that the last release
> was permanently marked as:
>
> <release version="2.0b1" date="June 3, 2001">
>
> This is something that has been forgotten to be done between
> every version number for the change log.  As a result, it is
> _very_ difficult to figure out what changes and updates happened
> when.
>
> I propose that we do not use the automatic filtering on the
> change.xml file, and we hand code the versions for the releases
> in the file.  This will force the average developer to realize
> (hopefully) that my change is in version 2.0b1-dev (will be
> 2.0b2).
>
> Please, be careful with the change log.  It is a good tool if
> maintained correctly.
>
> Also, is our TODO list up to date?

Hmm.. haven't look into it quite a while.

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

Re: sub sitemap and components (was: RE: TODO)

Posted by Berin Loritsch <bl...@apache.org>.
Make sure the Component also implements one of the lifestyle
interfaces:

SingleThreaded (instantiated by factory method)
ThreadSafe (one instance shared)
Poolable (multiple instances recycled after use)

The ComponentManager in Excalibur makes the safest assumption
it can in the absence of these: it assumes the Component is
SingleThreaded.

The implications of choosing the lifestyle of choice are:

SingleThreaded:  Creation is delayed until you actually request
                 it.  There is never a Component in reserve.

ThreadSafe: It is created on initialization, and the one instance
            is shared between all requesters.

Poolable: It is created on initialization with multiple instances.
          as it is requested, unused instances are given to the
          client.

Torsten Curdt wrote:
> 
> > > > Also, is our TODO list up to date?
> > >
> > > Well, could someone please help and have
> > > a look at the sub sitemap error?
> > > (I need this to work real badly)
> > >
> > > Or proove I'm wrong...
> >
> > It's fixed.  The 2.0 branch got broken during the
> > code merge--and 2.1 was never updated properly.
> > It should work for you now.
> 
> It does!! Berin, I officially want to state that I love you ;))
> Well, at least a thousand thanks for the fast fix!!
> This night I can sleep well again...
> 
> One more question regarding the Components load on startup:
> My component now implements Component, Configurable, Composable
> and Contextualizable. I see the role in the logs but no
> instance is created - well, at least
> 
>  void configure(Configuration conf)
> 
> is never called. Are the components only initialized and
> not configured on startup? Or what have I missed?
> 
> Thanks!!
> --
> Torsten
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

sub sitemap and components (was: RE: TODO)

Posted by Torsten Curdt <tc...@dff.st>.
> > > Also, is our TODO list up to date?
> > 
> > Well, could someone please help and have
> > a look at the sub sitemap error?
> > (I need this to work real badly)
> > 
> > Or proove I'm wrong...
> 
> It's fixed.  The 2.0 branch got broken during the
> code merge--and 2.1 was never updated properly.
> It should work for you now.

It does!! Berin, I officially want to state that I love you ;))
Well, at least a thousand thanks for the fast fix!!
This night I can sleep well again...

One more question regarding the Components load on startup:
My component now implements Component, Configurable, Composable
and Contextualizable. I see the role in the logs but no
instance is created - well, at least

 void configure(Configuration conf)

is never called. Are the components only initialized and
not configured on startup? Or what have I missed?

Thanks!!
--
Torsten

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

Re: TODO (was RE: Automagic Announcement Generation)

Posted by Berin Loritsch <bl...@apache.org>.
Torsten Curdt wrote:
> 
> > Also, is our TODO list up to date?
> 
> Well, could someone please help and have
> a look at the sub sitemap error?
> (I need this to work real badly)
> 
> Or proove I'm wrong...

It's fixed.  The 2.0 branch got broken during the
code merge--and 2.1 was never updated properly.
It should work for you now.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

Re: TODO (was RE: Automagic Announcement Generation)

Posted by giacomo <gi...@apache.org>.
On Thu, 14 Jun 2001, Torsten Curdt wrote:

> > Also, is our TODO list up to date?
>
> Well, could someone please help and have
> a look at the sub sitemap error?
> (I need this to work real badly)
>
> Or proove I'm wrong...
>
> But since Giacomo experienced the
> same behavior I feel quite confident
> it is not my fault (this time ;)

It seems to be fixed now (my clean version from about a half an hour ago
work well with sub sitemaps.

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

TODO (was RE: Automagic Announcement Generation)

Posted by Torsten Curdt <tc...@dff.st>.
> Also, is our TODO list up to date?

Well, could someone please help and have
a look at the sub sitemap error?
(I need this to work real badly)

Or proove I'm wrong...

But since Giacomo experienced the
same behavior I feel quite confident
it is not my fault (this time ;)
--
Torsten


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org