I think that's a bug - the properties aren't overwritten.
Mmm all right.
Try this:
add another profile with true,
and move the inside that profile.
If you don't activate the profile, that default profile should be enabled.
If you activate the obfuscation profile, then the default profile
sh
Stephane Nicoll wrote:
Hi,
On 1/13/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
The last solution i can think of is to specify
${obfuscate}
on all deps (in project A and B ) that can have an obfuscated attachment.
You could use a profile or -Dobfuscate=obfuscated. You just have to
make s
Hi,
On 1/13/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
The last solution i can think of is to specify
${obfuscate}
on all deps (in project A and B ) that can have an obfuscated attachment.
You could use a profile or -Dobfuscate=obfuscated. You just have to make sure
that not specifying to
On 1/13/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Obfuscated jars are usually only needed for binary distributions (assemblies).
A simple solution would be to have a distribution assembly project that directly
depends on all obfuscated jars.
Yeah that's one idea and I actually like it. T
Hi,
I don't know what your usecases are, but here are some ideas:
Obfuscated jars are usually only needed for binary distributions (assemblies).
A simple solution would be to have a distribution assembly project that directly
depends on all obfuscated jars.
Second solution is to obfuscate the j
Hi,
I already discussed this with brett and Dan and I would like to see if
anyone here has more insight about how to handle obfuscated jars.
The basic use case I have is to be able to specify whether I want the
standard jars or the obfuscated jars for a particular project.
Obfuscated jars are ha
