#: Michael Mertel changed the world a bit at a time by saying on 10/10/2005
1:27 PM :#
Hi Alex,
because it's a well known problem ... wouldnt it be nice for magnolia
(advanved) newbies to build magnolia without any tricks?
Isn't it possible to have a managed repository by Magnolia for all
related files? It seems so that the dependency on 3rd parties can cause
trouble, at least for maven newbies like me.
Just my $.02.
--Michael
Indeed this would be the best solution from my pov too. There is already a maven repository hosted
by Magnolia. However, there may be problems with hosting downloads for special jars (I am not sure
about this).
we will further investigate this,
./alex
--
.w( the_mindstorm )p.
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 06, 2005 7:04 PM
To: [email protected]
Subject: Re: [magnolia-user] maven build - dependency
#: Michael Mertel changed the world a bit at a time by saying
on 10/6/2005 6:01 PM :#
> Hi,
>
> if I have a clean maven repository and try to compile the
latest SVN
> snapshot ... I always got some dependency problems. At
least with the
> activation package, the jars are not in javax.activation
(requested in
> magnolia, magnolia-core) on
magnolia.sourceforge.net/repository nor in
> www.ibiblio.org/maven.
>
> I can compile without any problem if I put the needed files on my
> local apache and use this as another maven.repo.remote.
>
> Should this be fixed in the SVN? Is it a bug ? ... or is it just me
> silly know-nothing maven newbie ? This only happens if you
don't have
> the needed files already in your maven repo.
>
> --Michael
>
Please check this thread:
http://webmail.magnolia.info/Lists/dev-list/Message/4591.html
./alex
--
.w( the_mindstorm )p.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
