[mojo-dev] [jira] (MNBMODULE-246) unable to use Proguard Obfuscator due to maven single phase order problem

[Sergei Ivanov (JIRA)]

Title: Message Title

Sergei Ivanov commented on an issue   Re: unable to use Proguard Obfuscator due to maven single phase order problem Option 1. Bind proguard execution to prepare-package phase and configure it to operate on classes instead of jar. http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference Option 2 (if option 1 fails or you do want to operate on jar) Make sure you are overriding the default executions (you can see them by running mvn help:effective-pom on your project). Then the plugin declaration order should take effect and will be reflected in the execution order within the same phase. http://maven.apache.org/guides/mini/guide-default-execution-ids.html For jar plugin the default execution will be something like this (plugin version may differ, but execution id is fixed and it is important): <plugin> <artifactId>maven-jar-plugin</artifactId> <version>2.3.1</version> <executions> <execution> <id>default-jar</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> </execution> </executions> </plugin> Add Comment   Mojo's NetBeans Module Maven Plugin / MNBMODULE-246 unable to use Proguard Obfuscator due to maven single phase order problem This seems to be a problem with older versions of this plugin or maven as well. The problem is that the nbm-maven-plugin, maven-jar-plugin and proguard-maven-plugin are going to be executed in phase package. Since maven 3.0.3 (I think) the execution order of plugins in the same phase should be preserved. I need the execution order maven-jar-pl... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email