mirror of
https://github.com/abapGit/abapGit.git
synced 2025-05-04 05:47:17 +08:00
75d01344d8
For some reason, we are using experimental features of abapGit.
Some time ago, all class were re-serialized with the serializer
LCL_OBJECT_CLASS_NEW.
After upgrade to 1.60, we started getting an error telling that CLAS
is not supported.
The CLASS NEW serializer became standard and the class has been renamed.
Unfortunately, our xml files still includes reference to the CLASS NEW.
I would just use a sed script, if knew all the affected repositories -
we have plenty of repositories versioned by abapGit.
This patch revives the CLASS NEW. It reports itself as the standard
class, so the CLASS NEW can be removed in year or two when all files
are re-serialized.
See commit 21d22d93f2
18 lines
497 B
XML
18 lines
497 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<abapGit version="v1.0.0" serializer="LCL_OBJECT_CLAS" serializer_version="v1.0.0">
|
|
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
|
|
<asx:values>
|
|
<VSEOCLASS>
|
|
<CLSNAME>ZCL_ABAPGIT_OBJECT_CLAS_NEW</CLSNAME>
|
|
<VERSION>1</VERSION>
|
|
<LANGU>E</LANGU>
|
|
<EXPOSURE>2</EXPOSURE>
|
|
<STATE>1</STATE>
|
|
<CLSCCINCL>X</CLSCCINCL>
|
|
<FIXPT>X</FIXPT>
|
|
<UNICODE>X</UNICODE>
|
|
</VSEOCLASS>
|
|
</asx:values>
|
|
</asx:abap>
|
|
</abapGit>
|