> it often just intended by projects So, you think its right as it is? Great!
But, 83 with contradictory settings. That's probably not correct, right? Or
do you think that's intended? Do you think that would work? I think that's
going to lead to "undefined" behavior and hard to predict what gets
installed and what doesn't.
712 with implicit greedy=true (i.e. does not specify a value for greedy). I
was under the impression that the new publishers always were explicit,
either true or false. Is that not right? Perhaps I am wrong and everyone is
using the new publishers. If so, great, and perhaps only the
"contradictory" settings need attention? Great. Still, those that use the
83 bundles on the contradictory list should work things out with who ever
else is using/setting the values so there's only one setting, AFAIK.
If everyone is using the new publishers, then I'd still like to understand
why such vast numbers decided to use greedy=true (implicitly). I was under
the impression its use would be pretty rare. After all, it's optional at
run time, it may or may not be in a repository. Users or adopters may or
may not want the optional thing installed, so why tie "optional runtime
dependency" to install behavior, and to the repository a user just happens
to use?
I did not mean to say they were ALL wrong. But, if I had to guess, I'd say
there would be 6 or 20 "valid" cases. Sounds like you have some knowledge
that hundreds is the right amount? Are there cases where your project(s)
decided to use it?
Thanks in advance for educating me. I appreciate the discussion and
corrections to my understanding (and, to the general knowledge of
"cross-project" readers).
Thanks,
From: Dennis Hübner <dennis.hueb...@itemis.de>
To: Cross project issues <cross-project-issues-dev@eclipse.org>,
Date: 05/24/2012 03:19 AM
Subject: Re: [cross-project-issues-dev] Yet another nag note ... and,
I mean it this time!
Sent by: cross-project-issues-dev-boun...@eclipse.org
Hi David,
Still scores of projects that have not bothered to move to a current
repo publisher so there are hundreds of incorrect "greediness"
attributes.
Sure there are greedy optional dependencies in the repository, because it
often just intended by projects. I don't understand, why are you talking
about incorrect greediness? "Not a default" it not the same as "wrong".
IMHO this [1] report is only useful for statistic purpose.
Regards,
Dennis Hübner
[1]
http://build.eclipse.org/juno/simrel/reporeports/reports/greedyReport.html
Xtext Commiter / Build Engineer
Mobile: +49 (0) 151 / 17396687
Telefon: +49 (0) 431 / 99026870
Fax: +49 (0) 431 / 99026872
itemis AG
Niederlassung Kiel
Am Germaniahafen 1
24143 Kiel
http://www.itemis.de/
Rechtlicher Hinweis:
Amtsgericht Dortmund, HRB 20621
Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens
Trompeter, Sebastian Neus
Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus
Am 24.05.2012 um 06:40 schrieb David M Williams:
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
<<inline: graycol.gif>>
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
