Return-Path: 
 <user-return-5221-apmail-uima-user-archive=uima.apache.org@uima.apache.org>
X-Original-To: apmail-uima-user-archive@www.apache.org
Delivered-To: apmail-uima-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 333E6107D0
	for <apmail-uima-user-archive@www.apache.org>;
 Sun, 28 Jul 2013 10:38:01 +0000 (UTC)
Received: (qmail 91491 invoked by uid 500); 28 Jul 2013 10:38:00 -0000
Delivered-To: apmail-uima-user-archive@uima.apache.org
Received: (qmail 91281 invoked by uid 500); 28 Jul 2013 10:38:00 -0000
Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@uima.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@uima.apache.org>
List-Post: <mailto:user@uima.apache.org>
List-Id: <user.uima.apache.org>
Reply-To: user@uima.apache.org
Delivered-To: mailing list user@uima.apache.org
Received: (qmail 91273 invoked by uid 99); 28 Jul 2013 10:37:59 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Jul 2013 10:37:59 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of richard.eckart@gmail.com
 designates 209.85.215.172 as permitted sender)
Received: from [209.85.215.172] (HELO mail-ea0-f172.google.com)
 (209.85.215.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Jul 2013 10:37:53 +0000
Received: by mail-ea0-f172.google.com with SMTP id q10so2408913eaj.3
        for <user@uima.apache.org>; Sun, 28 Jul 2013 03:37:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        bh=O7Pm1T8WwUFm901FhbiMPoV5KOw/maqzDJpiF1Q5vL0=;
        b=qh3ITFOiWzXdGPxYwnYUyp4jrI6NkVOia/8jsK+xyoAn5mvt6if8Jv3k6QGUjTHkua
         AOPWWm3rVyqQ4olSmfiN5NDqw17oF1x/ToDOZ+YRAWNL4rCn/Pxx2QIhFFLFmCA+JVsf
         NENZpngiADHEXwe1rI7DJcLOw46cM2cQmAOMNkK637VojI0WfUi9Z+4nu5BKMGuSAl+h
         iSB0oupH/KpQdJlhUcGbMSTdIHv0a2RZa3BZ6/VtogXDwSDZ4FJxe+L9QHzU6cTfy+VZ
         rU0es6+60qB2nClOHMem96L63CMPl97F04FzkhThIU7HX1Tdjob8WKeliZbChNAcsfvO
         f3Nw==
X-Received: by 10.14.98.6 with SMTP id u6mr54689033eef.62.1375007853704;
        Sun, 28 Jul 2013 03:37:33 -0700 (PDT)
Received: from [10.0.1.20] (ip-176-199-182-177.unitymediagroup.de.
 [176.199.182.177])
        by mx.google.com with ESMTPSA id c3sm94190772eev.3.2013.07.28.03.37.31
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Sun, 28 Jul 2013 03:37:32 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Uima and Proguard obfuscation
From: Richard Eckart de Castilho <richard.eckart@gmail.com>
In-Reply-To: <loom.20130728T121417-252@post.gmane.org>
Date: Sun, 28 Jul 2013 12:37:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3A9380A7-A9CA-4B4F-A2B6-09A8ACF180C9@gmail.com>
References: <loom.20130728T121417-252@post.gmane.org>
To: user@uima.apache.org
X-Mailer: Apple Mail (2.1508)
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

uimaFIT uses a lot of reflection to inject parameter values.=20
I can well imagine that you have to be quite careful here.
Probably better not touch annotations and annotated fields at all
and restrict obfuscation to logic, such as the process() method.

It may be even better to extract the core logic that you want to
obfuscate entirely from the UIMA components and leave the UIMA
wrappers for your logic unobfuscated.

That said, the obfuscator may have "optimized"=20
> private String outputDirectory

away, because the value is never changed in the code known
to the obfuscator. It cannot know that uimaFIT changes this
field using reflection.

-- Richard

Am 28.07.2013 um 12:27 schrieb swirl <swirlobt@yahoo.com>:

> Hi!
>=20
> I was trying to create a obfuscated API library based on Uima/Uimafit.
>=20
> My project was in Maven so I used the Proguard plugin:=20
> http://pastebin.com/T3N3JgVv
>=20
> When tried to use the obfuscated jar in a separate application, an =
Uima=20
> parameter "PARAM_OUTDIR" was strangely nullified.=20
>=20
> For an un-obfuscated jar, looking through a decompiler:
> http://pastebin.com/JnQkV2mJ
>=20
> When I looked at the jar through a decompiler, this is what I see:
> http://pastebin.com/B0ZJpaFk
> Notice the line "private String outputDirectory;" is totally removed =
in the=20
> obfuscated jar.
>=20
>=20
> Is Proguard compatible with Uima/Uimafit?=20
> Is my plugin config incorrect?