Hi Marcel,
just saw your second mail:
Side note 1: I don't get exactly what you like to see, lets talk
about this tomorrow on the phone? (To not spam the list)
Side note 2: See my last mail, this is actually already implemented
and worked great so far.
However, it seems like you just discovered a bug, I checked the
o.e.swt packages and the package level statistics doesn't appear
(although they're clearly statistics for these packages), like any
of the javadoc html output for this package.
I'll have to take a closer look into this.
BTW, I'm very happy with your idea to javadoc the juno-sr2 repo.
A whole new set of (not yet thought of) problems and ideas came to
me :)
Best regards
Patrick
I just looked at swt.widgets.button:
Looks nice!
Side note 1: If the recommender has the information how many
sublasses were used to create the statistics, it would be great
to see this too :) Can you add this to your generator?
Side note 2: Can you create a summary for the package view
too? I.e, when I click on the packge in the browser, I'd be glad
to see for which classes in the package overrides
recommendations are made. In o.e.swt.widgets, for instance, it
would tell me that it has data for Button, Composite, Text etc..
Does this sound useful for you too?
Thanks,
Marcel
Hi,
here is my update for this week:
What I have done this week:
- Write a blogpost about loading third party jars in osgi
enviroments
- Finish the "ovrm" + "ovrp" list view
- javadoc the juno-sr2 repo with models from code
recommenders
- filter option for taglets on cli
- groupId leveled directory hierarchy output
- some refactorings in the Taglet Interfaces / abstract
classes
- ordering taglets in the html output
The javadoc'ed juno-sr2 repository is finished and atm on
our mining server in the Codetrails office, under /home/share/juno-sr2.
Its about 3GB big, so we'll have to upload it somehow to
the internet, if you want to. I'll call for that tomorrow.
Unfortunately, some 'sources' artifacts in the mvn2 repo
were corrupt (they actually had no sources packed), these
are listed under juno-sr2/logs.
Don't get irritated by the error message, which comes from
a bad exception handling for the moment.
What I have planned for the next (2) weeks:
So, this depends. If we want to mine further (big) mvn
repositories at once, I'll suggest the following:
- Insert a option to mine whole mvn repositorys (this is
done via a batch file with aether coordinates at the
moment)
- Finally care about the logging, you'll probably want to
know what gone wrong during the javadoc'ing of big
repositories
- Proper exception handling
Unfortunately, I can't work that much for GSOC in the next
2 weeks, I'm writing two exames.
I also won't be at the office on wednesday because of
this.
Best regards
Patrick
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/recommenders-dev
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/recommenders-dev
|
