You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by J Aaron Farr <ja...@yahoo.com> on 2003/05/22 18:29:04 UTC
[Fortress] [PATCH] README.txt ( Was: Re: [Announce] Excalibur ...)
--- Berin Loritsch <bl...@apache.org> wrote:
> J Aaron Farr wrote:
> >
> > Also, the README.txt is rather weak. Mind if I send a more thorough
> README?
>
> We will accept any contributions you have. Bear in mind that these
> aren't "blocker" issues (like the bugs that were found) and it is
> more than likely that the updates will make it into the next release
> of Fortress.
>
Understandable.
Here's a patch for the current Fortress README.txt. I would include runtime /
build requirements, but I wasn't sure what they were.
The examples.zip probably needs it's own README.txt too.
jaaron
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
Re: attachment configuration
Posted by Leo Simons <le...@apache.org>.
If I hear nothing in the next few days I'll send a request out :D
- Leo
Leo Simons wrote:
> I believe it is easy enough to disable the mimetype
> filtering on attachments. Do we want that? If so, just for the dev@ list
> (my opinion) or for the users@ list as well?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: attachment configuration
Posted by Berin Loritsch <bl...@apache.org>.
Leo Simons wrote:
> It seems like some types of attachments get stripped off. I believe only
> a few types of files (I think .zip and .txt) make it through, and only
> messages of up to 100kb make it through.
>
> there was some talks about this on infrastructure recently; basically
> qmail is fully configurable and we can ask apmail to configure this
> however we want to. I believe it is easy enough to disable the mimetype
> filtering on attachments. Do we want that? If so, just for the dev@ list
> (my opinion) or for the users@ list as well?
As long as there is no executale mime-type (i.e. *.exe, etc.) I would
be for it. The reason is that .patch, .diff, .xml, .xconf, etc. are
all semi-standards (well, .xml is a standard) and folks do have
thick thumbs at times (myself included).
I just don't want viruses or anything like that.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
attachment configuration (was: Re: [Fortress] [PATCH] README.txt
( Was: Re: [Announce] Excalibur ...))
Posted by Leo Simons <le...@apache.org>.
It seems like some types of attachments get stripped off. I believe only
a few types of files (I think .zip and .txt) make it through, and only
messages of up to 100kb make it through.
there was some talks about this on infrastructure recently; basically
qmail is fully configurable and we can ask apmail to configure this
however we want to. I believe it is easy enough to disable the mimetype
filtering on attachments. Do we want that? If so, just for the dev@ list
(my opinion) or for the users@ list as well?
cheers,
- Leo
> Berin Loritsch <bl...@apache.org> wrote:
>
>>Did you send it, or did it get stripped in transit?
>>
>>Just past the diff into the body of the email.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [Fortress] [PATCH] README.txt ( Was: Re: [Announce] Excalibur ...)
Posted by J Aaron Farr <ja...@yahoo.com>.
--- Berin Loritsch <bl...@apache.org> wrote:
>
> Did you send it, or did it get stripped in transit?
>
> Just past the diff into the body of the email.
>
Hmmm. not sure. sorry about that:
--- README.orig 2003-05-22 08:59:06.000000000 -0400
+++ README.txt 2003-05-22 12:28:18.000000000 -0400
@@ -1,6 +1,37 @@
Avalon Excalibur Fortress
-------------------------
-Fortress is a replacement for Excalibur's component package. It
-makes it easier to build your own scalable containers. It does
-separate the Container logic from the component accessor logic.
+What is it?
+-----------
+
+Fortress is a replacement for Excalibur's component package. It makes
+it easier to build your own scalable containers. It separates the
+Container logic from the component accessor logic.
+
+Where is it?
+------------
+
+http://avalon.apache.org/excalibur/fortress/
+
+Included Files
+--------------
+
+LICENSE.txt Apache Software License 1.1 that covers Fortress
+README.txt This file. A general overview.
+docs/ API documentation (javadocs)
+examples.zip Contains the Fortress examples distribution
+src.zip Contains the Fortress source code
+excalibur-fortress-*.jar Prebuilt Fortress binary distribution jars
+ 1.0.jar contains just the Fortress classes
+ (i.e.- the classes in src.zip)\
+ complete-1.0.jar Fortress classes + excalibur dependencies:
+ apache-altrmi
+ excalibur-i18n
+ excalibur-instrument
+ excalibur-event
+ excalibur-logger
+ excalibur-resolver
+ excalibur-lifecycle
+ tools-1.0.jar Fortress tools package
+
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [Fortress] [PATCH] README.txt ( Was: Re: [Announce] Excalibur
...)
Posted by Berin Loritsch <bl...@apache.org>.
J Aaron Farr wrote:
> --- Berin Loritsch <bl...@apache.org> wrote:
>
>>J Aaron Farr wrote:
>>
>>>Also, the README.txt is rather weak. Mind if I send a more thorough
>>
>>README?
>>
>>We will accept any contributions you have. Bear in mind that these
>>aren't "blocker" issues (like the bugs that were found) and it is
>>more than likely that the updates will make it into the next release
>>of Fortress.
>>
>
>
> Understandable.
>
> Here's a patch for the current Fortress README.txt. I would include runtime /
> build requirements, but I wasn't sure what they were.
>
> The examples.zip probably needs it's own README.txt too.
Did you send it, or did it get stripped in transit?
Just past the diff into the body of the email.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org