Hello Maven gurus,
Im quite new to Maven but I am now going to introduce it into a major
project (40+) and replace a recursive hierarchy of ant build files.....
Im a bit confused about a few central things and hope that one of you could
clarify it:
Our project consist of several feature teams each consisting of several
projects.
Some subprojects depend on other subprojects to be build and others on other
parent projects again.
I understand that the dependencies can be specified on jars that reside in
the repository...
My Questions are in short:
- How do I specify that one project must be build before another and thus
depend on it (without first placing a jar in the repository and creating a
dependency to it)?
- Can I in some way specify a dependency on a jar that if it doesn't exist
in the repository triggers a build of that jar instead of an attempted
download from the repository?
- What is considered a good setup for a project of this type (we need to do
local builds as well as nightly builds that tie it all together)?
Should it something like this?:
Project.xml (master build) - should specify dependencies etc.
Project.xml (<extends> master)
Maven.xml
Project.xml (<extends> master)
Maven.xml
- Is it "normal" to separate the use of a central global online repository
(for 3�rd party and stable releases) and the use of a local repository for
the daily developer builds?
Thank you for your patience with these newbe questions :)
Regards Jesper
(jesper at linvald dot net)
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.654 / Virus Database: 419 - Release Date: 06-04-2004
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
