Home/ Questions/Q 377647
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T14:43:01+00:00

EDIT : Ok… so I’ve gathered that SVN shouldn’t really be used for this…

  • 0

EDIT: Ok… so I’ve gathered that SVN shouldn’t really be used for this… which makes sense, I suppose (why version individual files when the version should be a separate jar?).

So we should use an internal server to host a repository management tool like Nexus (etc), and access that over http to pull down and put out dependencies. We are keeping our projects in SVN now. What is the standard for deployments? Dependencies go into Maven. Projects go into SVN. Should we ignore the dist and build folders? Where would our WAR files get deployed from?

OLD QUESTION (for posterity)

I’m brand new to Maven and don’t know jack about it. I’m trying to evaluate it to see how it will do with our Java development.

I would like to have a Maven repository in our SVN server so that dependencies can be pulled down from there using NetBeans 6.7. I have not been able to find how to do this throughout many google and stackoverflow searches.

What are the best practices here? I’m thinking that we’d want to download dependencies using svn+ssh, but most things online seem to point to using http.

Fill my brain with great things!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’d strongly recommend against doing this. Maven artifacts don’t belong on an SCM server. You should consider using a repository manager like Nexus to store your artifacts. See here for a comparison of the main repository managers.

    Having said that. If you are determined to use Subversion to host your artifacts. See this question on using the wagon scm to deploy to a Subversion repository.

    If you want to find out more about Maven, check out Maven: the definitive guide.

    There is a Maven plugin for Netbeans that will manage dependencies. This article lists some best practices for Maven and Netbeans.

    Update based on your updated question. What to do with your own jars:

    Maven has a deploy phase that will publish your artifacts to the remote repository. You need to configure the distributionManagement section of the pom, and provide appropriate credentials in your settings.xml to allow the deployment to happen. Typically you would set up a discrete logical repository on the server for your own artifacts to keep them isolated from third party artifacts. The Nexus book gives some good guidance on configuring repositories on Nexus. In particular see the Adopting a Repository Manager section.

    If you have configured your project correctly, run mvn deploy and all phases up to and including the deploy phase will run, and your artifact will be published to the repository, available for use by the rest of your team/company.

    If you need to restrict access to repositories, you can configure access controls to your repository so only authenticated users can access those artifacts (for Nexus see the Managing Security section of the book for guidance).

    It’s worth noting you can do largely the same things (more or less) with Artifactory or Archiva as Nexus, I’ve included Nexus references because I prefer it, and the documentation is really good.

    • 0