Hi, > > Try the following: > > $ merlinx -execute target/classes
perfect. > > This does not make a lot of sense relative to the command line. You > command line is setting the deployment target to the target/classes > directory. As such template-impl-1.0.jar is being referenced. I'm > going to assume that the stack trace was a result of running something like: > > $ merlin -execute target/classes/template-impl-1.0.jar correct. My mistake. I was trying different things. > > Merlin maintains a separate repository form Maven mainly because of > conflicts that arrive when development objectives and deployment > objectives conflict. But you can manage this by either using merlinx, > or using the -repository parameter to declare that the default > repository to use is the maven repo. the documentaiton said as of build 3.2-dev 20031210 the default ~/.avalon is being used as the repository unless set differenting (using AVALON_HOME, or merlin.properties). What I couldn't figure out is why as part of building the template, template*.jar were not written to merlin repository (at ~/.avalon) and instead written to ~/.maven repository ? Is deploying my jar files for my component/service to merlin repository a manual process when I am ready to deploy a merlin application ? > > Hope that clears things up. it did. Thanks much. > > Cheers, Steve. > > -- > |------------------------------------------------| > | Magic by Merlin | > | Production by Avalon | > | | > | http://avalon.apache.org/merlin | > | http://dpml.net/ | > |------------------------------------------------| > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
