I think the problem lies in the fact that the JS compress plugin uses the
artifacts created in the webapp directory in the build output directory.
The WAR plugin appears to also be using the same directory for the creation
of the WAR file and that is why the JARs are excluded in one and not the
other. Possible solutions I can see are:
1. Update the plugin to honor excludes of other plugins
2. Update the plugin to explode the WAR and use its resources, then
rebuild it.
3. Use the JAR plugin or the assembly plugin to handle the excludes,
as they will do it pre-package and the JAR files shouldn't ever make it into
the build output directory.
It is kind of hard to build our plugin to honor the configuration of
another, especially since not all users use the same standard set of
plugins. We can work on possibly doing the compression on the WAR but, it
will have worse performance than the current and is somewhat dependent on
the WAR being present, which can be handled via more configuration options.
This is a possibility but, would take some time to put into the trunk as
it's the holidays in the States and time is short. I would recommend the
third option but, it is up to you.
Hope this helps,
Adam Altemus
Senior Software Engineer
(724) 349-3339 ext. 302
(800) 830-5578 fax
aaltemus at mobilvox dot com
http://www.mobilvox.com <http://www.mobilvox.com/>
Confidentiality Notice: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
immediately notify the sender by reply e-mail and destroy all information
and attachments.
|
