korosh afshar wrote:


I just ported over a legacy code and made it into a component.


This code as dependency on some other custom library jar files.


while developing I used a project.properties to define a local path to each of the jar files to bypass the maven repository lookup scheme.

eg. maven.jar.myjar1 = ${basedir}/../lib/myjar1.jar etc.


But now I want to deploy to merlin and it complains about missing classes referenced by the component, which are in the jar dependent files.

Do I use block.xml for configuring this ?

The block.xml file is used when constructing a jar file that you want to deploy as a composite component. Using block.xml is optional (but rather convenient).


Another approach is to define a free-standing block definition. This is the same as a block.xml file except that it includes *all* required resources in the blocks classloader definition.

Unfortunately there isn't a tutorial on this subject just yet ... ummm, we should do something about that.


Should I manually copy my jar files into merlin's reposiotry cache ?

That's that will work and is perfectly sensible during development. When you get to formal system deployment you may want to consider setting up a special repository (locally or accessible over http) and including you jar files in the repository. To do this you need to declare a repository element in you kernel.xml file.


http://avalon.apache.org/merlin/meta/kernel/repository/index.html

Cheers, Stephen.


I am little confused about that?


thanks Korosh.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




--

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



Reply via email to