Setting up Maven to allow deployment to different repositories easily

Question

I\'m currently working in an environment where I define the rules for a lot of people. We currently use Hudson and Artifactory, and I want to evaluate if the switch to Jenkins a

Answer 1

I'm on a similar team, providing tools to others. We have our parent POM (not the settings.xml) set up like the below. The prod version is active unless one of my team members adds -DuseTestRepo=true to the mvn command line. You could experiment with changing the activation to look for a particular file that exists only on the Jenkins server (for example). I've also wondered if Maven interpolates properties in repo URLs. If it does, you could do ${my.remote.repo}/releases and define my.remote.repo in settings.xml. Haven't tried that one.

    
        test-repository
        
            
                useTestRepo
                true
            
        
        
        
        
            
                 
            
            
                 
            
        
    

    
        prod-repository
        
            
                !useTestRepo
            
        
        
        
        
            
                 
            
            
                 
            
        
    

As to delivering (deploying) your experimental parent POM - you would be deploying it to your test Nexus repo, right? And none of your developers are accessing that, only you. So Artifactory will contain the real com.company:corporate-parent:1.0 POM, and Nexus the com.company:corporate-parent:1.0 that contains the changes you require for your testing.

I would also consider changing the local repo in your settings.xml so you don't mix artifacts from the two remote repos.