Alex Karasulu wrote:
One last question (I can't seem to stop). First take a look at this output from merlin:simulate:
:-)
merlin:prepare-context: [echo] merlin.repository.local = C:\Documents and Settings\Administrator/.ma ven/repository [DEBUG ] (kernel.logging): default priority: DEBUG [DEBUG ] (kernel.logging): adding category: kernel, null [DEBUG ] (kernel.context): logging system established [DEBUG ] (kernel.context): setting repository to: C:\Documents and Settings\Adm inistrator\.maven\repository\repository [DEBUG ] (kernel.context): repository established
Notice the echo of the merlin.repository.local property. Now look at the 4th debug line here:
[DEBUG ] (kernel.context): setting repository to: C:\Documents and Settings\Administrator\.maven\repository\repository
Umm - this is *really* strange - but I think I know what is happening.
What do you think could make the kernel switch from the echo'ed setting to
this one which adds the extra repository component?
The plugin is bootstrapping from the jar files in the maven repository - not from ${merlin.home). In you case you have a version of merlin jars in your maven repository that assume that the argument passes as the repository base directory is in fact the system directory. That's why it is apprending /repository to the path. Could you please delete the avalon-* and merlin directories from the maven repository and try again.
I need to think about this ....
Also you said I should be putting stuff into the ${merlin.home}/repository.
Then what's the reason for having the -repository switch.
Sorry I mean you should be putting content into wherever you point -repository to.
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
