All Versions
37
Latest Version
Avg Release Cycle
202 days
Latest Release
-
Changelog History
Page 3
Changelog History
Page 3
-
v2.2.0 Changes
April 26, 2007โ Added
- yGuard is now fully JDK-1.6 compatible.
- ๐ The yGuard task now supports a way of specifying a set of jars that should be obfuscated at the same time using simple patternset syntax.
- yGuard now uses the same technique for all elements in the MANIFEST file to adjust fully qualified class name strings.
- ๐ฆ It is now possible to tell yGuard not to obfuscate specific package names.
- yGuard can now be given a list of digest algorithms that will be used to create the digests in the manifest.
- ๐ฆ yGuard now issues a warning if the package or class or method name of a native method is obfuscated.
-
v2.1.0 Changes
October 12, 2006โ Added
- โ Added
overloadEnabled
property
๐ Fixed
- ๐ Fixed a bug that caused yGuard to throw a
NullPointerException
if aattribute
element contained no nestedpatternset
. - ๐ Fixed a bug that caused yGuard to use multiple logging instances if a yGuard task was executed multiple times.
- ๐ Fixed LineNumberTable and SourceFile elements
- โ Added
-
v2.0.3 Changes
August 09, 2006- ๐ Fixed a bug that broke the nested
map
element of therename
element.
- ๐ Fixed a bug that broke the nested
-
v2.0.2 Changes
July 31, 2006๐ Fixed
- ๐ Fixed a bug that caused yGuard to fail during class file parsing if a method signature contained an inner class of a parameterized class.
- yGuard will not complain about the Java 1.5 attributes
Bridge
,Enum
andVarargs
as "unknown attributes" anymore. - ๐ Fixed a bug that caused all classnames to be kept from renaming if the
extends
attribute was used in combination with theclasses
attribute.
-
v2.0.1 Changes
July 12, 2006๐ Fixed
- ๐ Fixed an inconsistency between the interpretation of the Ant syntax in the
rename
andshrink
elements. Now, both elements applypatternset
elements in nestedmethod
andfield
elements to class names, just as stated in the yGuard documentation.
๐ Changed
- If the
classes
attribute of theclass
element is not set or set to "none", the shrinking engine will now include the classes that match based on the givenname
attribute or nestedpatternset
, effectively ignoring the classes attribute.
- ๐ Fixed an inconsistency between the interpretation of the Ant syntax in the
-
v2.0 Changes
June 22, 2006โ Added
- ๐ New elaborate code shrinking functionality.
- More powerful ant syntax:
extends/implements
attributes for theclass
element. - yGuard now needs Java2 SDK 1.4.x or greater to function properly.
๐ Changed
- General Ant syntax changes due to the introduction of the new
yguard
,shrink
andrename
elements.
-
v1.5 Changes
May 19, 2005โ Added
- โ Added JDK 1.5 (a.k.a Java 5.0 code-named Tiger) compatibility. yGuard can now deal correctly with the new JDK and Java features: generics, var-args, enumerations, annotations, new
.class
bytecode construct, signatures, local variable type table, enclosing method information. - Implemented the ability to obfuscate/scramble/shrink line number information. This makes it possible to more easily debug stacktraces without exposing line number information in the obfuscated version of the application.
- Implemented the ability to obfuscate the source file information. This is necessary in order to view line number information in stack traces. It is now possible to reassign the source file attribute inside class files so that the original source file name is not exposed in the obfuscated application.
- โ Added the ability to determine on a per-class basis what attributes to expose or obfuscate. This includes line number information (with optional scrambling/compression or removal), source file attributes, deprecation attributes, etc. This makes it easy to obfuscate parts of your application while keeping the public API untouched and debug information for third party jars intact.
- ๐ Improved the stacktrace deobfuscation tool. It can now unscramble line number information from stacktraces, features a more polished view of the mapping rules and deobfuscates stacktraces more reliably if the stacktraces are ambiguous.
- โ Added JDK 1.5 (a.k.a Java 5.0 code-named Tiger) compatibility. yGuard can now deal correctly with the new JDK and Java features: generics, var-args, enumerations, annotations, new
-
v1.5.0._03 Changes
๐ Fixed
- ๐ Fixed bad treatment of the new enclosing method feature in Tiger which sometimes led to AbstractMethodErrors at runtime.
-
v1.5.0._02 Changes
May 31, 2005๐ Fixed
- ๐ Fixed bad annotation handling for non-trivial annotations. Annotations had not been parsed and handled correctly, which could lead to either errors during obfuscation or Errors at runtime.
๐ Changed
- ๐ Improved obfuscation logic for enumerations. Now the two static methods valueOf(String) and values() don't have to be exposed manually anymore.
-
v1.5.0._01 Changes
May 24, 2005๐ Fixed
- ๐ Fixed a bug that made yGuard ignore some of the attributes in the expose section ("sourcefile" and "linenumbertable").
- ๐ Fixed a rare but severe bug that accidentally removed method attributes and sometimes led to
ArrayIndexOutOfBoundsExceptions
during the obfuscation.