How to use a specific version or proguard

[Pascal]

Hello

I would like to use proguard 4.3 instead of the 4.2.

I tried to active 4.3 using the <proguardVersion> parameter:

<proguardVersion>4.3</proguardVersion>
<proguardInclude>proguard.conf</proguardInclude>
<proguard>true</proguard>
<proguardPreverify>true</proguardPreverify>

But it goes on calling v4.2 when I execute mvn package

[proguard] ProGuard, version 4.2

I tried also to declare the proguard plugin as v4.3

<plugin>
<groupId>com.pyx4me</groupId>
<artifactId>proguard-maven-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals><goal>proguard</goal></goals>
</execution>
</executions>
<configuration>
<proguardVersion>4.3</proguardVersion>
<libs>
<lib>${wtk.home}/lib/cldcapi11.jar</lib>
<lib>${wtk.home}/lib/midpapi20.jar</lib>
</libs>
</configuration>
<dependencies>
<dependency>
<groupId>net.sf.proguard</groupId>
<artifactId>proguard</artifactId>
<version>4.3</version>
<scope>runtime</scope>
</dependency>
</dependencies>
</plugin>

But it is worst: both v4.3 and v4.2 are called when packaging ?!

Could you help me to configure this please ?

Regards,
Pascal

[Vlad Skarzhevskyy]

Maven version? Platform?

--
Vlad

[Pascal]

C:\>mvn -version
Maven version: 2.0.10
Java version: 1.6.0
OS name: "windows vista" version: "6.0" arch: "x86" Family: "windows"

[Michael Hackett]

Pascal,

I haven't tried the <proguardVersion> element, but as a result of
switching to the 2.0.4-SNAPSHOT version for the fix Vlad just made for
me, I noticed that my <dependency> block (just like yours, except I
had v4.1 in there) started working. Also, the default Proguard version
with the new plugin version is 4.3 anyway.

-- Michael

On Mar 4, 7:26 am, Pascal <pascal.maug...@gmail.com> wrote:
> Hello
>
> I would like to use proguard 4.3 instead of the 4.2.
>
> I tried to active 4.3 using the <proguardVersion> parameter:

[...]

> I tried also to declare the proguard plugin as v4.3
>
>           <plugin>
>                 <groupId>com.pyx4me</groupId>
>                 <artifactId>proguard-maven-plugin</artifactId>

[...]

[Vlad Skarzhevskyy]

I'd say more that this is definitely a problem and probably not in
proguard-maven-plugin.

I have this working badly on OS X with older version of maven and so on.....

The problem is that it behaves different in multi module build as well....

I only hope that would be solved in maven 2.1 ....