That fixed it perfectly! I have added to my shared project.xml these
entities:
<dependency>
<groupId>avalon-meta</groupId>
<artifactId>avalon-meta-plugin</artifactId>
<version>1.4.0</version>
<url>http://avalon.apache.org</url>
<type>plugin</type>
</dependency>
<dependency>
<groupId>avalon-util</groupId>
<artifactId>avalon-util-plugin</artifactId>
<version>1.0.0</version>
<url>http://avalon.apache.org</url>
<type>plugin</type>
</dependency>
<dependency>
<groupId>merlin</groupId>
<artifactId>merlin-plugin</artifactId>
<version>3.3.0</version>
<url>http://avalon.apache.org</url>
<type>plugin</type>
</dependency>
And they seem to download fine. However.. avalon-util.. do I need that
plugin if I am running unit tests? I added it because it was in the dist
plugin folder... But the docs didn't seem to refer to it..
Eric
> -----Original Message-----
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 30, 2004 12:45 AM
> To: Avalon framework users
> Subject: Re: Back on the list.. And first issue
>
>
> Stephen McConnell wrote:
>
> > Now onto the real problem ... in you scenario your getting an exception
> > indicating that the a "test" container is not assembled. I have no
> > immediate idea what could be causing that but I'm updating my checkout
> > of fulcrum and I'll take a look.
> >
>
> Have identified two problems:
>
> 1. Not sure why but the maven setup we have in fulcrum is
> resulting in merlin attempting to establish containers
> relative to both target/classes and target/test-classes
> and this is causing a conflict (which is not being
> detected by merlin which is leading to the creation of
> a second container of the same name that is not being
> assembled). As far as the merlin side of this problem is
> concerned I've registered the following JIRA issue:
> http://nagoya.apache.org/jira/browse/RUNTIME-40
>
> The solution to the problem is to add a merlin.properties
> file into the configuration/impl directory containing
> the following:
>
> merlin.info = false
> merlin.debug = false
> merlin.audit = false
> merlin.deployment = target/test-classes
> merlin.override = conf/config.xml
>
> The important line in the above is merlin.deployment value
> which will ensure that only one container is declared.
>
> 2. Once the above is resolved a error was reported concerning
> the configuration component requesting a context entry for
> urn:avalon:home - however, the component had not declared
> this - adding a @avalon.entry spec on the contextualize
> method fixes this (see attached path).
>
> 3. Under 3.3 I'm getting a deployment timeout so I added the
> following to the class level component info:
>
> @avalon.attribute
> key="urn:composition:deployment.timeout" value="0"
>
> BUILD SUCCESSFUL
> Total time: 24 seconds
>
> Cheers, Steve.
>
> --
>
> |---------------------------------------|
> | Magic by Merlin |
> | Production by Avalon |
> | |
> | http://avalon.apache.org |
> |---------------------------------------|
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
