I'm always annoyed having to create wro.properties and wro.xml when using
maven-wro4j-plugin. Ideally, all that configuration could be done directly in
the maven-wro4j-plugin <configuration>
You'd have something like :
<configuration>
<targetGroups>bootstrap</targetGroups>
<cssDestinationFolder>${project.build.directory}/${project.build.finalName}/css/</cssDestinationFolder>
<jsDestinationFolder>${project.build.directory}/${project.build.finalName}/js/</jsDestinationFolder>
<wroManagerFactory>ro.isdc.wro.maven.plugin.manager.factory.ConfigurableWroManagerFactory</wroManagerFactory>
<preProcessors>cssImport,semicolonAppender</preProcessors>
<postProcessors>lessCss,cssMinJawr</postProcessors>
<groups>
<group name="bootstrap">
<css>/less/bootstrap.less</css>
<js>/js/bootstrap-transition.js</js>
<js>/js/bootstrap-alert.js</js>
<js>/js/bootstrap-modal.js</js>
<js>/js/bootstrap-dropdown.js</js>
<js>/js/bootstrap-scrollspy.js</js>
<js>/js/bootstrap-tab.js</js>
<js>/js/bootstrap-tooltip.js</js>
<js>/js/bootstrap-popover.js</js>
<js>/js/bootstrap-button.js</js>
<js>/js/bootstrap-collapse.js</js>
<js>/js/bootstrap-carousel.js</js>
<js>/js/bootstrap-typeahead.js</js>
</group>
</groups>
</configuration>
plugin configuration would take precedence over config files by default.
Original issue reported on code.google.com by fbri...@gmail.com on 12 Jun 2012 at 12:33
Original issue reported on code.google.com by
fbri...@gmail.com
on 12 Jun 2012 at 12:33