Brett Porter wrote:
On 10/3/05, Miks Rozenbergs <[EMAIL PROTECTED]> wrote:
And now comes the question -- do I understand correctly that Maven would
not support such a model? That in Maven's case the dependant source
project should be added to <dependencies> AND ALSO ALL Module POM's
(IMHO I will need several Module POM's, as one DLL is used in multiple
components)? Which means someone should MANUALLY resolve dependencies!
[skiped...]
I think what you are assuming is that this is necessary so that you
can build all of the dependencies in your tree, giving them all a
common root. If you want to rebuild everything at once, this is true -
but that defeats the purpose of the Maven repository. You should only
need to rebuild the pieces of the system in development, and for those
you need to select the latest version in your dependencies anyway.
Rebuilding everything at once is not the main goal. What we were after
was a reliable way of rebuilding any software project (think POM) and
make sure that all dependent projects are rebuild as well (if changed).
Think of it as a graph of 200+ nodes and I need to be able to trigger a
build at any arbitrary node with 100% guaranty that any dependent nodes
will be rebuild using the latest from CVS TRUNK (or some branch or via a
tag).
For example there might be a DLL (let's say xxx.dll) which in it's turn
is dependent on 3 other DLL's. All of them are separate Visual Studio
projects. A bug is found and it's fix requires changes in xxx.dll and in
one of the dependent ones. So, we make those changes and I should be
able to do build of xxx.dll which should trigger builds of all 3
dependent projects, out of which only one will be rebuild, because
others hasn't changed.
How do I do that with Maven 2?
>
[skiped...]
I hope this clears it up.
Cheers,
Brett
Regards,
Miks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
