ADT Eclipse Two Methods in one Class in two Transport Requests

[Bastian_Stritt]

Hello,

if I change 2 Methods in 1 Class, SE80 asks me twice for a Transport Request, so I can easily separate them, e.g. if one change is a correction of a production error.

In Eclipse I dont get this question. If I change the second method, it assignes the change directly to the same TR as for Change 1.

Is it possible to change this behavior to the way like in SE80?

Best regards

Bastian

[Jeansy]

Hi,

in ADT it is not possible to put single methods into different Transport Requests as the whole class is shown in ADT and therefore the whole class is added to the Transport Request. This is a known issue.

This has been addressed already here: https://influence.sap.com/sap/ino/#/idea/277509

Kind regards
Jens

[matt]

It certainly causes an issue when my non-eclipse using colleagues edit a method!

[Bastian_Stritt]

Hi,

thank you for your answer.

If you use "Format Block" instead of "Format" (other Shortkey) it doesn't lock the whole class. It reformats just the Method you changing atm and then ADT only transports this method.

And, if you separate 2 methods of the same class in SE80 in 2 TRs, Eclipse can handle this case. But it can't create it...:(

Kind regards

Bastian

[ThFiedler]

Hi Bastian,

that is because you are editing the complete class in one editor. Let's assume you are changing several methods and press save. Do you then expect several transport request popups?

We have the idea of providing a single method editing mode in ADT. But this is huge effort and currently not in our backlog. Maybe we can think about a "smaller" solution that solves the transport request issue.

Regards,

Thomas.

[Bastian_Stritt]

Hi Thomas,

exact this. In SE80 it works likes this (in Form Mode), if I change 3 Methods, I have to press 3 times SAVE and I get asked 3 times for a TR. I want something similar in Eclipse.

I have this sometimes, when I have to different developments (one new feature and one bug, for example) and I need them to transport separat.

This single edit Mode in Eclipse would be nice, but amt I dont need it. I use "Format Block" for Pretty Printer instead just "Format". So, only the current method is formatted, not the whole class. And this helped me a lot with locking.

Regards Bastian

[VXLozano]

Because my past experiences, I love the new behaviour. Yes, it has its limitations, but with my level of accidental transport mix-ups, the rule "one dev object <=> one transport request" works wonders.
Just my two c

[matt]

thomasfiedler Although I like the entire class editor, if there were a single method editor, I'd be able to compare just that method with previous versions or across systems. Although the fact that I can do so with an entire class is often very useful as well.

[matt]

Could I venture to suggest that if you need two methods in different transports, you should look carefully at whether your class is too big, or is fulfilling more than one function - violating the S of SOLID principles.

[Bastian_Stritt]

matthew.billingham Yes you are correct. But if the Class is old and huge what should I do? Refactoring is huge efford in Dev and Testing. We do this, but it needs time.

And, as I mentioned, if I have a bug in production in Method A and work on Method B for a new feature, I have this Problem. It is not very often, but sometimes and this would help.

[matt]

Oh, it'd be a neat feature, I agree. I have inherited some huge classes. If I have to add something new, I often put the new thing into its own class, rather than create a new method. And like you, occasionaly, I bite the bullet and refector into separate classes. Anything that reduces technical debt!

[Bastian_Stritt]

If a class has already 2 TR associated to it, this Dialog appears if I change another method:

but I can't get this, if only one TR is associated. This would be enough, so ADT can handle this already...