So as part of doing the jbossxb-1.0.0.CR8 release I dug a bit more into the maven deploy stuff so that I could deploy to the repository.jboss.com/maven2 cvs repository using mvn rather than copying files around. What I ended up doing is adding a local copy to file distributionManagement section withe a cvs-file-repository repository that references the local repository.jboss.com/maven2 cvs checkout: | ... | <distributionManagement> | <repository> | <id>cvs-file-repository</id> | <!-- Set maven.cvs.root in your settings.xml --> | <url>file://${maven.cvs.root}</url> | </repository> | </distributionManagement> | </project> | the maven.cvs.root is defined in the local settings.xml under a local-properties profile that is defined as active: | <settings> | <localRepository>/usr/Repository/maven2</localRepository> | <profiles> | <profile> | <id>local-properties</id> | <properties> | <maven.cvs.root>/usr/Repository/repository.jboss.com/maven2</maven.c... | </properties> | </profile> | </profiles> | | <activeProfiles> | <activeProfile>local-properties</activeProfile> | </activeProfiles> | </settings> | I still have to checkin the files via cvs. I guess the correct way is to move to using the mvn release:* plugins with full scm integration and a repository accessible via ssh rather than going through cvs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989534#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...