On Wednesday 07 January 2004 02:56, Timothy Bennett wrote:
> Berin Loritsch wrote:
> > Tone it down big guy. I am juggling three different thought processes
> > currently, and I am not in a position to give a more clear answer just
> > yet. Maybe later, but right now I am juggling too many things
mcconnell2004/01/06 15:22:29
Added:
merlin/composition/impl/src/test/org/apache/avalon/composition/model/test
Tag: Ver_3_4 PlaygroundTestCase.java
merlin/composition/impl/src/test/org/apache/avalon/playground
Tag: Ver_3_4
mcconnell2004/01/06 15:20:55
avalon/merlin/composition/impl/src/test/org/apache/avalon/playground/basic - New
directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mcconnell2004/01/06 15:20:47
avalon/merlin/composition/impl/src/test/org/apache/avalon/playground - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Berin Loritsch wrote:
Tone it down big guy. I am juggling three different thought processes
currently, and I am not in a position to give a more clear answer just
yet. Maybe later, but right now I am juggling too many things and quite
frankly the ones that pay me have higher priority.
!!??!!??
W
Berin Loritsch wrote:
Stephen McConnell wrote:
Berin Loritsch wrote:
Tone it down big guy. I am juggling three different thought processes
currently, and I am not in a position to give a more clear answer just
yet. Maybe later, but right now I am juggling too many things and quite
frankly the
Okay, enough.
I don't want to get on a plane to see you guys and teach you good manners.
;-)
Also I wasn't convinced yet of the irrefutable need to change meta package,
but I agree with the serialization strategy is better. Although making Leo's
work support the currently usage is much better -
Stephen McConnell wrote:
Berin Loritsch wrote:
Tone it down big guy. I am juggling three different thought processes
currently, and I am not in a position to give a more clear answer just
yet. Maybe later, but right now I am juggling too many things and quite
frankly the ones that pay me have h
Berin Loritsch wrote:
Stephen McConnell wrote:
Berin Loritsch wrote:
Stephen McConnell wrote:
Stephen McConnell wrote:
>> No. I didn't ask for the ramifications .. I just asked you
>> what your underlying reasons were. Presumably you are trying
>> to do *something* and its not easy t
Stephen McConnell wrote:
Berin Loritsch wrote:
Stephen McConnell wrote:
Stephen McConnell wrote:
>> No. I didn't ask for the ramifications .. I just asked you
>> what your underlying reasons were. Presumably you are trying
>> to do *something* and its not easy to do.
>>
>> What is
Berin Loritsch wrote:
Stephen McConnell wrote:
Stephen McConnell wrote:
>> No. I didn't ask for the ramifications .. I just asked you
>> what your underlying reasons were. Presumably you are trying
>> to do *something* and its not easy to do.
>>
>> What is that *something*?
What is
Stephen McConnell wrote:
Stephen McConnell wrote:
>> No. I didn't ask for the ramifications .. I just asked you
>> what your underlying reasons were. Presumably you are trying
>> to do *something* and its not easy to do.
>>
>> What is that *something*?
What is it that you are trying
Berin Loritsch wrote:
Stephen McConnell wrote:
Can you point me to some concrete examples where third party
classloaders cannot access resources in a jar file? It's not a
problem I'm seeing. In fact I would be really surprised if this was a
real problem as it would negate just about any rea
Stephen McConnell wrote:
Can you point me to some concrete examples where third party
classloaders cannot access resources in a jar file? It's not a problem
I'm seeing. In fact I would be really surprised if this was a real
problem as it would negate just about any real application out there
Berin Loritsch wrote:
Stephen McConnell wrote:
Berin Loritsch wrote:
In order to solve "model" issues much easier and much more flexibly,
What "model" issues are your referring to?
Sometimes new features need new meta info to help fine tune those features.
For instance, dynamic generation o
Niclas Hedhman wrote:
On Wednesday 07 January 2004 00:15, Niclas Hedhman wrote:
Sorry Berin, I think you missed the target - Why do it in the first place?
Typo...
Sorry Berin, I think you missed the target - Why do I need it in the first
place?
Sometimes new features need new meta info to hel
Niclas Hedhman wrote:
On Tuesday 06 January 2004 23:22, Berin Loritsch wrote:
In order to solve "model" issues much easier and much more flexibly, I
propose to use the work that Leo did a while back with the Attributes
embedded in the class file itself.
Without knowing too much (as usual) about
On Wednesday 07 January 2004 00:15, Niclas Hedhman wrote:
> Sorry Berin, I think you missed the target - Why do it in the first place?
Typo...
Sorry Berin, I think you missed the target - Why do I need it in the first
place?
-
Stephen McConnell wrote:
Berin Loritsch wrote:
In order to solve "model" issues much easier and much more flexibly,
What "model" issues are your referring to?
Sometimes new features need new meta info to help fine tune those features.
For instance, dynamic generation of intrumentation points, or
On Wednesday 07 January 2004 00:05, Berin Loritsch wrote:
> Niclas Hedhman wrote:
> > Open for arguments...
I see a list of "why not, not do it" (I just love double negation), which
doesn't imply "why to do it".
Let's see in detail what we can dig out of these arguments;
> I understand the conc
Berin Loritsch wrote:
Niclas Hedhman wrote:
On Tuesday 06 January 2004 23:22, Berin Loritsch wrote:
In order to solve "model" issues much easier and much more flexibly, I
propose to use the work that Leo did a while back with the Attributes
embedded in the class file itself.
Without knowing
Berin Loritsch wrote:
Jonathan Hawkes wrote:
I've heard Leo's work with Attributes mentioned a lot in this group. For
those of us coming in late in the game, do you have an
example/illustration?
Thanks!
Jonathan Hawkes
The basic principle doesn't change. You still have to declare them via a
j
Niclas Hedhman wrote:
On Tuesday 06 January 2004 23:22, Berin Loritsch wrote:
In order to solve "model" issues much easier and much more flexibly, I
propose to use the work that Leo did a while back with the Attributes
embedded in the class file itself.
Without knowing too much (as usual) abo
Berin Loritsch wrote:
In order to solve "model" issues much easier and much more flexibly,
What "model" issues are your referring to?
Keep in mind that the Avalon Meta package is about meta-info associated
with component types and service definitions. There are no issues with
this that I am
On Tuesday 06 January 2004 23:22, Berin Loritsch wrote:
> In order to solve "model" issues much easier and much more flexibly, I
> propose to use the work that Leo did a while back with the Attributes
> embedded in the class file itself.
Without knowing too much (as usual) about the subject, I w
Jonathan Hawkes wrote:
I've heard Leo's work with Attributes mentioned a lot in this group. For
those of us coming in late in the game, do you have an example/illustration?
Thanks!
Jonathan Hawkes
The basic principle doesn't change. You still have to declare them via a
javadoc comment, but the s
Thanks!
- Original Message -
From: "Hamilton Verissimo de Oliveira (Engenharia - SPO)"
<[EMAIL PROTECTED]>
To: "Avalon Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, January 06, 2004 9:40 AM
Subject: RES: [RT] Changing Meta Package
> -Mensagem original-
> De: Hamilton Veris
-Mensagem original-
De: Hamilton Verissimo de Oliveira (Engenharia - SPO)
> Please see http://cvs.apache.org/viewcvs.cgi/avalon-sandbox/attributes/
and get redirect to
http://cvs.apache.org/viewcvs.cgi/jakarta-commons-sandbox/attributes/
:-)
---
Please see http://cvs.apache.org/viewcvs.cgi/avalon-sandbox/attributes/
regards,
hammett
-Mensagem original-
De: Jonathan Hawkes [mailto:[EMAIL PROTECTED]
Enviada em: terça-feira, 6 de janeiro de 2004 12:35
Para: Avalon Developers List
Assunto: Re: [RT] Changing Meta Package
I've hear
I've heard Leo's work with Attributes mentioned a lot in this group. For
those of us coming in late in the game, do you have an example/illustration?
Thanks!
Jonathan Hawkes
- Original Message -
From: "Berin Loritsch" <[EMAIL PROTECTED]>
To: "Avalon Developers List" <[EMAIL PROTECTED]>
In order to solve "model" issues much easier and much more flexibly, I propose
to use the work that Leo did a while back with the Attributes embedded in the
class file itself. It is a much more flexible way of doing things which will
not require future modifications to the meta model to take care
Stephen McConnell wrote:
To be honest, I am not in a situation where I need enterprise level
architecture anymore. I just need something simple.
The current Fortress does fit my needs, and I am almost scared to try
Merlin.
There are two important questions here:
(a) why does Fortress not
The logging project will host the log4net project soon. Now we don't have to
be afraid of be the only one ASF project with CLI issues... no more! :-)
hammett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Giacomo Pati wrote:
Stephen, what should that tell me: You spread the refactoring not only
to the core and sub-system but also onto meta, repo, util, etc?
Avalon Meta was initially within the Merlin system (back in 2.1). It
was moved out to a separate Avalon level package and in that process
t
Niclas Hedhman wrote:
On Tuesday 06 January 2004 14:37, Giacomo Pati wrote:
Stephen McConnell wrote:
As far as commit messages are concerned, please take into consideration
(a) commits on implementation improvements, (b) commits related to
sub-system relocation (i.e. system moving out of merlin
mcconnell2004/01/06 03:42:18
Modified:repository/site/xdocs/about reference.xml
Log:
Correct table defintion.
Revision ChangesPath
1.5 +0 -1 avalon/repository/site/xdocs/about/reference.xml
Index: reference.xml
===
Niclas Hedhman wrote:
You start sounding like a demanding Corporate Manager :D
No-one likes to be told they need discipline. "Accusing" me of
"management" because of it...how dare you? :P
May I suggest a slightly different 1,2,3;
yes you may!
Step 1. Write a test.
Step 2. Refactor a "smell".
Ste
Steve wrote:
> My guess is that your probably thinking about "how do I make Merlin
> internals do what I want" - and yes - that could be scary. But the
> solution here is rather simple - take a step back and separate out the
> following:
>
> (a) bootstrapping, this is all 100% avalon-repository
I'd like to have a container that does everything that Phoenix does and
additionally has good end user documentation. Merlin comes closest to that.
Ulrich
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-
39 matches
Mail list logo