Maven 2.x WAR Plugin

packaged (war:war) and exploded (war:expanded) webapps have different content

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.1-beta-1
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Specifically, when using <packagingExcludes>WEB-INF/lib/*.jar</packagingExcludes>, the jars are correctly excluded from the packaged form of the war, but still present in the exploded form.

Both forms should have identical content and should be totally interchangable. This also means that there is no possible way to exclude jars from an exploded webapp.

As a workaround, I also attempted this:

<resource>
  <excludes>
    <exclude>WEB-INF/lib/*.jar</exclude>
  </excludes>
</resource>

But just got an exception thrown for my efforts...

Activity

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

If you read the documentation, the <packagingExcludes> parameter is only available for the war goal. Changing from bug to new feature.

http://maven.apache.org/plugins/maven-war-plugin/exploded-mojo.html
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html

Show
Dennis Lundberg added a comment - If you read the documentation, the <packagingExcludes> parameter is only available for the war goal. Changing from bug to new feature. http://maven.apache.org/plugins/maven-war-plugin/exploded-mojo.html http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html
Hide
Permalink
Dieter König added a comment -

Huh? You are referencing the documentation. Is possibly the documentation of exploded goal wrong?
"Description:
Create an exploded webapp in a specified directory."

How should this be understood?

By the way there is no need in functionality exploded goal provides ACTUALLY because the exploded directory in that form is already generated during war:war processing. That's why i was also assuming exploded would generate the "unpackaged" war and what indeed should be the truth.

Show
Dieter König added a comment - Huh? You are referencing the documentation. Is possibly the documentation of exploded goal wrong? "Description: Create an exploded webapp in a specified directory." How should this be understood? By the way there is no need in functionality exploded goal provides ACTUALLY because the exploded directory in that form is already generated during war:war processing. That's why i was also assuming exploded would generate the "unpackaged" war and what indeed should be the truth.

People

  • Assignee:
    Unassigned
    Reporter:
    Kevin Wright
Vote (2)
Watch (1)

Dates

  • Created:
    Updated: