Bryan Kearney wrote:
Aidan Skinner wrote:
On Wed, Jun 24, 2009 at 3:59 PM, Bryan Kearney<[email protected]>
wrote:
The main issue is that for dep resolution it still needs something
looks like a maven repo, not like /usr/java. I think a new resolver
wouldn't be very hard to write, but I haven't found the cycles for it
yet.
Why is it bad to use the maven repos instead of copying things from
java/lib?
It makes reproducible builds hard/impossible and doesn't play well
with package systems.
I have not seen the former issue.. but I will trust you on it. On the
latter (package systems) using maven repos seems no worse then what is
being done now.
The issue with using maven repos is that if you happen to use svn to
rollback to a version where we were using maven, the build will most
likely fail because it is dependent on a set of external maven repos
that are no longer in sync with the needs of that particular revision.
The nice thing about the way it is now, is that I can do an svn update
-r<foo> and rollback to any given version with the current build system
and be fairly certain that the build will function because the only
dependency stored outside of svn is ant, and that has a fairly small and
stable footprint.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
