Question

I am having a java project with a ant build file, using this ant file i create an ejb of the project and deploy it on the jboss server.
Now I am planning to use maven and convert this existing project which consist of nearly 28-30 jar’s in its class path(jars related to ejb3, hibernate, jboss, etc).
I can easily do it using eclipse i.e right click project goto maven and click Conver to Maven.
A pom.xml is generated and the MavenClassPath Container is also added to the project.

Now I want to know how to get rid of those 28-30 jar’s present in the lib folder of the project and in the classpath. i.e. I want my pom.xml handle all the dependencies.
Does Maven provide any mechanism to achieve this goal while converting the project or I have to add all of these jar dependencies one by one manually in the pom.xml file.

The intention of doing this is I want to have common maven remote repository where the jars will be stored and each developer machine will point to it through their maven project.

Thanks

Answer 1

I think you’re after a repository manager like Nexus (I use Nexus, it seems to be the most popular http://nexus.sonatype.org/ ).

Nexus can be used as:

1. A proxy repository (for Maven Central, etc)
2. A repository for your own releases.

Nexus provides user management for your developers to release builds into the repo.

Developers will then point their Maven settings.xml file to your Nexus repository, and all their dependencies will come from here (Nexus will cache them).

I’m afraid you will have to configure the dependencies individually, but that is a good thing, because you should pay attention to what version ranges you are interested in for each dependency.

Any jars which can’t be found in Maven Central, etc, you can add to your own Nexus repository .

Ofcourse there are alternatives to Nexus, but I haven’t used any.

HTH