Just to clarify the building from source situation, the real requirement
is that if we were in a concrete bunker somewhere with no connection to
the outside world, and all we had was an installed fedora box + all the
source rpms for fedora, we should be able to rebuild the entire OS.
Note
Jason van Zyl wrote:
On 14 Dec 06, at 10:30 AM 14 Dec 06, Rafael Schloming wrote:
Just to clarify the building from source situation, the real
requirement is that if we were in a concrete bunker somewhere with no
connection to the outside world, and all we had was an installed
fedora box
Jason van Zyl wrote:
On 6 Dec 06, at 3:02 PM 6 Dec 06, Carl Trieloff wrote:
John Casey wrote:
Let's start with: What are the requirements?
Regards,
John
yes that is good - I would not see the patches set as something to
commit as is but a prototype to see if it could
be done. we now
Jason van Zyl wrote:
I don't remember a specific instance, but I'm sure there are some who
would like them. Either way, we need to consider Fedora as a consumer
of Maven and that they know what their users want, which apparently is
Maven bundled with Fedora.
I doubt they have asked but I
John Casey wrote:
2: Ensure that projects can build against a single version of a
dependency, rather than multiple.
This bothers me the most. If my project's pom.xml says I depend on foo
version 1.1.3, it better be built and installed with foo version
1.1.3,
not foo version 1.2 or foo
on the
burden of integration testing as soon as the depart from upstream build
procedures.
--Rafael
-john
On 12/6/06, Rafael Schloming [EMAIL PROTECTED] wrote:
John Casey wrote:
2: Ensure that projects can build against a single version of a
dependency, rather than multiple
Rafael Schloming wrote:
John Casey wrote:
All of this makes sense, until you consider that the user might start
using
the Fedora-provided version of Maven for his own software builds. Then
you
have a possibility of letting him produce a very messy build that doesn't
use artifact versions
