[ https://issues.jboss.org/browse/RF-12903?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12903: --------------------------------- In order to don't force users to include two dependencies, just one, we have decided to refactor the assembly step: * The idea is that we can move the resource-plugin's source to the framework itself. * It will be located under {{src/main/resource-plugin}}. * Then, we can package it as {{richfaces-resource-optimizer.jar}} (the {{richfaces}} project JAR with classifier {{resource-optimizer}}. * This JAR will contain an API similar to the plugin's API (via Main class/method) * We will be able to execute this {{resource-optimizer}} in a {{prepare-package}} phase using {{maven-exec-plugin}} and generate optimized resources together with {{richfaces.jar}} generation * At the end, users will be provided with an option to use {{richfaces-resource-optimizer.jar}} to optimize a content for their applications * the optimizer will be dependency of {{richfaces-resources-maven-plugin}}, which will handle Maven-specific API -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira