[
https://issues.apache.org/jira/browse/BUILDR-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Toulme resolved BUILDR-335.
-----------------------------------
Resolution: Fixed
Fixed in 1.4.2:
22:09:36~/w/buildr>svn ci CHANGELOG lib/buildr/java/packaging.rb spec -m
"BUILDR-335 follow up: excluding libraries from war is confusing"
Sending CHANGELOG
Sending lib/buildr/java/packaging.rb
Sending spec/java/packaging_spec.rb
Transmitting file data ...
Committed revision 998400.
> excluding libraries from war is confusing
> -----------------------------------------
>
> Key: BUILDR-335
> URL: https://issues.apache.org/jira/browse/BUILDR-335
> Project: Buildr
> Issue Type: Wish
> Affects Versions: 1.3.5
> Reporter: Ittay Dror
> Assignee: Antoine Toulme
> Fix For: 1.4.2
>
>
> the confusion is from how ArchiveTask excludes files, but manifests itself in
> wars.
> when i create a war package, it automatically adds all compile dependencies
> as libs. then during preparation it adds them with
> path('WEB-INF/lib').include Buildr.artifacts(@libs)
> now say i have a library foo.jar which i want to exclude.
> these do not work:
> war.exclude('**/foo.jar')
> war.path('WEB-INF/lib').exclude('foo.jar')
> only this works:
> war.path('WEB-INF/lib').exclude('**/foo.jar')
> knowing that this is the way is not intuitive an required me to dig through
> the code of archive.rb
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
