Consistently getting "seems up to date" without processing.

SIRA_PRISE — Mon, 04 May 2020 11:55:48 -0000

Forget it. Was looking at the wrong config file. Sorry !

Consistently getting "seems up to date" without processing.

SIRA_PRISE — Mon, 04 May 2020 11:51:08 -0000

I'm using a very basic configuration :

-forceprocessing
-verbose
-dontshrink
-dontoptimize
-basedirectory ...
-injars TEST/bin/tmpserver.jar
-outjars ACPT/bin/sp.server.jar
-libraryjars ...
... keepcommands here

The injar exists, the outjar doesn't. Even despite the -forceprocessing option, I consistently get "output seems up to date" and outjar doesn't get created. What am I doing wrong ? (Oh yes, I'm working via the Ant task.)

Proguard removing square brackets in string

doomstone123 — Thu, 23 Apr 2020 12:41:30 -0000

Proguard in changing the varaible definiton in interal library don't know why code is breaking because of it.

**Before obfuscator**

private static final Signature GET_DECLARED_METHODS = TypeUtils.parseSignature("java.lang.reflect.Method[] getDeclaredMethods()");

**After obfuscator**

private static final Signature GET_DECLARED_METHODS = TypeUtils.parseSignature("java.lang.reflect.Method");

Proguard + Spring Batch | Application context not getting loaded

doomstone123 — Sat, 18 Apr 2020 17:54:21 -0000

Not sure why i am getting the below exception. This is happenning during spring application context is getting loaded. Running proguard over the executable jar.

Exception in thread "main" java.lang.ExceptionInInitializerError
at org.springframework.cglib.proxy.CallbackInfo.<clinit>(CallbackInfo.java:60)
at org.springframework.cglib.proxy.Enhancer.setCallbackTypes(Enhancer.java:372)
at org.springframework.context.annotation.ConfigurationClassEnhancer.newEnhancer(ConfigurationClassEnhancer.java:128)
at org.springframework.context.annotation.ConfigurationClassEnhancer.enhance(ConfigurationClassEnhancer.java:109)
at org.springframework.context.annotation.ConfigurationClassPostProcessor.enhanceConfigurationClasses(ConfigurationClassPostProcessor.java:429)
at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanFactory(ConfigurationClassPostProcessor.java:263)
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:286)
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:130)
at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:706)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:532)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(Unknown Source)
at org.springframework.cglib.core.TypeUtils.parseSignature(TypeUtils.java:171)
at org.springframework.cglib.proxy.MethodInterceptorGenerator.<clinit>(MethodInterceptorGenerator.java:44)
... 11 more</clinit></clinit>

Proguard Configuration
<options> <option>-dontnote</option> <option>-dontwarn</option> <option>-dontshrink</option> <option>-dontoptimize</option> <option>-adaptclassstrings</option> <option>-keepdirectories</option> <option>-keepattributes Exceptions, InnerClasses, Signature, Deprecated, SourceFile, LineNumberTable, *Annotation*, EnclosingMethod </option> <option>-keepnames interface **</option> <option>-keep interface ** </option> <option>-keeppackagenames</option> <option>-keepparameternames</option> <option>-ignorewarnings</option> <option>-keep interface * extends * { *; }</option> <option>-keepclassmembers class * { @org.springframework.beans.factory.annotation.Autowired *; @org.springframework.beans.factory.annotation.Value *; @org.springframework.context.annotation.Bean *; @org.springframework.beans.factory.annotation.Qualifier *; @org.springframework.context.annotation.ComponentScan *; @org.springframework.stereotype.Repository *; @org.springframework.data.repository.NoRepositoryBean *; @org.springframework.context.annotation.Configuration *; @org.springframework.stereotype.Component *; @org.springframework.batch.core.configuration.annotation.EnableBatchProcessing *; } </option> <option>-keepclassmembers enum * { *; }</option> <option>-keep class * implements java.io.Serializable</option> <option>-keep class ch.qos.logback.** { *; }</option> <option>-keep class org.slf4j.** { *; }</option> <option>-keep class org.springframework.** { *; }</option> <option>-keep class com.google.** { *; }</option> <option>-keep class org.apache.** { *; }</option> <option>-keepclassmembers class * { void finalizeReferent(); }</option> <option>-keepclassmembers enum * { public static **[] values(); public static ** valueOf(java.lang.String); }</option> </options>

General Questions

Eric Lafortune — Mon, 06 Apr 2020 20:14:29 -0000

You should specify the output jar in the "Input/Output" tab > "Add output..."

ProGuard doesn't obfuscate the runtime jar rt.jar, but it does need it as a library jar to process your program jar correctly.

Identify obfuscated stacktraces

Eric Lafortune — Mon, 06 Apr 2020 20:08:17 -0000

You generally can't know for sure.

ProGuard by default uses names a, b, c,... for classes, fields and methods, but a developer can specify his or her own dictionaries.
In the ProGuard examples, the source file name in a stack trace is set to "SourceFile" and many developers adopt that as well.

Identify obfuscated stacktraces

Disha Shrinath Shetty — Fri, 20 Mar 2020 17:02:46 -0000

Could someone help me out with how can I identify using code if a stacktrace is obfuscated using Proguard or not?

Optimized Classes/Objects cleaned up after GC

T. Neidhart — Wed, 18 Dec 2019 12:18:02 -0000

This optimization has been fixed in the sense that write-only instance field where not removed anymore which was clearly a bug. Do you maybe have some weak / soft references to avoid some data from being garbage collected until its really needed?

If that is the case you probably should keep these fields explicitly like that:

-keepclassmembers,allowshrinking,allowobfuscation class {
java.lang.ref.WeakReferences ;
java.lang.ref.SoftReference ;
}

That will disable optimization for fields that have this type.

Optimized Classes/Objects cleaned up after GC

T. Neidhart — Tue, 17 Dec 2019 10:00:58 -0000

In order to disable this specific optimization you can add

-optimizations !field/removal/writeonly

if this is not the cause, you could add a keep rule like that to prevent optimization on the affected classes:

-keep,includecode class xxx { *; }

where xxx refers to the fully qualified classname.

Optimized Classes/Objects cleaned up after GC

T. Neidhart — Tue, 17 Dec 2019 07:16:01 -0000

Could you create a ticket at the github project and attach possibly the relevant class files when processed with 6.1.1 and 6.2.x? We have made some changes wrt write-only fields, I wonder if this might be responsible.

Recent posts to Discussion

Consistently getting "seems up to date" without processing.

Consistently getting "seems up to date" without processing.

Proguard removing square brackets in string

Proguard + Spring Batch | Application context not getting loaded

General Questions

Identify obfuscated stacktraces

Identify obfuscated stacktraces

Optimized Classes/Objects cleaned up after GC

Optimized Classes/Objects cleaned up after GC

Optimized Classes/Objects cleaned up after GC