Date: 2004-02-26T12:55:16 Editor: AaronFarr <[EMAIL PROTECTED]> Wiki: Apache Avalon Wiki Page: AvalonFAQ/Merlin URL: http://wiki.apache.org/avalon/AvalonFAQ/Merlin
moved FAQ's from AvalonForBeginners. Perhaps we should change the format? -farr Change Log: ------------------------------------------------------------------------------ @@ -21,8 +21,18 @@ == I am getting an error ''unable to obtain goal [prepare-filesystem]''. What is wrong? == You don't have the Meta Plugin installed or compiled. +===I get an error saying "No Goal \[avalon:meta\]" == +The two plugins need to be added to you [MAVEN-HOME]/plugins directory. The plugins are shipped with the Merlin binary distribution and include: +avalon-meta-plugin-[VERSION].jar +merlin-plugin-[VERSION].jar + = Running Merlin = +== Why does Merlin interrupt the deployment of my component ? == + +Merlin (builds later than Jan 5, 2004) has a mechanism by which if the component takes too long to deploy, it will interrupt its deployment and move on. If your component takes a long time to initialize and deploy, use the deployment-timeout parameter in kernal.xml. Refer to: http://avalon.apache.org/merlin/meta/kernel/parameters/index.html + + == How do I start Merlin? == == Where is the entry point? == @@ -61,8 +71,7 @@ Working Directory: ${project_loc} I'm not following the Mavenized directory within my IDE and the "classes" in the Tool Argument refers to the directory where my class files are located, you can specify whichever directory holds your class files ( like target\classes if you are using mavenized directory structure ) . And you would need to place a BLOCK-INF folder under your source folder ("src" folder in my case) and this folder would hold your block.xml. Also you would need to place your component.xinfo files in the same folder as your component source file e.g if your component is under tutorial folder ( specifying "tutorial" package) the place the xinfo files in it. If you try to copy BLOCK-INF folder or the *.xinfo files directly to the classes folder, Eclipse would delete those when it rebuilds the project. But placing them under source folder would ensure the Eclipse copies that to your classes folder itself and also retains those there. My directory structre for a project named MerlinTest looks likes this: - ------------------------------------------ +{{{ MerlinTest/ src/ tutorial/ @@ -79,8 +88,7 @@ HelloComponent.xinfo BLOCK-INF/block.info - ------------------------------------------------ +}}} Now you should be able to run Merlin CLI from within eclipse by selecting your project (like MerlinTest in my case) in the left navigation or project explorer and go to Run->External Tools and just run the Merlin CLI. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
