You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Berin Loritsch <bl...@apache.org> on 2002/09/25 15:49:05 UTC
Preparing for Fortress 1.0 Release
We have the prereq of making official releases of each of these peices:
> Concurrent
> Collections
> Container (for the legacy compatibility)
> Event
> I18n (for Meta)
> Meta (for the metadata stuff)
> SourceResolver
> AltRMI (for Instrumentation)
> Instrument
> Instrument-Manager
> Util (for System--haven't moved that over yet)
> Logger
> ThreadContext
What we need are some docs for these things. I don't have the time to
take care of all of them, so I am seeking some help. The Docs need to
represent the WHAT, WHEN, WHY, HOW questions, as well as any notes about
future direction. Here are some notes I would like to incorporate:
Concurrent -- Point people to Doug Lea's libraries. Do we want to
officially deprecate this?
Collections -- It will be replaced in favor of Jakarta-Commons
Colletions when they make a new release.
Container -- Usage notes on Legacy, ClassLoader, Lookup, Lifecycle
SourceResolver -- Usage notes, and notes on extending it for your
own protocols.
Instrument -- Notes on how to make your classes instrumentable. If the
interfaces are stable, we need to look at making this a
stable release. (Test cases are critical!!!!)
Instrument-Manager -- Notes on how to incorporate the InstrumentManager
into your projects, as well as how to configure
it. If there are things that will change here,
please indicate that.
Logger -- Notes on how to configure the various LoggerManagers.
ThreadContext -- Something. I don't know a whole bunch about this,
other than it is supported in the ThreadPool.
I will take responsibility for the Event package and moving the
SystemUtil code into Event. I will also make the Meta package an
*Optional* dependency for the time being. That means for the purpose
of a Fortress 1.0 release, we can remove the requirement for Meta
and I18n so we can document them later enabled classes.
Leif, Can you take responsibility for the Instrument/Instrument-Manager
projects to get the docs and some testcases up?
Peter D., Can you take responsibility for ThreadContext (I think that is
your baby)?
Carston or Giacomo, Can you take responsibility for Logger and Source
Resolver?
Nikola, can you take Collections/Concurrent? For these, we don't have
to instruct how to use the classes, just an overview of what is in there
and what problem the type of class solves (i.e. Buffer, etc.).
That leaves a volunteer needed for Container. Since I added most of the
new things, I can take it. I will be happy to let someone else take
care of it though. ;P
If we team up and split the labor like that, I think we can get Fortress
1.0 out the door. Who has experience with Ant tasks? I want something
that can convert an ECM Roles file to a Fortress compatible one. I will
add a utility class that will help in the transition--that way we can
make the transition as seamless as possible.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Preparing for Fortress 1.0 Release
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Berin Loritsch wrote:
> We have the prereq of making official releases of each of these peices:
>
>> AltRMI (for Instrumentation)
>
AltRMI is actually only required by the Altrmi connector of the
Instrument Manager. If it is
not configured in the instrument configuration file, it is not used.
Currently, it is the only
available connector if you want to access the IM from a client however.
>> Instrument
>> Instrument-Manager
>
>
> Instrument -- Notes on how to make your classes instrumentable. If the
> interfaces are stable, we need to look at making this a
> stable release. (Test cases are critical!!!!)
Ok, I'll push to try and get these done. Been burried with work the
past couple
months. Still a few hours a day I am wasting on sleep that I can use to
get this
done. :-)
> Instrument-Manager -- Notes on how to incorporate the InstrumentManager
> into your projects, as well as how to configure
> it. If there are things that will change here,
> please indicate that.
>
> Leif, Can you take responsibility for the Instrument/Instrument-Manager
> projects to get the docs and some testcases up?
Wil do. The client still needs some work though, but it does not need to be
at the same level of stability as it is an external application.
Cheers,
Leif
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Preparing for Fortress 1.0 Release
Posted by Berin Loritsch <bl...@apache.org>.
Fortress does not require I18n, so it is a *little* less work.
>> I18n (for Meta)
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Preparing for Fortress 1.0 Release
Posted by Berin Loritsch <bl...@apache.org>.
Marcus Crafter wrote:
> Hi Berin,
>
> On Wed, Sep 25, 2002 at 09:49:05AM -0400, Berin Loritsch wrote:
>
>>That leaves a volunteer needed for Container. Since I added most of the
>>new things, I can take it. I will be happy to let someone else take
>>care of it though. ;P
>
>
> I can take care of Container if you like.
Excellent! Take a look at how I set up the docs for Event (even the
commented out entries in menu.xml). It will give an idea of what should
be good enough.
>>If we team up and split the labor like that, I think we can get Fortress
>>1.0 out the door. Who has experience with Ant tasks? I want something
>>that can convert an ECM Roles file to a Fortress compatible one. I will
>>add a utility class that will help in the transition--that way we can
>>make the transition as seamless as possible.
>
>
> This shouldn't be too hard to do. I'll take a crack at it.
>
> Do you have any dates for all this in mind BTW ?
As soon as its done.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Preparing for Fortress 1.0 Release
Posted by Marcus Crafter <cr...@fztig938.bank.dresdner.net>.
Hi Berin,
On Wed, Sep 25, 2002 at 09:49:05AM -0400, Berin Loritsch wrote:
>
> That leaves a volunteer needed for Container. Since I added most of the
> new things, I can take it. I will be happy to let someone else take
> care of it though. ;P
I can take care of Container if you like.
> If we team up and split the labor like that, I think we can get Fortress
> 1.0 out the door. Who has experience with Ant tasks? I want something
> that can convert an ECM Roles file to a Fortress compatible one. I will
> add a utility class that will help in the transition--that way we can
> make the transition as seamless as possible.
This shouldn't be too hard to do. I'll take a crack at it.
Do you have any dates for all this in mind BTW ?
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Preparing for Fortress 1.0 Release
Posted by Giacomo Pati <gi...@apache.org>.
On Wed, 25 Sep 2002, Berin Loritsch wrote:
> We have the prereq of making official releases of each of these peices:
>
> > Concurrent
> > Collections
> > Container (for the legacy compatibility)
> > Event
> > I18n (for Meta)
> > Meta (for the metadata stuff)
> > SourceResolver
> > AltRMI (for Instrumentation)
> > Instrument
> > Instrument-Manager
> > Util (for System--haven't moved that over yet)
> > Logger
> > ThreadContext
>
> What we need are some docs for these things. I don't have the time to
> take care of all of them, so I am seeking some help. The Docs need to
> represent the WHAT, WHEN, WHY, HOW questions, as well as any notes about
> future direction. Here are some notes I would like to incorporate:
>
> Concurrent -- Point people to Doug Lea's libraries. Do we want to
> officially deprecate this?
>
> Collections -- It will be replaced in favor of Jakarta-Commons
> Colletions when they make a new release.
>
> Container -- Usage notes on Legacy, ClassLoader, Lookup, Lifecycle
>
> SourceResolver -- Usage notes, and notes on extending it for your
> own protocols.
>
> Instrument -- Notes on how to make your classes instrumentable. If the
> interfaces are stable, we need to look at making this a
> stable release. (Test cases are critical!!!!)
>
> Instrument-Manager -- Notes on how to incorporate the InstrumentManager
> into your projects, as well as how to configure
> it. If there are things that will change here,
> please indicate that.
>
> Logger -- Notes on how to configure the various LoggerManagers.
>
> ThreadContext -- Something. I don't know a whole bunch about this,
> other than it is supported in the ThreadPool.
>
> I will take responsibility for the Event package and moving the
> SystemUtil code into Event. I will also make the Meta package an
> *Optional* dependency for the time being. That means for the purpose
> of a Fortress 1.0 release, we can remove the requirement for Meta
> and I18n so we can document them later enabled classes.
>
> Leif, Can you take responsibility for the Instrument/Instrument-Manager
> projects to get the docs and some testcases up?
>
> Peter D., Can you take responsibility for ThreadContext (I think that is
> your baby)?
>
> Carston or Giacomo, Can you take responsibility for Logger and Source
> Resolver?
I can have a look at Logger (I know: look at Event to get a clue how to
do it ;)
Giacomo
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>