Yes, that is what I'm looking for I think. I will give it a go in the coming week.
On Sat, Dec 27, 2008 at 1:36 AM, Maarten Storm <mtst...@gmail.com> wrote: > Yes I can add the dependencies using import (did not know that this > was a scope...) and no, that is not possible since all the parent > poms are poms that have packaging pom, maven does not except these. I > try to fool Maven by adding a empty jar per pom and that worked, but > thats not the good way (fooling the tool ). I will keep import in > mind. > > On Sat, Dec 27, 2008 at 1:20 AM, Brian E. Fox <bri...@reply.infinity.nu> > wrote: >> Can't you achieve this using the import scope? This would allow you to >> declare the dependencyManagement of all your jars in one pom and effectively >> import that into the projects that need it, thus synchronizing the >> dependencies across them all. >> >> >> On 12/26/08 7:11 PM, "Maarten Storm" <mtst...@gmail.com> wrote: >> >>> Hello, >>> The reason why I would like to add dependencies programmaticaly is the >>> following: In my open source project I have 3 subprojects that do not >>> share the same parent pom. I'm working on a new packaging strategy >>> called dpom. This Dependency Pom is just like a normal pom but it >>> synchronized project links in the site.xml of the 3 subprojects. This >>> allows me to make a overall site for projects that do not share the >>> same parent pom. >>> >>> I'm working now at a company that has the same problem that I have >>> within my open source project. They have about 15 huge projects (over >>> 20 man years per project) and the would like to monitor the >>> dependencies over all these project without interfering them (share >>> the same parent). The idea behind this is that ew can make a list in >>> the configuration for all the parent projects and generating an >>> overlal website. The dependency report will give all the transitive >>> dependencies of all the projects so the can monitor that. I am working >>> a a specialized dependency tree that will make a cross references >>> where the dependencies are used. >>> >>> So the steps I would like to program are: >>> >>> 1: Read the every pom in the list of the configuration form a repository. >>> 2: Analyze every pom for dependencies. >>> 3: Add these new found dependencies to the dpom project ( and remember >>> where it's origine (dpom report)). >>> >>> I hope this helps. The DPOM packaging is not used for normal maven >>> this like jar/ear/war etc., it is only meant for site generation. >>> I hope you can help me with step 2 en 3. >>> >>> Kind regards, >>> Maarten Storm >>> >>> On Fri, Dec 26, 2008 at 8:31 PM, Jason van Zyl <jvan...@sonatype.com> wrote: >>>> From the Maven 1.x days where we did this and realized that if the model of >>>> your dependencies not explicit in your pom.xml file then it's not clear to >>>> anyone where dependencies are coming from and leads to problems. >>>> >>>> On 24-Dec-08, at 6:53 PM, Maarten Storm wrote: >>>> >>>>> Hello all, >>>>> I would like to add programmatically dependencies to the MavenProject. >>>>> I have looked in the mail archives but I could not find info on this >>>>> topic.Is there a possible solution for this? >>>>> >>>>> Kind regards, >>>>> Maarten Storm >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>>>> For additional commands, e-mail: dev-h...@maven.apache.org >>>>> >>>> >>>> Thanks, >>>> >>>> Jason >>>> >>>> ---------------------------------------------------------- >>>> Jason van Zyl >>>> Founder, Apache Maven >>>> jason at sonatype dot com >>>> ---------------------------------------------------------- >>>> >>>> We all have problems. How we deal with them is a measure of our worth. >>>> >>>> -- Unknown >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>>> For additional commands, e-mail: dev-h...@maven.apache.org >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
