On May 26, 2009, at 3:00 PM, Matteo Pelucco wrote:
Grégory Joseph ha scritto:
So -- my question to you: why are you doing this? (I'd like to
understand the reason, so as to provide either good advice or fix
something on our end)
The *main* reason is that we would like to avoid to declare
dependancies to standard magnolia jars: now I have the information
that "magnolia-project" is intended as internal (Magnolia Team) POM
and not a public one.
So, I think that in our parent project we must "copy" almost of
magnolia-project dependancies, isn't it?
Why would you? They'll be transitively brought in if they're needed.
mvn help:effective-pom and mvn dependency:tree should help figuring
out what's in and what's out.
-g
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
