Hello,

I'm trying to create an "installer" artifact type, and then depend on
the installer's dependencies in other projects.

The transitive dependencies aren't being exposed in the dependent project.

A concrete example of what's currently Not Working for me is this: I
want to provide a "jdbc-drivers-installer" that declares it's
dependencies on e.g.,

<dependency>
 <groupId>postgresql</groupId>
 <artifactId>postgresql</artifactId>
 <version>x.y.z</version>
</dependency>

(as well as other JDBC drivers). I've been able to kludge up a buld
lifecycle for <packaging>installer</packaging> such that Maven
produces a jdbc-drivers-1.0.0-SNAPSHOT-installer.tar.gz, which 1)
bundles the declared dependencies and 2) adds an install.sh at the top
level that when run will copy the bundled dependencies to the
appropriate place on the appliance. This part I've got working, as I
described here 
(http://www.nabble.com/Trying-to-%22reuse%22-the-maven-assembly-plugin-tf3416766s177.html).

The part that doesn't work, the applications that are going to be
installed on the appliance, such as webapps, depend (...) on the exact
same set of JDBC drivers, and I want to express this dependency inside
the webapp POM as follows:

<dependency>
 <groupId>net.example</groupId>
 <artifactId>jdbc-drivers</artifactId>
 <classifier>installer</classifier>
 <type>tar.gz</type>
 <scope>provided</scope>
</dependency>

(in other words, I want to manage the specific JDBC dependencies in
the same place as builds the installer.tar.gz, and I want to get these
on the compile classpath by depending to that installer artifact,
through transitivity; Don't Repeat Yourself, as it were).

Yeah. Not So Much. The dependency on the installer is honored by Maven
(I can see the dependency when I build the dependent, using mvn -X),
except it appears the artifact handler doesn't know what to do with
it. Or, more accurately, the default artifact handler doesn't know
that I expect the transitive dependencies to be added to the webapp's
compile classpath. As a result, the dependent webapp build fails with
compile errors on the import statements.

I suspect I'll be having to write a custom artifact handler, but I'm
wondering whether anybody here can offer recommendations how to go
about it.

Thanks,
--
Tommy

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to