From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110121/002286.html | 74 +++++++++++++++++++++++++++++++++ 1 file changed, 74 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110121/002286.html (limited to 'zarb-ml/mageia-dev/20110121/002286.html') diff --git a/zarb-ml/mageia-dev/20110121/002286.html b/zarb-ml/mageia-dev/20110121/002286.html new file mode 100644 index 000000000..724b6011b --- /dev/null +++ b/zarb-ml/mageia-dev/20110121/002286.html @@ -0,0 +1,74 @@ + + + + [Mageia-dev] Java-Policy first draft published + + + + + + + + + +

[Mageia-dev] Java-Policy first draft published

+ Frank Griffin + ftg at roadrunner.com +
+ Fri Jan 21 14:22:26 CET 2011 +

+
+ +
nicolas vigier wrote:
+>
+> Nothing should be downloaded from remote maven repositories during RPM
+> builds. All dependencies should be installed from rpm packages only.
+>
+>
+>   
+So you propose that we package every version of every maven plugin and
+dependency as RPMs and basically reinvent the entire Maven artifact
+architecture ?
+
+It's not a question of "use the most current or fix it".  POMs allow the
+author to specify the version of the artifact, and it doesn't matter
+whether it would work with a later version or not, because Maven will be
+no more tolerant of a version mismatch than RPM would be.  It simply
+won't build unless you rewrite the POM, in which case you can kiss
+upstream support goodbye.
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1