[
http://jira.codehaus.org/browse/MIDEA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94026
]
Larry Hamel commented on MIDEA-88:
----------------------------------
Yes, scm section has been there all along, and that scm works for calls like
mvn scm:checkout. Here it is, with some details edited out:
<scm>
<!-- to use this scm declaration in continuum,
must have 'ext' set up to so ssh with appropriate private key -->
<connection>scm:cvs:ext:[EMAIL
PROTECTED]:/ssr/blahk:faqtory</connection>
<developerConnection>scm:cvs:ext:[EMAIL
PROTECTED]:/ssr/blahk:faqtory</developerConnection>
<!--<tag>HEAD</tag>-->
<url>https://blah.com/scgi-bin/viewcvs.cgi</url>
</scm>
The key is that is clearly has 'cvs' as provider. that is the key setting that
is lost in an idea:idea update.
WORKAROUND: if just updating dependencies, idea:module is sufficient and
doesn't change project.
> version control setting lost on update
> --------------------------------------
>
> Key: MIDEA-88
> URL: http://jira.codehaus.org/browse/MIDEA-88
> Project: Maven 2.x Idea Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: idea 6.0.5 windows xp
> Reporter: Larry Hamel
>
> have project with version control set to cvs.
> change pom for a new dependency.
> close project. in idea
> mvn idea:idea
> open project in idea
> see that version control setting is lost
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
