Dale, At one of my clients we have a large TFS deployment for TFVC and GIT as well as a lot of the other SDLC support. However TFS does NOT include support for a binary component repository manager like Artifactory or Nexus. And we also ended up using Jenkins fyi.
I think you have no real choice but to use repository manager in parallel to your TFS server. If you try to put the component/repository management aspect into TFS/TFVC with some manual/custom setup you will spend considerable time and money getting that working and supporting it. My suggestion would be to get the development infrastructure support team (same team as TFS admins, often called build mgt team, or dev infrastructure or SCM...) to take on the role of managing a repo manager. When it comes to choice of repo manager my suggestions would be to use Sonatype Nexus OSS since it gives you support for Maven and NuGet repositories without any licensing requirements and is the most widely used repo manager. Nexus OSS also includes yum, npm and rubygems support in case you need those. Here is the Nexus docs. http://books.sonatype.com/nexus-book/reference/index.html You might also want to read some of the blogs posts regarding Nexus and Nuget from Damir Arh. http://www.sonatype.org/nexus/author/d-arh/ I hope that helps Manfred Disclaimer: I also work with Sonatype as Nexus trainer and author among other things. Preston, Dale wrote on 02.03.2015 11:57: > The .net world uses NuGet for dependency resolution in a way similar, but not > exactly like, Maven would use Artifactory or Maven repositories. The newest > version of TFS will support Maven builds and Java - though all the old > versions > did as well; it was just not as well integrated and required custom build > scripting. We'd like to dump our GIT/Artifactory/Jenkins for TFS so that the > TFS team can support our SDLC environment and our development team doesn't > have > to. > > We believe we can do everything except the dependency resolution/repository > functionality that Artifactory provides in TFS 2015. The TFS team doesn't > want > to support Artifactory though so we'd end up with split support for our > environment. I'd rather keep our SDLC stack than to just give part of it to > them but I'd love to hand it all off to someone outside of our developer team > for support so developers can work on coding. > > I hope that makes it clearer what it is that I'm trying to accomplish. > > Dale > > -----Original Message----- > From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] > Sent: Monday, March 02, 2015 13:07 > To: Maven Users List > Subject: [EXTERNAL]Re: TFS or NuGet repository for Maven > > Hi, > > What do you exactly mean by TFS / NuGet integration for Maven > repositories... > > A maven repository either in Artifactory or in other repository manager > don't need any integration into TFS (version control?) ? > > > Kind regards > Karl Heinz Marbaise > On 3/2/15 8:03 PM, Preston, Dale wrote: >> Is anyone aware of any TFS or NuGet integration for Maven repositories? We >> currently have an Artifactory repository internally for use with Maven but >> would like to integrate with our corporate TFS or NuGet servers for our Jave >> and Maven projects. >> >> Thanks, >> >> Dale >> >> Dale Preston >> Senior Integration Analyst >> Alaska Data Integrator >> 918-661-1346 (Desk) >> 918-931-9182 (Mobile) >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
