On May 26, 2009, at 3:26 PM, Matteo Pelucco wrote:
Grégory Joseph ha scritto:
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.
Sorry for spending to many words about this, I know that it is
probably due to my little maven knowledge.
But, as far as I know, I've understood that when I need a jar
reference, I need to declare it on parent pom -> dependancies
management and on project pom -> dependancies (without version). By
hands.
What do you mean with "They'll be transitively brought in if they're
needed"?
My parent pom does *not* know to be a Magnolia project, so how can
he attach e.g. a magnolia-core-3.6.3.jar?
In other words, which are the mandatory magnolia dependancies
declaration in order to build a magnolia-project?
If by project you mean webapp, then this example might help. Just note
that it's quite outdated, so don't copy it line-by-line ;)
http://svn.magnolia-cms.com/view/community/modules/magnolia-webapp-documentation/trunk/pom.xml?revision=19481&view=markup
If you mean a module, just have a look at any of the up-to-date
modules under http://svn.magnolia-cms.com/view/community/modules
Cheers,
-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>
----------------------------------------------------------------
