buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert (JIRA)" <>
Subject [jira] Resolved: (BUILDR-335) excluding libraries from war is confusing
Date Thu, 19 Aug 2010 22:06:15 GMT


Alex Boisvert resolved BUILDR-335.

    Resolution: Fixed

Added another spec that shows bug is indeed fixed for:


boisvert@smudge:~/svn/buildr-trunk$ svn commit -m "Add another spec for BUILDR-335 (shows
that it is indeed fixed)" spec/java/
Sending        spec/java/packaging_spec.rb
Transmitting file data .
Committed revision 987327.

> excluding libraries from war is confusing
> -----------------------------------------
>                 Key: BUILDR-335
>                 URL:
>             Project: Buildr
>          Issue Type: Wish
>    Affects Versions: 1.3.5
>            Reporter: Ittay Dror
>            Assignee: Antoine Toulme
>             Fix For: 1.4.1
> 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.

View raw message