> -----Original Message-----
> From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 30, 2004 09:32
> To: Avalon Developers List
> Subject: Re: Question about closing a LogKit PriorityFilteringTarget
> 
> On Friday 30 July 2004 15:11, Leif Mortenson wrote:
> 
> > Thanks, I had got this much figured out.   That helpful README.txt in
> > the root does
> > wonders :-)   The whole thing built on the first time through without
> > any problems.
> > Great job!!!
> 
> Thanks. We hope to productify Magic soon, so it will be easy to use in
> other
> projects/products as well.
> 
> > Is there a way to tell Magic to put
> > its targets into
> > the maven local repository?
> 
> Yes. There are the 'properties' and the 'env variable' approach.
> I think setting the environment variable
> MAGIC_HOME=$HOME/.maven/repository
> is the most convenient for you.
> 
> > I thought that I could maybe do this by setting Magic to use the Maven
> > repository, but
> > their directory hierarchies are a bit different.   It looks like the
> > files that Magic downloads
> > use the same structure,  but the avalon targets are all placed into an
> > avalon subdirectory
> > within the repository.
> 
> This is actually not an Magic/Maven issue at all. The structures ARE the
> same,
> but we want to reduce the number of top level directories, and therefor
> moved
> to "avalon/logkit" as the group. One could argue if there is any meaning
> of
> doing this on those artifacts that already have top level directories in
> ibiblio.org/maven
> 
> Locally, you can temporary fix this, by opening runtime/index.xml, and
> change
> the <group> for LogKit from "avalon/logkit" to "avalon-logkit".

Or better still - change the <groupId> reference in project.xml from
Avalon-logkit to avalon/logkit.

Steve.

> 
> 
> Cheers
> Niclas
> 
> --
>    +------//-------------------+
>   / http://www.bali.ac        /
>  / http://niclas.hedhman.org /
> +------//-------------------+
> 
> 
> ---------------------------------------------------------------------
> 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