> ... since that bundle doesn’t declare anything optional in its Manifest
>
> Could it be that the report blames the wrong bundle?
>
http://build.eclipse.org/juno/simrel/reporeports/reports/greedyReport.html
>

I see now there is some confusion about what the report is showing. It is
not showing "blame" as most reports do.

It is Just showing bundles that are required ... by someone else ...
optionally but without greedy attribute.  So, yes, it is that "someone
else" that is to blame,
and is very hard to "track down". Manually or programmatically.

I wrote this "quick and easy" report as a sanity check that everyone was
moving to new publisher, and hoped we would not have to get to the point of
tracking down "blame".

If everyone had moved, and the report was "clean", we'd be done. with no
blame report needed. But, as it is ... sounds like a case of "you get what
you measure" ... so we need to measure "blame".

Sorry I didn't read your comments closely enough previously.

I'll see if I can improve the report some to keep track of "blame" ... not
sure I can easily, but, we'll see.







From:   "Oberhuber, Martin" <[email protected]>
To:     Cross project issues <[email protected]>,
Date:   05/24/2012 08:10 AM
Subject:        [cross-project-issues-dev] Simrel Greediness Report (was: Yet
            another nag note)
Sent by:        [email protected]



Hi David,

Given that I also found “219. org.eclipse.rse.services.ssh” in your
greediness report, I was confused (since that bundle doesn’t declare
anything optional in its Manifest).

Could it be that the report blames the wrong bundle?
http://build.eclipse.org/juno/simrel/reporeports/reports/greedyReport.html

I just performed an “unzip –p …/releases/staging/content.jar | less” and I
see that my 2 bundles are
“required optional with defaults” by org.eclipse.dltk.rse.core so I believe
that bundle is to blame in this case…

I am likely responsible for fixing the “7. Gnu.io” one which should
definitely be non-greedy especially given
that we don’t ship it from Eclipse (it’s a “works-with” pre-req).
Investigating now…

Martin


From: [email protected] [
mailto:[email protected]] On Behalf Of Dennis
Hübner
Sent: Thursday, May 24, 2012 9:19 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Yet another nag note ... and, I
mean it this time!

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
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

<<inline: graycol.gif>>

_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to