On 4/2/07, smu <[EMAIL PROTECTED]> wrote:
Hi, Thanks for this idea. I just did this way - declared common libraries in one modulies and made all other modules dependant on it. Also what I did - almost all external dependencies I declared with transtive=false. Otherwise you will receive huge bunch of unnecessary jars.
If you're using maven2 compatibility, you may get a 'huge bunch of unnecessary jars' because of your configuration mapping. See this recent thread: http://www.nabble.com/ibiblio-resolver-and-optional-pom-dependencies-tf3497317.html BTW ibiblio resolver is not currect (maven2) - it doesn't undestand
'project.name' properties - you have to correct them yourself.
This seems to be a bug. Could you give more details (like pointing to a pom using project.name, or pointing to a maven doc page explaining how we should resolve project.name? Indeed we already fixed some properties: https://issues.apache.org/jira/browse/IVY-425 Thanks for your feedback! - Xavier Bye,
Saulius Xavier Hanin wrote: > > On 3/27/07, smu <[EMAIL PROTECTED]> wrote: >> >> >> Hi, >> >> I'm trying to migrate to ivy from maven and have one question. Is it >> possible to create some common dependencies for multimodule project? >> Something like parent and child pom.xml in maven2. For example, I'm using >> Spring in almost all modules but don't want to declare it in every module >> (as in case of version change I will have to update all ivy.xml files). >> Is >> it possible to do with ivy? > > > Ivy do not support parent/child like maven, but you can do something very > similar by using virtual module. A virtual module is a module which > publishes no artifact at all (put an empty publication section in its ivy > file, since no publication element at all is equivalent to publishing one > jar artifact). > > Then when you declare a dependency on it, you will transitively get all > its > dependencies, and only its dependencies since it doesn't publish any > artifact. > The advantage is that you can obviously declare multiple dependencies like > that, so you are not limited to single level inheritance of maven > parent/child mechanism. > > HTH, > > - Xavier > > Thanks, >> Saulius >> -- >> View this message in context: >> http://www.nabble.com/Common-dependencies-tf3473658.html#a9694201 >> Sent from the ivy-user mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Common-dependencies-tf3473658.html#a9797003 Sent from the ivy-user mailing list archive at Nabble.com.
-- Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ Manage your dependencies with Ivy! http://incubator.apache.org/ivy/
