Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Renaming non leaf package results does not rename full hierarchy #26

Open
doczir opened this issue Dec 14, 2015 · 1 comment
Open

Renaming non leaf package results does not rename full hierarchy #26

doczir opened this issue Dec 14, 2015 · 1 comment
Labels
bug UML to Java

Comments

@doczir
Copy link
Collaborator

doczir commented Dec 14, 2015

Because of how the java model handles packages, renaming a non leaf package means it will simply create a new package with the new name.

For example renaming the incquerylabs package in com.incquerylabs.evm.jdt will result in two packages: com.incquerylabs.evm.jdt and com.renamed
@doczir doczir added the bug label Dec 14, 2015
@doczir doczir closed this as completed in ecd6359 Dec 14, 2015
abelhegedus added a commit that referenced this issue Jan 6, 2016
@abelhegedus
fix #26 added ModelSetSnippet to avoid removing existing Java files
9951e27
@abelhegedus abelhegedus reopened this Jan 6, 2016
@itsdani
Copy link
Collaborator

itsdani commented Jan 6, 2016

In the following hierarchy

  • outerpackage
    • MyClass
    • innerpackage

after renaming outerpackage to renamed, the result in the Java project is:

  • renamed
    • innerpackage
  • outerpackage
    • MyClass

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug UML to Java
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@abelhegedus @doczir @itsdani