RE: cvs commit: avalon/fortress/container project.xml

Stephen McConnell wrote: > > Carsten: > > A lifecycle extension dealing with an alternative > configuration model should not go under Fortress - instead it > should be located somewhere like excalibur-configuration or > perhaps more appropriate .. > avalon-components. > > What's your opinion

Re: total domination - no prisoners

Niclas Hedhman wrote: On Tuesday 09 March 2004 13:16, Stephen McConnell wrote: My thoughts for the day. But I would like to highlight that there is an alternate way to go about these concerns; The current approach is a lot about converging the existing container implementations and shoe-hor

[GUMP@lsd]: avalon-excalibur/excalibur-logger failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project excalibur-logger has an issue affecting it's community integration. This issue

[GUMP@lsd]: avalon-excalibur/excalibur-logger failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project excalibur-logger has an issue affecting it's community integration. This issue

Re: total domination - no prisoners

On Tuesday 09 March 2004 13:16, Stephen McConnell wrote: > My thoughts for the day. But I would like to highlight that there is an alternate way to go about these concerns; The current approach is a lot about converging the existing container implementations and shoe-horn in the 'behaviour' o

total domination - no prisoners

My thoughts for the day. A quiet weekend brings me to the open subject of the resolution of a the avalon component model and our support for the one true model. According to Silvian Wallez, the one true model is a step too far in the direction of too much magic. However - before we accept this

cvs commit: avalon/merlin/facilities/finder/test/src/java/org/apache/avalon/finder/test Widget.java

mcconnell2004/03/08 17:48:09 Modified:merlin/facilities/finder/test/conf block.xml merlin/facilities/finder/test/src/java/org/apache/avalon/finder/test Widget.java Log: Add ecm to testcase. Revision ChangesPath 1.2 +12 -0 a

ECM facility

I've just committed some content into the merlin/facility directory dealing with a pull-based service finder implementation. This commit is dealing with two things: (a) an example of the addition of a semantic extension to merlin without modification or extension to the container

cvs commit: avalon-site/site/finder - Imported sources

mcconnell2004/03/08 16:49:13 Log: Inital import of finder docs. Status: Vendor Tag: AVALON Release Tags: DOCS_20040309 N avalon-site/site/finder/api.html N avalon-site/site/finder/cvs-usage.html N avalon-site/site/finder/dependencies.html N avalon-site/site/finder/

Re: cvs commit: avalon/fortress/container project.xml

J Aaron Farr wrote: On Mon, 2004-03-08 at 19:38, Stephen McConnell wrote: Carsten: A lifecycle extension dealing with an alternative configuration model should not go under Fortress - instead it should be located somewhere like excalibur-configuration or perhaps more appropriate .. avalon-com

Re: cvs commit: avalon/fortress/container project.xml

On Mon, 2004-03-08 at 19:38, Stephen McConnell wrote: > Carsten: > > A lifecycle extension dealing with an alternative configuration model > should not go under Fortress - instead it should be located somewhere > like excalibur-configuration or perhaps more appropriate .. > avalon-components. >

Re: cvs commit: avalon/fortress/container project.xml

Carsten: A lifecycle extension dealing with an alternative configuration model should not go under Fortress - instead it should be located somewhere like excalibur-configuration or perhaps more appropriate .. avalon-components. What's your opinion? Stephen. [EMAIL PROTECTED] wrote: cziegeler

cvs commit: avalon/merlin/facilities/finder/test/src/java/org/apache/avalon/finder/test ECMWidget.java

mcconnell2004/03/08 16:27:08 Modified:merlin/facilities/finder maven.xml project.properties project.xml merlin/facilities/finder/ecm/src/java/org/apache/avalon/finder/ecm DefaultRoleManager.java ECM.java Added: merlin

cvs commit: avalon/merlin/facilities/finder/site/xdocs/ecm - New directory

mcconnell2004/03/08 16:26:18 avalon/merlin/facilities/finder/site/xdocs/ecm - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon/merlin/facilities/finder/site/xdocs - New directory

mcconnell2004/03/08 16:26:09 avalon/merlin/facilities/finder/site/xdocs - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon/merlin/facilities/finder/site/etc - New directory

mcconnell2004/03/08 16:25:52 avalon/merlin/facilities/finder/site/etc - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon/merlin/facilities/finder/site - New directory

mcconnell2004/03/08 16:25:35 avalon/merlin/facilities/finder/site - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: State of the Aspect

Leo Sutic wrote: For example, Merlin has something called Dependency Validation. This means that the container will validate your components and make sure that all dependencies are satisfied before even starting the components. (ECM and Fortress will just happily start components and run until on

Re: State of the Aspect

Hamilton Verissimo de Oliveira (Engenharia - SPO) wrote: -Mensagem original- De: Stephen McConnell [mailto:[EMAIL PROTECTED] 1. interdependencies between aspects - My feeling is that as aspect is independent, and if a dependency is identified, then in fact your not looking at a

Re: State of the Aspect

-Mensagem original- De: Stephen McConnell [mailto:[EMAIL PROTECTED] >1. interdependencies between aspects - My feeling is that > as aspect is independent, and if a dependency is identified, then > in fact your not looking at an aspect - instead its a system > of some

[jira] Created: (FORTRESS-3) In an initialization failure, fortress keeps a not daemon thread that prevents the VM from shutting down

Message: A new issue has been created in JIRA. - View the issue: http://issues.apache.org/jira/secure/ViewIssue.jspa?key=FORTRESS-3 Here is an overview of the issue: --

RE: State of the Aspect

> From: Hamilton Verissimo de Oliveira (Engenharia - SPO) > > Lesson learned: never had a dinner at LS's house. He can't > even make a good spaghetti! Butler voice: Dinner will be eaten with knife, fork, hammer and chisel, sir... /LS -

Re: State of the Aspect

Leo: Three things (if I'm tracking this correctly) that you are raising: 1. interdependencies between aspects - My feeling is that as aspect is independent, and if a dependency is identified, then in fact your not looking at an aspect - instead its a system of some kind. I also

Re: State of the Aspect

-Mensagem original- De: Leo Sutic [mailto:[EMAIL PROTECTED] > This is done by providing a very minimal kernel, to which one > can add kernel features called "Aspects" (I haven't come up with > a better name - any ideas?). plugins, concerns... boy this is difficult. > For example, Merlin

RE: State of the Aspect

> From: Jonathan Hawkes [mailto:[EMAIL PROTECTED] > > Yes, very cool, but you didn't actually answer my question :) > > The thread had something do with AOP Aspects and their > dependencies (I think). I believe one of the questions was, > "should one aspect inherit its dependencies from ano

[Apache Avalon Wiki] Updated: AvalonReleaseManagerHowto

Date: 2004-03-08T13:19:10 Editor: 212.198.0.93 <> Wiki: Apache Avalon Wiki Page: AvalonReleaseManagerHowto URL: http://wiki.apache.org/avalon/AvalonReleaseManagerHowto no comment Change Log: -- @@ -66,8

[Apache Avalon Wiki] Updated: AvalonReleaseManagerHowto

Date: 2004-03-08T12:48:10 Editor: AaronFarr <[EMAIL PROTECTED]> Wiki: Apache Avalon Wiki Page: AvalonReleaseManagerHowto URL: http://wiki.apache.org/avalon/AvalonReleaseManagerHowto cleaned up formatting -farra Change Log: ---

Re: State of the Aspect

-Mensagem original- De: Jonathan Hawkes [mailto:[EMAIL PROTECTED] Enviada em: segunda-feira, 8 de março de 2004 17:10 > Yes, very cool I'm weasel. > but you didn't actually answer my question :) Not that much, then.. > The thread had something do with AOP Aspects and their dependencies

Re: State of the Aspect

Yes, very cool, but you didn't actually answer my question :) The thread had something do with AOP Aspects and their dependencies (I think). I believe one of the questions was, "should one aspect inherit its dependencies from another aspect". Actually, I never quite understood the thread; and th

Re: State of the Aspect

A more specific use case would be keep our foots on the ground :-) So I think before discussing what LoggerAspect or SecurityAspect actually do, we shold bring to table what we actually need - in the light of what would make things easier. * What Avalon provides * A framework to write applicatio

Re: State of the Aspect

It might help if you can come up with a more specific use case. What does LoggerAspect actually do? And what does SecurityAspect actually do? And how is it dependent on LoggerAspect? So in type 3 form, public class LoggerAspectImpl implements LoggerAspect { public LoggerAspectImpl(Logger l

Re: State of the Aspect

> So I'm close to just disallowing any explicit dependencies. Do you see any possiblity of dependencies that aren't loggers? So, instead of LoggerAspect loggerAspect = new LoggerAspectImpl( something ); kernel.addAspect( loggerAspect ); SecurityAspect secAspect = new SecurityAspectImpl(

RE: State of the Aspect

> From: Alex Karasulu [mailto:[EMAIL PROTECTED] > > > Instead, borrow from Pico; > > > > LoggerAspect loggerAspect = new LoggerAspectImpl( something ); > > kernel.addAspect( loggerAspect ); > > You're dead on by looking at Pico for answers here. That looks good - but I've been thinking ab

cvs commit: avalon/fortress/container project.xml

cziegeler2004/03/08 10:50:25 Modified:fortress/container project.xml Added: fortress/container/src/impl/org/apache/avalon/fortress/util ReflectiveConfigurator.java Log: Fortress-Creator that uses reflection instead of Parameterizable/Configurable to

cvs commit: avalon-site/site/excalibur/fortress/style maven.css maven_ns4_only.css ns4_only.css print.css tigris.css

farra 2004/03/08 10:25:23 Modified:site download.html index.html news.html xdocsdownload.html index.xml news.xml Added: site/community/who hammett.html site/excalibur/fortress/api allclasses-frame.html allclasses-nof

Re: [site] uh, where did Fortress go?

On Mon, 2004-03-08 at 13:11, Stephen McConnell wrote: > J Aaron Farr wrote: > > > Hello. > > > > Ummm. Perhaps I'm just really confused, but shouldn't the fortress HTML > > docs end up in: > > > > http://cvs.apache.org/viewcvs.cgi/avalon-site/site/excalibur/ > > > > Where are they? I have upd

cvs commit: avalon-site/site/excalibur/fortress/images/logos - New directory

farra 2004/03/08 10:17:56 avalon-site/site/excalibur/fortress/images/logos - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/util/dag/class-use - New directory

farra 2004/03/08 10:17:47 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/util/dag/class-use - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECT

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/util/dag - New directory

farra 2004/03/08 10:17:40 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/util/dag - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/util/class-use - New directory

farra 2004/03/08 10:17:40 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/util/class-use - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/role/class-use - New directory

farra 2004/03/08 10:17:32 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/role/class-use - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTEC

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/lookup/class-use - New directory

farra 2004/03/08 10:17:26 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/lookup/class-use - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROT

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/handler/class-use - New directory

farra 2004/03/08 10:17:17 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/handler/class-use - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PRO

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/factory/class-use - New directory

farra 2004/03/08 10:17:10 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/factory/class-use - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PRO

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/lookup - New directory

farra 2004/03/08 10:16:56 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/lookup - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/extensions/class-use - New directory

farra 2004/03/08 10:17:03 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/extensions/class-use - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/handler - New directory

farra 2004/03/08 10:16:56 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/handler - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/role - New directory

farra 2004/03/08 10:16:56 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/role - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/factory - New directory

farra 2004/03/08 10:16:55 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/factory - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/extensions - New directory

farra 2004/03/08 10:16:55 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/extensions - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/class-use - New directory

farra 2004/03/08 10:16:55 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl/class-use - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl - New directory

farra 2004/03/08 10:16:48 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/impl - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/util - New directory

farra 2004/03/08 10:16:48 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/util - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress - New directory

farra 2004/03/08 10:16:45 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/class-use - New directory

farra 2004/03/08 10:16:48 avalon-site/site/excalibur/fortress/api/org/apache/avalon/fortress/class-use - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache - New directory

farra 2004/03/08 10:16:38 avalon-site/site/excalibur/fortress/api/org/apache - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org/apache/avalon - New directory

farra 2004/03/08 10:16:40 avalon-site/site/excalibur/fortress/api/org/apache/avalon - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/resources - New directory

farra 2004/03/08 10:16:35 avalon-site/site/excalibur/fortress/api/resources - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api/org - New directory

farra 2004/03/08 10:16:35 avalon-site/site/excalibur/fortress/api/org - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/style - New directory

farra 2004/03/08 10:16:28 avalon-site/site/excalibur/fortress/style - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/images - New directory

farra 2004/03/08 10:16:28 avalon-site/site/excalibur/fortress/images - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress/api - New directory

farra 2004/03/08 10:16:28 avalon-site/site/excalibur/fortress/api - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon-site/site/excalibur/fortress - New directory

farra 2004/03/08 10:16:25 avalon-site/site/excalibur/fortress - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [site] uh, where did Fortress go?

J Aaron Farr wrote: Hello. Ummm. Perhaps I'm just really confused, but shouldn't the fortress HTML docs end up in: http://cvs.apache.org/viewcvs.cgi/avalon-site/site/excalibur/ Where are they? I have updated I want to post. Anyone hiding them somewhere? :) avalon\fortress\docs\src\xdocs St

cvs commit: avalon/fortress/container/src/test/org/apache/avalon/fortress/test MetaInfoEntryTestCase.java

cziegeler2004/03/08 10:05:46 Modified: fortress/container/src/test/org/apache/avalon/fortress/impl/extensions/test InstrumentableCreatorTestCase.java fortress/container/src/test/org/apache/avalon/fortress/test MetaInfoEntryTe

cvs commit: avalon/fortress/new/xdocs index.xml

farra 2004/03/08 09:47:08 Modified:fortress/new/etc site.jsl fortress/new project.xml fortress/new/xdocs index.xml Log: updated the index to mention the new release updated the site.jsl to removed apachecon link Revision ChangesPath 1.2

[site] uh, where did Fortress go?

Hello. Ummm. Perhaps I'm just really confused, but shouldn't the fortress HTML docs end up in: http://cvs.apache.org/viewcvs.cgi/avalon-site/site/excalibur/ Where are they? I have updated I want to post. Anyone hiding them somewhere? :) -- jaaron -

Re: Fortress updates

On Mon, 2004-03-08 at 09:50, Niclas Hedhman wrote: > Hi, > > I have (with Aaron's help) made the modifications for Fortress to build. > > cd fortress/container > maven jar:install > cd ../tools > maven jar:install > cd ../examples > maven jar:jar > > I will see if I can get any of these to run..

cvs commit: avalon/fortress/examples/src/test test.txt

farra 2004/03/08 08:00:23 Modified:fortress/examples maven.xml project.xml fortress/examples/src/java/org/apache/avalon/fortress/examples/swing Main.java fortress/examples/src/java/org/apache/avalon/fortress/examples/viewer

Fortress updates

Hi, I have (with Aaron's help) made the modifications for Fortress to build. cd fortress/container maven jar:install cd ../tools maven jar:install cd ../examples maven jar:jar I will see if I can get any of these to run... Niclas -- +-//---+ | http://www.bali.ac

cvs commit: avalon/fortress/examples/src/test placeholder

niclas 2004/03/08 06:47:11 Modified:fortress/examples project.xml Added: fortress/examples/src/test placeholder Log: Fixed up so fortress builds... Revision ChangesPath 1.3 +6 -1 avalon/fortress/examples/project.xml Index: project.xml ==

cvs commit: avalon/fortress/examples/src/test - New directory

niclas 2004/03/08 06:46:42 avalon/fortress/examples/src/test - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Fortress Builds

On Mon, 2004-03-08 at 09:28, J Aaron Farr wrote: > On Mon, 2004-03-08 at 09:03, Niclas Hedhman wrote: > > 1. Container builds with "maven jar:jar" :o) > > > > 2. Examples gives an Exception. > > There was an empty "dependency" tag. I've committed a new project.xml. > Try that. (still may not b

Re: Fortress Builds

On Mon, 2004-03-08 at 09:03, Niclas Hedhman wrote: > 1. Container builds with "maven jar:jar" :o) > > 2. Examples gives an Exception. There was an empty "dependency" tag. I've committed a new project.xml. Try that. (still may not build completely, but maven won't choke) -- jaaron

cvs commit: avalon/fortress/examples project.xml

farra 2004/03/08 06:36:02 Modified:fortress/examples project.xml Log: removed empty dependency Revision ChangesPath 1.2 +3 -8 avalon/fortress/examples/project.xml Index: project.xml ===

cvs commit: avalon/fortress README.txt

farra 2004/03/08 06:20:54 Added: fortress README.txt Log: small Fortress readme with simple build instructions Revision ChangesPath 1.1 avalon/fortress/README.txt Index: README.txt ===

Re: Fortress Builds

1. Container builds with "maven jar:jar" :o) 2. Examples gives an Exception. __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-beta-10 WARN: Exception: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationT

Re: Fortress Builds

On Mon, 2004-03-08 at 09:01, Hamilton Verissimo de Oliveira (Engenharia - SPO) wrote: > -Mensagem original- > De: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > > > And I see personally no reason why we need this maven-common.xml :) > > "Too much magic, too much magic" syndrome :-) > I ag

Re: Fortress Builds

-Mensagem original- De: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > And I see personally no reason why we need this maven-common.xml :) "Too much magic, too much magic" syndrome :-) - To unsubscribe, e-mail: [EMAIL PRO

RE: Fortress Builds

From: Hamilton Verissimo de Oliveira (Engenharia - SPO) > > Leo, > > I think the maven.xml distributed with Fortress won't work in > a directory structure different than what we have in the CVS. > > This maven project looks for a > ${avalon.buildsystem}/maven-common.xml that is not packag

Re: Fortress Builds

Leo, I think the maven.xml distributed with Fortress won't work in a directory structure different than what we have in the CVS. This maven project looks for a ${avalon.buildsystem}/maven-common.xml that is not package with it. -- hammett -Mensagem original- De: Leo Sutic [mailto:[EMA

RE: State of the Aspect

> -Original Message- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > > On Monday 08 March 2004 16:09, Leo Sutic wrote: > > -oOo- > > > > One problem is about interdependencies between aspects. Suppose you make > > logging an aspect. Then you make security an as

RE: Fortress Builds

(I never bothered reading all that.) Try maven jar:install, or maven dist. /LS > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Fortress Builds

On Monday 08 March 2004 21:17, Leo Sutic wrote: > What error messages do you get? I managed to build fortress/container > just fine when I did the release. Not sure if you can call it an "error message", more like instructions "do this" (see below) The http://nagoya.apache.org/wiki/apachewik

RE: Fortress Builds

> From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > > Can someone in the "Fortress Proponents Camp" give me some > short explaination of how to build Fortress in CVS? What error messages do you get? I managed to build fortress/container just fine when I did the release. /LS -

RE: Fortress Builds

Niclas Hedhman wrote: > > > BTW, would someone be against using the maven multiproject > plugin for > > Fortress and make the build much easier (and working for all)? > > Really? IMHO, the more "maven" the worst the situation, but > maybe that is only me. > Shrug. As I wrote recently, we use

Re: Fortress Builds

On Monday 08 March 2004 20:08, Carsten Ziegeler wrote: > I guess the only one who knows how to build fortress is Leo. He managed to > get the release out, so somehow it should be possible... That really helps considering his current status :o( Berin? > BTW, would someone be against using the

RE: Fortress Builds

I guess the only one who knows how to build fortress is Leo. He managed to get the release out, so somehow it should be possible... BTW, would someone be against using the maven multiproject plugin for Fortress and make the build much easier (and working for all)? Carsten > -Original Messag

Fortress Builds

Hi, Can someone in the "Fortress Proponents Camp" give me some short explaination of how to build Fortress in CVS? I get a large output if I do "maven" in fortress/container, telling me to follow instructions on http://nagoya.apache.org/wiki/apachewiki.cgi?MavenForrestPlugin which tells me t

cvs commit: avalon/logging/test project.xml

niclas 2004/03/08 03:32:02 Modified:logging/impl project.xml logging/impl/src/java/org/apache/avalon/logging/impl ConfigurationParameter.java DefaultLoggingCriteria.java LoggerParameter.java logging/log4j proj

[Apache Avalon Wiki] Updated: FrontPage

Date: 2004-03-08T03:29:37 Editor: 81.225.126.237 <> Wiki: Apache Avalon Wiki Page: FrontPage URL: http://wiki.apache.org/avalon/FrontPage What's wrong with "welcome"? Change Log: -- @@ -1,6 +1,6 @@ #pr

cvs commit: avalon/repository/impl/src/java/org/apache/avalon/repository/impl DefaultFactory.java

niclas 2004/03/08 03:26:10 Modified:repository/impl/src/java/org/apache/avalon/repository/impl DefaultFactory.java Log: Slowly removing excalibur dependencies from Merlin. Revision ChangesPath 1.9 +3 -3 avalon/repository/impl/src/java/

cvs commit: avalon/repository/impl project.xml

niclas 2004/03/08 03:26:10 Modified:repository/cli project.xml repository/cli/src/java/org/apache/avalon/repository/cli Main.java RepositoryVerifier.java repository/impl project.xml Log: Slowly removing excalibur dependencies fro

cvs commit: avalon/meta/impl/src/java/org/apache/avalon/meta/info/verifier TypeVerifier.java

niclas 2004/03/08 03:24:53 Modified:meta/impl project.xml meta/impl/src/java/org/apache/avalon/meta/info/builder ServiceBuilder.java TypeBuilder.java XMLLegacyCreator.java XMLServiceCreator.java XMLTy

cvs commit: avalon/util/i18n/src/test/org/apache/avalon/util/i18n/test ResourceManagerTestCase.java ResourceManagerTestCaseResources.properties Resources.properties

niclas 2004/03/08 03:23:05 Added: util/i18n maven.xml project.xml util/i18n/src/java/org/apache/avalon/util/i18n ResourceManager.java Resources.java package.html util/i18n/src/test/org/apache/avalon/util/i18n/test

cvs commit: avalon/util/i18n/src/test/org/apache/avalon/util/i18n/test - New directory

niclas 2004/03/08 03:22:03 avalon/util/i18n/src/test/org/apache/avalon/util/i18n/test - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon/util/i18n/src/test/org/apache/avalon/util/i18n - New directory

niclas 2004/03/08 03:21:49 avalon/util/i18n/src/test/org/apache/avalon/util/i18n - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon/util/i18n/src/java/org/apache/avalon/util/i18n - New directory

niclas 2004/03/08 03:21:49 avalon/util/i18n/src/java/org/apache/avalon/util/i18n - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon/util/i18n/src/java/org/apache/avalon/util - New directory

niclas 2004/03/08 03:21:34 avalon/util/i18n/src/java/org/apache/avalon/util - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: avalon/util/i18n/src/test/org/apache/avalon/util - New directory

niclas 2004/03/08 03:21:34 avalon/util/i18n/src/test/org/apache/avalon/util - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

  1   2   >