Creating/Accessing Maven repository in SVN through NetBeans 6.7 *Revised?

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.

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.

Don't store them in SVN. I would do two things to make sure you're not getting too many headaches: Mirror a repository closer to your box someplace that you and your workmates can share. This will eliminate extra downloading and allow you to fix any problems that may come up (and they will) with the mirrored pom/jar files so your mates don't have to share in the headache.

There are several repo managers out there that help with this. Do your best to work with your machine repository and push changes/modifications to any pom files that you may make to the local shared repo.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.