Property to disable transitive dependencies resolving

Not sure it's EAR-plugin related. This sounds more like a maven-core functionnality to me.

Sorry i'm a maven newbie, i don't know where the right position is. But I think the following code block include the unwanted dependencies.

ScopeArtifactFilter filter = new ScopeArtifactFilter( Artifact.SCOPE_RUNTIME );
if ( !isArtifactRegistered( artifact, allModules ) && !artifact.isOptional() &&
  filter.include( artifact ) )
{
    EarModule module = EarModuleFactory.newEarModule( artifact, defaultLibBundleDir );
    allModules.add( module );
}

I try to use the excludeTransitive parameter for the dependency:resolve-plugins mojo. Maybe that works for me.

Mmmm, true.

What you're asking is disabling transitive deps altogether or you want to disable them for a particular dependency?

In my case altogether.

I check the dependency plugin, it doesn't work. Can i submit a patch, that excludes the code block above?

no It won't do what you expect.

WDYM when you say "it doen't work"?

I mean that the dependency:resolve 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.

...
     <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>

> I mean that the dependency:resolve with the property excludeTransitive don't have any effects to the ear plugin.

Well I wonder how it could have any effect.

And your patch is plain wrong anyway: it works as a side effect. since you have a single dependency and non scope dependencies. Trust me, your simple project does not reflect how this plugin is used at all.

also note that you don't need the ejbModule entry at all. It's only used if you want to customize module's parameters (bundle file name, uri, etc)

Ok i see it. Your are right, the patch is wrong.

Please give me a second try, i think project.getArtifacts() is the right place. To get the list with no transitive dependencies simply use project.getDependencyArtifacts().

Hi Stephane,

Any chance of getting this in? Looks like the above change will not affect the normal flow. This allows folks to explicitly choose what gets EARed up and not worry about transitive dependencies.

It's missing test cases so I need to write them first. But that sounds reasonable indeed. It's just not complete as a patch for now.

Hi,

We are also facing same issue in maven-ear-plugin. In our project, one of our transitive dependency using ".so" files. In that project, they didn't specify any scope for ".so" files. Also it is not possible for us to give scope (entirely different project, and it is not in our hands to change/give scope). Finally when we build our ear module, it is throwing unknown artifact types[so].

Could you please let me know when it will be fixed?

Thanks,
Kannan

you can exclude the dependency. Defining the so dependency again with scope provided will most probably fix the issue