diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110112/002099.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110112/002099.html | 82 |
1 files changed, 82 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110112/002099.html b/zarb-ml/mageia-dev/20110112/002099.html new file mode 100644 index 000000000..7c2401d64 --- /dev/null +++ b/zarb-ml/mageia-dev/20110112/002099.html @@ -0,0 +1,82 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Java-Policy first draft published + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Java-Policy%20first%20draft%20published&In-Reply-To=%3C4D2E3138.7020207%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002097.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Java-Policy first draft published</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Java-Policy%20first%20draft%20published&In-Reply-To=%3C4D2E3138.7020207%40roadrunner.com%3E" + TITLE="[Mageia-dev] Java-Policy first draft published">ftg at roadrunner.com + </A><BR> + <I>Wed Jan 12 23:54:48 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002097.html">[Mageia-dev] Java-Policy first draft published +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#2099">[ date ]</a> + <a href="thread.html#2099">[ thread ]</a> + <a href="subject.html#2099">[ subject ]</a> + <a href="author.html#2099">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Renaud MICHEL wrote: +><i> +</I>><i> Or maybe, if the jar in the external dependency plugin is actually the same +</I>><i> (or compatible) version as the on from the normal package maybe we could +</I>><i> make a plugin package only containing the eclipse related files +</I>><i> (plugin.properties) and creating a symlink to the system wide jar. But that +</I>><i> mean that eclipse plugins, which are now frequently provided as single jar +</I>><i> files, would need to be packaged as files and directories like in older +</I>><i> eclipse releases. +</I>><i> +</I>><i> What do you think? +</I>><i> +</I>><i> +</I>I think we want to consider carefully before we try to replace complex +existing plugin installation procedures in various products. This issue +is also being discussed relative to Firefox in another thread. + +Users of things like NetBeans and Eclipse are used to the mechanisms +provided by those tools for managing plugin installation, and are not +going to take kindly to having to use rpmdrake instead. And in some +cases, e.g. Maven, you don't have a choice - if Maven needs it and it +isn't there, it will get it from repositories whether or not you have +packaged a plugin as an RPM. + +At some point, you just give up and accept the fact that you can't +reform the entire world. As more and more projects migrate to Maven, +the problem (sort of) goes away. All of our suggestions here are +basically trying to recreate what Maven does without requiring projects +to use it. +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002097.html">[Mageia-dev] Java-Policy first draft published +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#2099">[ date ]</a> + <a href="thread.html#2099">[ thread ]</a> + <a href="subject.html#2099">[ subject ]</a> + <a href="author.html#2099">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |