How to build my own Maven dependencies in NetBeans, without a parent project

Question

0.00/5 (No votes)

See more:

I'm using NetBeans 7.4 RC1 to create Maven projects.

Let's say I create two Maven projects, named A and B, and a third named X which includes the other two projects as dependencies.

On building X Maven searches the local Maven repository (and the connected company-proxy) for the dependencies and obviously does not find any initially.

If I run the build command of NetBeans on projects A and B, it performs a maven install, which then installs the projects into my local repository. Now, when I build X it will find the dependency and all is well.

Is there a way to configure Maven (or NetBeans) to automatically build the dependencies (and install it to my local repository)? I know there's a solution to do this with POM Projects where the modules (in this case A, B and X I suppose) can be added to it, and the POM project specified as a parent in all the modules - this will allow me to select the "Build with Dependencies" option, which will then build all the modules in the POM project. But this is not a good solution if say project A is a utility project, used in many other projects.

Essentially what I'd like to avoid is building all the dependencies for a project every time I want to test my project; especially when I'm working on the project and its dependencies at the same time.

I hope I'm missing the point.

Posted 26-Sep-13 3:15am

Thinus Prinsloo

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Nagy Vilmos · Answer 1 · 2013-09-26T03:21:00

Solution 1

I think you may be missing the point [or I am]

TTBOMK, once the dependencies are built for the first time then everything will look after itself. So there is no need to keep rebuilding all the projects all the time, the rebuilds are done as and when they are needed.

Posted 26-Sep-13 3:21am

Nagy Vilmos

Comments

Thinus Prinsloo 27-Sep-13 2:32am

With Maven it's not quite that simple. Not only should code be built, but it should also be installed into your local Maven repository, so that other projects using that code as dependency will get the latest version (automatically from the local repository).