Changing JPA entity

[devedipoint]

Let's assume we have a Entity with fields and relationships with others. Now we cannot use entity generator to change this Entity (fields, relations) because:

• it will overwrite existing classes and *.js
• it will add next liquibase file like it would creating entity in contrast to make alter table. It causes exception with liquibase trying to add the same table again.

1. It could detect if Entity exist and then fill existing fields and relationships, to enabling changes.
2. Generator can detect what is changing by diff. On this basis, we can detect if a field is :

• added
• modified
• removed

and add this information to liquibase changeset. The same is with relationship and extending classes.

What do You think?

[jdubois]

• This has changed in the v2.0.0 version, as we will "remember" the entity when you run it again. But still, the basic issue still exists.
• On the Java part I'm not too worried: people can just code it, if it's just adding a field we don't provide much value. Otherwise we need to have some comment somewhere so we know where to add the code (like here)
• The real issue is Liquibase: it's the most complicated and annoying part. And for this, at the moment, I have this solution Add a maven goal to run "Liquibase Hibernate" #754

-> this is one of the latest issues for v2.0.0, I have great hopes for it. Besides, I've seen it has been improved since I last worked on it.
So my goal is to focus on this, that's why I'm closing your ticket:

• if you don't think it's a good idea, don't hesitate to re-open it
• if you think it's a good idea, help is welcome to work on this ticket, as it's taking a lot of time, and it's quite complex to test