[ 
http://jira.codehaus.org/browse/MEAR-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103389
 ] 

Thomas Hart commented on MEAR-73:
---------------------------------

I mean that the 
[dependency:resolve|http://maven.apache.org/plugins/maven-dependency-plugin/resolve-mojo.html]
 with the property {{excludeTransitive}} don't have any effects to the ear 
plugin.

The patch works for me. The following pom.xml produces the right ear (see 
image). Only the {{dependencies}} are included *not* the transitive 
dependencies.
{code:xml}
...
     <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-ear-plugin</artifactId>
        <version>2.3.1-SNAPSHOT</version>
        <configuration>
          <excludeTransitive>true</excludeTransitive>
          <version>5</version>
          <defaultLibBundleDir>lib</defaultLibBundleDir>
          <modules>
            <ejbModule>
              <groupId>suite4p.enabler.jb402</groupId>
              <artifactId>suite4p.enabler.jb402.server</artifactId>
            </ejbModule>
          </modules>
          <jboss>
            <version>4</version>
          </jboss>
        </configuration>
      </plugin>
    </plugins>
  </build>
  
  <dependencies>
    <dependency>
      <groupId>suite4p.enabler.jb402</groupId>
      <artifactId>suite4p.enabler.jb402.server</artifactId>
      <type>ejb</type>
    </dependency>
  </dependencies>
{code}

> Property to disable transitive dependencies resolving
> -----------------------------------------------------
>
>                 Key: MEAR-73
>                 URL: http://jira.codehaus.org/browse/MEAR-73
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Improvement
>            Reporter: Thomas Hart
>            Assignee: Stephane Nicoll
>         Attachments: patch.txt
>
>
> We have ears with a lot of modules. So the transitive dependencies are very 
> huge and to exclude all these with {{<excluded>true</excluded>}} is no 
> option. Also to mark these dependencies with optional is no way. It is 
> possible to create a new property for that?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to