0 classes found and parsed via Javaassist in 23ms

[dmc1778]

Hi,

I would be grateful if you help me to fix the following issue.

Every time I try to run Jpeek over my targeted source files, it executes and prints the following in the command line.

0 classes found and parsed via Javassist in 23ms 0 classes parsed via ASM in 114ms No classes parsed in 589ms Constructors will be ignored Static methods will be ignored Private methods will be ignored NHD.xml generated in 443ms MMAC.xml generated in 481ms CAMC.xml generated in 512ms LCOM5.xml generated in 548ms SCOM.xml generated in 598ms 5 XML reports created Matrix generated

Thanks.

[0crat]

@paulodamaso/z please, pay attention to this issue

[0crat]

@nimashiri/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

[dmc1778]

I really want to help you to maintain this awesome project, but, I live in IRAN and I can't pay via Stripe, Pay Pal, VISA, MASTERCARD, and etc.

Thanks, Nima.

On Tue, Feb 25, 2020 at 10:08 PM Zerocrat notifications@github.com wrote:

@nimashiri https://github.com/nimashiri/z https://www.0crat.com/u/nimashiri this project will fix the problem faster if you donate a few dollars to it; just click here https://www.0crat.com/contrib/C7JGJ00DP and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/yegor256/jpeek/issues/395?email_source=notifications&email_token=AECFFZIGZ64L5VSMH5WWTG3REVQQRA5CNFSM4K3PWPXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM472YY#issuecomment-591002979, or unsubscribe https://github.com/notifications/unsubscribe-auth/AECFFZK6MWV5VN77PXYZVN3REVQQRANCNFSM4K3PWPXA .

[paulodamaso]

@0crat in

[0crat]

@0crat in (here)

@paulodamaso Thanks for your contribution, @nimashiri/z! If you would be a member of the project, you would now earn +15 reputation points, as explained in §29. You can join and apply to it, see §2.

[0crat]

The job #395 assigned to @volodymyrbondarchuk/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

[0crat]

@volodymyrbondarchuk/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

[0crat]

The user @volodymyrbondarchuk/z resigned from #395, please stop working. Reason for job resignation: It is older than 10 days, see §8

[0crat]

Job gh:yegor256/jpeek#395 is not assigned, can't get performer

[0crat]

The job #395 assigned to @fanifieiev/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

[fanifieiev]

@nimashiri Could you show me you the command line you run against your sources??? When you specify --sources or -s parameter, are you pointing to *.java or *.class files???

[dmc1778]

Thanks for your reply. I was mistakenly pointing to source code files, then I figured out that I should point to byte-code files.

On Wed, Mar 25, 2020 at 9:51 AM Fevzi Anifieiev notifications@github.com wrote:

@nimashiri https://github.com/nimashiri Could you show me you the command line you run against your sources??? When you specify --sources or -s parameter, are you pointing to .java or .class files???

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/yegor256/jpeek/issues/395#issuecomment-603646638, or unsubscribe https://github.com/notifications/unsubscribe-auth/AECFFZPT5SKGBZFEL5K5WWDRJGIGFANCNFSM4K3PWPXA .

[fanifieiev]

Thanks for your reply. I was mistakenly pointing to source code files, then I figured out that I should point to byte-code files. … On Wed, Mar 25, 2020 at 9:51 AM Fevzi Anifieiev @.**> wrote: @nimashiri https://github.com/nimashiri Could you show me you the command line you run against your sources??? When you specify --sources or -s parameter, are you pointing to .java or *.class files??? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#395 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AECFFZPT5SKGBZFEL5K5WWDRJGIGFANCNFSM4K3PWPXA .

@nimashiri Please close this issue, if it that is not a problem anymore.

[0crat]

@sereshqua/z please review this job completed by @fanifieiev/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

[sereshqua]

@0crat quality bad

[0crat]

Quality is low, no payment, see §31

[fanifieiev]

@sereshqua Can you please explain why the quality is bad for that kind of issue??? The issue was that the user did not use JPeek properly. I asked some questions and the user found out he did not use it properly. What should be else done in such issues????

[sereshqua]

@fanifieiev you did everything correctly to help the user :)

the only thing here is that there was no job and no solution to the job, just the communication

the way how i treat the policy: solution is the solution only related to the code, so i think this job should NOT have gone to the scope before clarification

[sereshqua]

@paulodamaso WDYT about situation above?

[fanifieiev]

@fanifieiev you did everything correctly to help the user :)

the only thing here is that there was no job and no solution to the job, just the communication

the way how i treat the policy: solution is the solution only related to the code, so i think this job should NOT have gone to the scope before clarification

@sereshqua I think we need to treat such issues as jobs as well, sometimes without code changes. There are a lot of other projects on github where people solve issues by the way of communication only.

[sereshqua]

@fanifieiev yeah it can go this way, or architect would not be putting scope label to avoid other people involvement and solve this issue by communication with issue creator