maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <>
Subject [jira] Updated: (MEAR-87) Allow exclusion of artifacts when building the ear file.
Date Sun, 03 Aug 2008 15:41:26 GMT


Stephane Nicoll updated MEAR-87:

    Fix Version/s: 2.4

That's interesting but we start having so many configuration options to manage the dependencies
that I am afraid it becomes too much complex. We already have the excludes on the modules
so we need to define a first-win strategy (and who wins on what).

> Allow exclusion of artifacts when building the ear file.
> --------------------------------------------------------
>                 Key: MEAR-87
>                 URL:
>             Project: Maven 2.x Ear Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.3.1
>            Reporter: Dieter Houthooft
>            Priority: Minor
>             Fix For: 2.4
>         Attachments: maven-ear-plugin-excludes-fixed.patch, maven-ear-plugin-excludes.patch
> What is included in the .ear file is determined by the module list and the dependency
list and its transitive dependencies. We are often confronted with changing demands about
what to include in our ear files. It is quite hard to change our dependency management (scopes)
every time without side-effects on other distributable artifacts. So I created an exclude
configuration option which allows to exclude artifacts from the ear file based on regular
expressions (java.util.regex) matching artifactIds and groupIds.
> Use it like this:
> <configuration>
>    <excludes>
>       <exclude>
>          <groupId>be.nondistributable.*</groupId>
>       </exclude>
>    </excludes>
> </configuration>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message