Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

I understand why you would want to add archive information to a pom. But why SCM info? Is it possible to materialize a project completely from a pom?

The way I've always stored maven projects in svn, is I add everything (including the eclipse project, maven pom), to a repository. Any time I make a change to anything (including the pom), I do a SVN commit.

Is there a way to perform SVN operations directly through maven? Is this a best practice?

Another thing is important to know about Maven in this relationship, because if you are doing releases via the maven-release-plugin for which you need the SCM information, maven will automatically create SCM Tags for you etc.

Furthermore it's interesting to know where a project comes from if you are using an artifact in particularly in a commercial environment. (It's good to produce maven sites for that case).

It's also possible to do operations via the maven-release-plugin (create a branch) via Maven not via SVN directly.

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question . Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.
• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers .