search

vimalg / zaplink

Automatically exported from code.google.com/p/zaplink
0 stars 0 forks source link

Mass extractor makes source code changes #135

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
#WARNING : All issues must have the framework information file build using
transaction ZL_INFOS or if not working program ZAPLINK_INFOS_STANDALONE
(that could be downloaded). Each issue without these file might be close
without any investigation. Before opening an Issue please try with the last
framework version.

#What version of the product are you using? ==> add a release label
"Dectected-on ...".

0.9 Mass Extractor

What steps will reproduce the problem?
1. Create class
2. Export class using mass extractor. 

What is the expected output?

I expect the classes to be dumped to XML files to my local disk. I also expect 
that the classes will be accesses in READ-ONLY mode on SAP without any changes 
made.

What do you see instead?

Sometimes Mass Extractor is regenerating PUBLIC/PRIVATE/PROTECTED headers of 
classes (don't know exactly what the condition is). This results in a pop-up 
asking for transport requests. For users that only want to use Mass Export to 
keep their source code in a source code repository, this is unacceptable, as 
they do not want any changes in their SAP ABAP code.

#Please provide any additional information below.

Methods _CHECK_CLASS_SECTIONS and _cleanup_class are called. They are further 
calling function module SEO_CLASS_GENERATE_SECTIONS, which causes this nasty 
behavior.

Maybe a flag in the interface of the program should be added that reads 
'READ_ONLY' (selected by default) meaning that no changes will be made to SAP 
ABAP source code.

Original issue reported on code.google.com by dominik....@gmail.com on 5 Mar 2012 at 1:13

GoogleCodeExporter commented 9 years ago 
Hi,

We understand your issue, but mass extractor is just an autogenerated program 
to work as a stand alone program.
So we can't do anything on this program, we have to change the components.

Section's class are regenarate in order to have the same code signature which 
allow you to ensure "versioning"...
This is a standard behavior and is connected to issue 71.
Action made is "just" regenerate section in order to always have same source 
code.

We'll think of this request, but right know I do not have any idea to add this 
feature without impacting the whole framework.

I sugest to comment the two method in your version of the extractor stand alone.

Original comment by tar...@bensiali.net on 5 Mar 2012 at 2:04