Browse Version - jira.codehaus.org

All Projects : Maven SCM : future (Fix For Version)

Summary

SCM-188	UNRESOLVED	Add the posibility of adding an entire directory to SCM
SCM-154	UNRESOLVED	Bazaar tests should not assume bzr is installed
SCM-54	UNRESOLVED	API enhancement for SSCM vendor compatability
SCM-38	UNRESOLVED	Ability to assign an issue tracking to add, lock, and checkin
SCM-39	UNRESOLVED	Ability to checkout/update selective modules under root
SCM-34	UNRESOLVED	Add PVCS support
SCM-157	UNRESOLVED	Add TCK tests for Clearcase
SCM-156	UNRESOLVED	Add TCK tests for Perforce
SCM-158	UNRESOLVED	Add TCK tests for Starteam
SCM-117	UNRESOLVED	Add parameters to scm configuration element
SCM-271	UNRESOLVED	Allow scm:checkin to run without a pom
SCM-267	UNRESOLVED	Branches setting is being used as a tag
SCM-23	UNRESOLVED	Capabilities query support.
SCM-167	UNRESOLVED	Check out complains about missing directory.
SCM-33	UNRESOLVED	Collect more information into the ScmFile
SCM-153	UNRESOLVED	Continuum fails while trying to build from clearcase
SCM-42	UNRESOLVED	Create a ChangeSorter for sort and group ChangeSet list
SCM-227	UNRESOLVED	Document use cases for maven-scm-plugin
SCM-273	UNRESOLVED	Each provider must provide a facilty to detect whether it can run on a given system
SCM-69	UNRESOLVED	Improve error message when commit over https fails
SCM-121	UNRESOLVED	Intermittent CVS test failures
SCM-281	UNRESOLVED	Perforce problem: incorrect client spec is used
SCM-269	UNRESOLVED	Perforce support doesn't work when there's a space in the local path
SCM-214	UNRESOLVED	Provide ability to bootstrap project just by groupId and artifactId
SCM-142	UNRESOLVED	Starteam tree stale
SCM-274	UNRESOLVED	Support tagging with non-standard svn repository layout
SCM-261	UNRESOLVED	Synergy provider assumes instance of 1 for projects... won't work for distributed CM (and some other scenarios)
SCM-258	UNRESOLVED	The perforce provider should be able to accept complex filespecs using a clientspec rather than the path in the SCM url
SCM-257	UNRESOLVED	The perforce provider should provide an "update" functionality for the SCM plugin's "update" command that is semantically correct.
SCM-31	UNRESOLVED	The scm url validator should return a code corresponding to the error
SCM-223	UNRESOLVED	VSS add command
SCM-240	UNRESOLVED	add support for tagging a revision
SCM-132	UNRESOLVED	extssh connection method not shown
SCM-262	UNRESOLVED	scm:tag for subversion tagging from local version of code, not directly from repository
SCM-207	UNRESOLVED	Implementing update and checkout command

	maven-plugin	4
	maven-scm-api	8
	maven-scm-provider-bazaar	1
	maven-scm-provider-clearcase	3
	maven-scm-provider-cvs	2
	maven-scm-provider-perforce	5
	maven-scm-provider-pvcs	1
	maven-scm-provider-starteam	3
	maven-scm-provider-svn	3
	maven-scm-provider-synergy	1
	maven-scm-provider-vss	2
	No Component	3