Community
Participate
Working Groups
3.2 M5 testing - have two source folders, 'src' and 'tests' - have a CU 'org.eclipse.m5testing.Foo' in 'src' in its corresponding source folder - use drag and drop to move 'Foo' to the 'tests' source folder, which is currently empty < expected: the package ('org.eclipse.m5testing') is kept and the corresponding folder structure created under 'tests'. > actual: the cu is dropped into the default package Note that I only want the described behavior when dropping onto a source folder. The current behvavior is fine when the user drops onto a specific package, as he probably wants the moved elements to appear there. However, when I just want to split up a package, it would be much more convenient as described above. Going through Refactor > Move > Create New Package... is much more complicated. Imagine the following scenario: - I quickly and dirtily created some code, accompanied with the corresponding tests. - I find out that I want to separate the testing harness from the production code: - create a source folder 'tests' - move any classes that are testing-only code to the new source folder.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
