Maven project dependency in application?

[Filip Van Raemdonck]

Hi all,

I've been looking everywhere I could think of, but haven't found an answer
to the following question:

What's the (best?) way to add a library built from a Maven project into
a Netbeans project, as a dependency?
For that matter, what does "adding a dependency" on a project actually
do? Modify the classpath?

I've found no way to do the first, and no clear answer to the latter.
If I missed something I'd gladly be pointed to the right documentation.


Kind regards,

Filip

--
http://www.sysfs.be/

[Filip Van Raemdonck]

Hi all,

On Wed, Aug 12, 2009 at 09:54:05PM +0200, Filip Van Raemdonck wrote:

[Dave Heaton]

Hi Filip,

I posted a quick blog that outlines how I've been using Maven
libraries in a NetBeans suite:

http://analogsilence.com/2009/08/12/netbeans-maven-dependency-wrapping/

The process I describe does two things:

* copies Maven dependencies into your cluster's "modules/ext"
directory at build time (see http://wiki.netbeans.org/DevFaqWrapperModules)

* includes Maven dependencies as "class-path-extensions" in your
project.xml file (also see http://wiki.netbeans.org/DevFaqHowPackageLibraries)

It's definitely not an ideal solution, but like you, I couldn't find
anything at the time when I wrote it. It's used in an environment
where we have a large dependency set (over 60 libraries) and manually
managing library wrappers would be a nightmare. I also didn't want to
store libraries in SCM.

Just make sure the Maven library you've built from sources is deployed
to a repository somewhere, or at the very least, installed in your
local repository (via "mvn install").

Hope this helps.

-Dave

On 12-Aug-09, at 4:39 PM, Dave Heaton wrote: