#6 multiple outjars

[Anonymous]

Hi!

It would be great if ProGuard would have possibility
to create multiple outjars if there are multiple
injars. Usually it is quite inconvinient to pack
whole program inside one jar file or to create
different jars for different program libraries. In case
of client / server software one big jar file is not
good. And if there are different ProGuard projects
for every program libraries the scrambling can't be
that effective.

Basic suggestions is that classes from output jar x
are put to output jar x and classes from input jar y
are put to output jar y.

[Eric Lafortune]

Logged In: YES
user_id=555208

I can see some use for it, so I'll think about it. I'm not
sure if there aren't any hidden snags, and the necessary
configuration options could become confusing.

You should be able to achieve the same effect by repackaging
the contents of the single output jar into multiple jars.
Should this be too complicated, say, in client/server
software, you could probably first process all input jars in
a global shrinking/obfuscation pass. Next, you could create
a client jar and a server jar by passing the result through
two specific shrinking passes. Each of them would have
minimal size and they would still be compatible (although I
can see potential serialization problems). It's even better
than what you could achieve using this idea, with a client
jar, a server jar, and a common library jar, because both
the client and the server would get the library jar in its
entirety.

Eric.

[Brian Goetz]

Logged In: YES
user_id=27611

I think this feature is quite important. What we would like to
do is take multiple injars, run them through proguard in batch,
and then have all the classes from jar A go into the
obfuscated jar A, the classes from B go into the obfuscated
B, etc.

This is really important when building J2EE components which
must reside in their own JAR/WAR/EAR/SAR deployment unit.

[Jan te Lindert]

Logged In: YES
user_id=962504

Repackaging the single output jar into multiple output jars
might solve the problem. Fact is, that most of the time this
single output jar will have (very) much classes, which, due to
the obfuscation, are not recognizable anymore.
The mapping might help, but sorting all classes by the map file
should typically be a job for a program.
I would very much appreciate it, if this request was being
honoured.
It definitely enhances this great tool!

[Eric Lafortune]

Logged In: YES
user_id=555208

This feature (along with support for wars, ears, zips, and
directories containing them) is now included in the upcoming
version 3.0. You can group input jars and output jars for
collecting class files and resource files as desired. You
can also filter input jars and output jars (and wars, ears,
...) based on file names.