On 15/09/2006, at 12:34 AM, Emmanuel Venisse wrote:
Personally, I prefer the PULL method.
Agreed.
I think we need to have two type of analysis.
The first is for dependencies that have a corresponding project in
continuum.
The second is for other dependencies that are available in the rep
Personally, I prefer the PULL method.
I think we need to have two type of analysis.
The first is for dependencies that have a corresponding project in continuum.
The second is for other dependencies that are available in the repo.
For the first one, we need the lastKnownBuildId or just check if t
Hi,
I wanted to propose some solutions for triggering builds if dependencies are
changed.
(I mean: if project A depends on project B, and project B was updated/rebuilt,
then
A should also be rebuilt to check for any api breaking changes etc.).
From the top of my head I can name 2 distinct ap
Sending again, it doesn't seem to have made the list.
Original Message
Subject: Dependency triggered builds
Date: Thu, 14 Sep 2006 10:30:01 +0200
From: Kenney Westerhof <[EMAIL PROTECTED]>
To: continuum-dev@maven.apache.org
Hi,
I wanted to propose some so
