Now that I've had a test case fail, how can I achieve jar:install when I can't achieve test:test because Merlin is only looking at jars in the repository, (chicken and the egg paradox)? Is there a way to get it to use target/classes?
The test is already using target/classes. If you add a merlin.properties file to the working directory and add
merlin.info = true
.. you will get a listing of the environment settings. The following is the result of removing the comment from the merlin.info line in the merlin.properties file in the hello tutorial.
----------------------------------------------------------- Merlin Kernel Environment Listing -----------------------------------------------------------
${user.dir} == D:\dev\avalon\merlin\platform\tutorials\hello
${user.home} == C:\WINNT\Profiles\mcconnell${avalon.repository.cache} == D:\system\maven\repository
${avalon.repository.online} == true
${avalon.repository.hosts} == http://www.dpml.net,http://www.ibiblio.org/maven
${merlin.lang} == null
${merlin.home} == D:\merlin
${merlin.system} == D:\merlin\system
${merlin.config} == D:\merlin\config
${merlin.kernel} == file:/D:/merlin/config/kernel.xml
${merlin.logging.implementation} == artifact:avalon-logging/avalon-logkit-impl#1.0-SNAPSHOT
${merlin.logging.config} == null
${merlin.runtime} == artifact:avalon-activation/avalon-activation-impl#2.0-SNAPSHOT
${merlin.override} == conf/config.xml
${merlin.dir} == D:\dev\avalon\merlin\platform\tutorials\hello
${merlin.temp} == C:\TEMP
${merlin.context} == D:\dev\avalon\merlin\platform\tutorials\hello\target
${merlin.anchor} == D:\dev\avalon\merlin\platform\tutorials\hello
${merlin.info} == true
${merlin.debug} == false
${merlin.audit} == false
${merlin.server} == true
${merlin.autostart} == true
${merlin.code.security.enabled} == false
${merlin.deployment.timeout} == 1000
${merlin.repository} == D:\system\maven\repository
${merlin.repository.hosts} == http://www.dpml.net/,http://www.ibiblio.org/maven/
${merlin.deployment} == file:/${user.dir}/target/classes/
The list line of the listing shows the merlin.deployment setting which is by default referencing the target/classes directory as the deployment path. Merlin will look in this directory for a subdirectory name BLOCK-INF containing the file block.xml.
To understand you scenario we would need to know what the testcase has resolved as the deployment path. If you could turn on info listing and post the merlin.deployment value it would be a little easier to figure out what is happening.
I'm sure this is something simple but I'm a bit slow on monday mornings ;)
:-)
Something else you may want to try it switching on merlin.debug. You will get a bunch more information and perhaps the cause of the problem.
Cheers, Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
