[
https://issues.apache.org/jira/browse/SCM-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SCM-849.
------------------------------
Fix Version/s: (was: waiting-for-feedback)
Resolution: Won't Fix
This provider has been removed in master.
> SCM:EXPORT Goal for Synergy SCM does not work (or even is not implemented)
> ---------------------------------------------------------------------------
>
> Key: SCM-849
> URL: https://issues.apache.org/jira/browse/SCM-849
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-synergy
> Affects Versions: 1.9.5
> Environment: Windows
> Reporter: Raphaël MARTIN
> Priority: Blocker
> Labels: CI, maven, windows
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> the *scm:export* goal for Maven SCM Provider Plugin for IBM CM Synergy is not
> implemented or not working at all.
> I know that Synergy is an old or even obsolete SCM system. But it is still
> maintained by IBM in its version 7.2.
> I can understand why the *scm:export* has not been implemented and why you
> did not make evolving the SCM Provider Plugin since a long long time...
> But the *scm:export* would be really useful to me, in order to use it in
> Continuous Integration Process, involving CM Synergy. Even if CM Synergy is
> obsolete, it is not dead and widely used in my company (A big Automotive
> French Manufacturer). And of course, I cannot use *scm:checkout* +
> *scm:update* in place of *scm:export*.
> Maybe, with Synergy 5.x or 6.x, *scm:export* was impossible to implement. But
> I think with Synergy 7.2 (The last and only version supported by IBM since
> april 2016), new option in ccm command line tool can be useful to finally
> implement *scm:export*.
> I can even do the work and contribute to this task. Just explain how I can do
> that...
> FYI, in the documentation (maven *scm:help*) *scm:export* goal is considered
> as available.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
