Dave:

Here is an example of running a standalone block using the artifact
protocol:

$ merlin artifact:block:avalon/tutorial/hello -execute

This generates the following output

[INFO   ] (tutorial.hello): Hello World!

In the above example the artifact type is 'block', the group is
'avalon/tutorial' and the name of the block is 'hello.  The resulting
path is:

[repository]/avalon/tutorial/blocks/hello.block  

If you run the above command using the default configuration then merlin
will find the artifact in the dpml repository:

http://www.dpml.net/avalon/tutorial/blocks/

The artifact:block:avalon/tutorial/hello uri can be used on the command
line, or equally as a value in the merlin.deployment property.

Cheers, Steve.



-----Original Message-----
From: David Leangen [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 21, 2004 6:19 AM
To: Avalon framework users
Subject: RE: Embedding - howto
Importance: High


I'm up and running!!

Steve helped me work out the issue with resolving to my block definition
file. I actually have to type in the full pathname to this file, so the
code
should be:

criteria.put( "merlin.deployment",
"target/deliverables/block/your-container-defintion.block" );


The thing with this approach, though, is that is doesn't really inspire
confidence for managing projects in the long term. Is anybody able to
share
with me what they consider best practices for managing projects?

I am assuming that the project should be deployed in a jar file, then
sent
to the repository. That way it can be resolved using artifact spec
([repository-cache]/[group]/[type]s/[name]-[version].[type]).


Would you agree that this is the best approach?


Is there a build target that can do this for me, or do I have to make my
own
target to manage my blocks?


Thanks for the insights!


---------------------------------------------------------------------
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]

Reply via email to