Skip to content

war:exploded changed since 3.4.1+ #593

@AnthonyArents

Description

@AnthonyArents

Affected version

3.4.1+

Bug description

up until 3.4.0 I managed to use packaging excludes as a way to remove frontend source code from my final war, but still be able to use frontend source code in war:exploded for local development. Netbeans uses war:exploded to link the project with tomcat. This use case seems to be overlooked when the following issue was adressed: #554. Would there be any way to allow for this old undocumented behaviour to work? maybe an extra parameter or having a specific parameter for packaging excludes only in war:war ?

Config in use

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-war-plugin</artifactId>
  <version>${build.plugin.maven.war}</version>
  <configuration>
    <packagingExcludes>
      static/frontend/**,
      build/index.html
    </packagingExcludes>
  </configuration>
</plugin>

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions