warSourceExcludes does not work in 2.1-alpha-2

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Not A Bug
  • Affects Version/s: 2.1-alpha-2
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

we use following configuration to produce jar-less war artifacts, in order to embed them to EAR:

<warSourceExcludes>WEB-INF/lib/*.jar</warSourceExcludes>

This does not work with release 2.1-alpha-2.
Switching to 2.1-alpha-1 solves the problem.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dennis Lundberg added a comment -

On closer inspection it is not the same issue as MWAR-182.

Show
Dennis Lundberg added a comment - On closer inspection it is not the same issue as MWAR-182.
Hide
Permalink
Dennis Lundberg added a comment -

This was a deliberate change between 2.1-alpha-1 and 2.1-alpha-2. From 2.1-alpha-2 onwards <warSourceExcludes> works only on the files in the <warSourceDirectory>.

To exclude files that are added during the packaging of the WAR you should use this instead:

<packagingExcludes>WEB-INF/lib/*.jar</packagingExcludes>
Show
Dennis Lundberg added a comment - This was a deliberate change between 2.1-alpha-1 and 2.1-alpha-2. From 2.1-alpha-2 onwards <warSourceExcludes> works only on the files in the <warSourceDirectory>. To exclude files that are added during the packaging of the WAR you should use this instead: 
<packagingExcludes>WEB-INF/lib/*.jar</packagingExcludes>

People

  • Assignee:
    Unassigned
    Reporter:
    Petr Kozelka
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: