Mined Opinions For API: proguard

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • The funny thing is that -overloadaggressively is one of the recommended options in various Proguard examples for setting up GSON.. details
  • Proguard is renaming multiple members to the same name 'a', which is perfectly valid in classfiles.. details
  • There's probably also a Proguard setting to avoid duplicate names, but I'm not familiar enough to say what it is.. details
  • That avoids any name clashes as well.. details
  • Here is the section of the obfuscation map relevant to one of the nearly identical errors.. details
  • I don't see the problem.. details
  • Unless I'm being misled, the errors are like: class Property declares multiple JSON fields named a and same for class PropertyDefinition.. details
  • Without obfuscation there are no errors.. details
  • Upon starting up my app logs two errors, but only after obfuscation.. details
  • One thing to watch out for: After exporting my app and testing I ran into problems due to Proguard and GSON.. details
  • One thing to watch out for: After exporting my app and testing I ran into problems due to Proguard and GSON.. details
Summaries the opinions about proguard using topic modeling.
  • 0. duplicate setting multiple valid member rename thing option familiar overloadaggressively: 3
    • The funny thing is that -overloadaggressively is one of the recommended options in various Proguard examples for setting up GSON.. details
    • Proguard is renaming multiple members to the same name 'a', which is perfectly valid in classfiles.. details
    • There's probably also a Proguard setting to avoid duplicate names, but I'm not familiar enough to say what it is.. details
  • 0. obfuscation propertydefinition multiple export testing thing watch avoid declare relevant: 7
    • That avoids any name clashes as well.. details
    • Unless I'm being misled, the errors are like: class Property declares multiple JSON fields named a and same for class PropertyDefinition.. details
    • I don't see the problem.. details
    • Here is the section of the obfuscation map relevant to one of the nearly identical errors.. details
    • Upon starting up my app logs two errors, but only after obfuscation.. details
    • Without obfuscation there are no errors.. details
    • One thing to watch out for: After exporting my app and testing I ran into problems due to Proguard and GSON.. details
Summaries of the opinions about proguard using three algorithms (Textrank, Lexrank and Luhn) adopted from extractive summarization. Each algorithm was used once for the positive opinions and once for the negative opinions.
  • The funny thing is that overloadaggressively is one of the recommended options in various Proguard examples for setting up GSON .
  • Proguard is renaming multiple members to the same name 'a', which is perfectly valid in classfiles .
  • There's probably also a Proguard setting to avoid duplicate names, but I'm not familiar enough to say what it is .
  • The funny thing is that overloadaggressively is one of the recommended options in various Proguard examples for setting up GSON .
  • Proguard is renaming multiple members to the same name 'a', which is perfectly valid in classfiles .
  • There's probably also a Proguard setting to avoid duplicate names, but I'm not familiar enough to say what it is .
  • The funny thing is that overloadaggressively is one of the recommended options in various Proguard examples for setting up GSON .
  • Proguard is renaming multiple members to the same name 'a', which is perfectly valid in classfiles .
  • There's probably also a Proguard setting to avoid duplicate names, but I'm not familiar enough to say what it is .
  • One thing to watch out for: After exporting my app and testing I ran into problems due to Proguard and GSON .
  • Upon starting up my app logs two errors, but only after obfuscation .
  • Without obfuscation there are no errors .
  • Unless I'm being misled, the errors are like: class Property declares multiple JSON fields named a and same for class PropertyDefinition .
  • Here is the section of the obfuscation map relevant to one of the nearly identical errors .
  • I don't see the problem .
  • That avoids any name clashes as well .
  • One thing to watch out for: After exporting my app and testing I ran into problems due to Proguard and GSON .
  • Upon starting up my app logs two errors, but only after obfuscation .
  • Without obfuscation there are no errors .
  • Unless I'm being misled, the errors are like: class Property declares multiple JSON fields named a and same for class PropertyDefinition .
  • Here is the section of the obfuscation map relevant to one of the nearly identical errors .
  • I don't see the problem .
  • That avoids any name clashes as well .
  • One thing to watch out for: After exporting my app and testing I ran into problems due to Proguard and GSON .
  • Upon starting up my app logs two errors, but only after obfuscation .
  • Without obfuscation there are no errors .
  • Unless I'm being misled, the errors are like: class Property declares multiple JSON fields named a and same for class PropertyDefinition .
  • Here is the section of the obfuscation map relevant to one of the nearly identical errors .
  • I don't see the problem .
  • That avoids any name clashes as well .
Summaries of the opinions about proguard using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about proguard using contrastive viewpoints. Each entry contains a pair of positive and negative sentences that are most likely discussing about similar API features.
Summaries of opinions about based on specific API aspects, such as, performance, usability, etc. The 'Overview' page provides an overview of the aspects detected in the opinions. The 'Trend' page shows the distribution of polarity over time for each aspect. The 'Positive Opinions' page groups positive opinions by the detected aspects. The 'Contrastive By Aspect' page shows paris of contrastive opinions under each aspect (where found).
Performance:
  • N/A
  • One thing to watch out for: After exporting my app and testing I ran into problems due to Proguard and GSON.
Usability:
  • The funny thing is that -overloadaggressively is one of the recommended options in various Proguard examples for setting up GSON.
  • That avoids any name clashes as well.
Features:
  • Proguard is renaming multiple members to the same name 'a', which is perfectly valid in classfiles.
  • N/A
Bug:
  • N/A
  • Here is the section of the obfuscation map relevant to one of the nearly identical errors.
  • Features: 1
    1. general: 1
      • Proguard is renaming multiple members to the same name 'a', which is perfectly valid in classfiles.. details
  • Usability: 2
    1. general: 2
      • The funny thing is that -overloadaggressively is one of the recommended options in various Proguard examples for setting up GSON.. details
      • There's probably also a Proguard setting to avoid duplicate names, but I'm not familiar enough to say what it is.. details
  • Performance: 1
    1. general: 1
      • One thing to watch out for: After exporting my app and testing I ran into problems due to Proguard and GSON.. details
  • Bug: 3
    1. general: 3
      • Here is the section of the obfuscation map relevant to one of the nearly identical errors.. details
      • I don't see the problem.. details
      • Without obfuscation there are no errors.. details
  • Usability: 4
    1. general: 4
      • That avoids any name clashes as well.. details
      • Unless I'm being misled, the errors are like: class Property declares multiple JSON fields named a and same for class PropertyDefinition.. details
      • Upon starting up my app logs two errors, but only after obfuscation.. details
      • One thing to watch out for: After exporting my app and testing I ran into problems due to Proguard and GSON.. details